Our customer thinks that he owns the data and should have direct access via SQl Management Studio to view/edit his data directly in production environment, exactly in the same way he has done until now in all previous versions of Dynamics.
As a Microsoft Agent has told us, this access right now is only guarantee in sandbox environments, but no in production. The new procedure from now on should be to download the production DB to a Sandbox environment, check the situation and needs in this sandbox environment (having in mind that some parameters may need to be adaptaed as we will be not in production...) and send back to Microsoft agents the queries/updates/changes we would like to execute directly in the Production Database.
Frankly, we do not see what's the point of this change, that will result only in a decrease in the time and service we will offer to our customers in this Microsoft product evolution. As a matter of fact, any instruction we can do via SQl Management studio, can also be done via Job or code embebed into the system... But of course, having access via SQL management Studio will allow us to explore the data and offer inmediate solutions that may be needed in some scenarios for our customers.
We've been told also that there's no official document that reflects this change in the management environment procedure vs previous versions, but just a few words and articles explained in the technet product documentation...
We'll appreciate very much if this suggestion is taken in consideration in the near future.
Best regards and have a good travel on the Microsoft ecosystem products for all of you!!!