This post is part of the series on SQL Snippets.
I create a lot of SQL objects such as views, tables, stored procedures and so on. If they will be used from within Microsoft Dynamics then they can simply be assigned to the DYNSA role, but if they are for use in custom reporting or integrations then separate security will be required.
Usually for reporting, and especially for integrations,…
Continue Reading azurecurve’s Article on their blog
SQL Snippets: Create and Use Database Role to Restrict Access
This post is part of the series on SQL Snippets. I create a lot of SQL objects such as views, tables, stored procedures and so on. If they will be used from within Microsoft Dynamics then they can simply be assigned to the DYNSA role, but if they are for use in custom reporting or integrations then separate security will be required.
Blog Syndicated with azurecurve’s Permission
More About This Author
Array
Dyn365GP24 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Delete an Environment
Dyn365GP23 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Delete a Company
Dyn365GP22 April 2024Upcoming Microsoft Dynamics 365 Business Central Knowledge Hub Webinars (May-Jul 2024) from MADIC dynamics
Dyn365GP22 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Rename an Environment
