We recently ran into an issue where we were forced to change our Read/Write account password for our SQL server database. The result has been an epic treasure hunt to identify all the web applications and macros that were tracking usage data(and backend data to support the app) to the database - and then updating each individual connection string.
Surely there must be a way of storing a central connection string so that it's secure but accessable by multiple applications? We were thinking about js, which would work for the read-only account but obviously not a good idea to have the read/write account username and password freely available.
Notes: All connection attempts to the database will be on a secure intranet.