Originally Posted by
Ron Coderre
Your DBA should only be concerned about applications that store the database username/password locally, which of course is a huge security concern. Since Excel does not create secure compiled applications, I can understand the objection. A possible workaround would be for the DBA to assign VBA developers to a specific role with restricted access (perhaps to certain views or stored procedures) and use Active Directory validation. My choice is to use VBA to run SQL Server Reporting Services (SSRS) reports (that are structured like data dumps) into CSV files and load those files to Excel. SSRS security prevents unauthorized users from accessing the reports.
Bookmarks