Re: Store Connection/App settings in A/D
What are the pros/cons of storing connection strings and global app
in A/D. We have a lot of applications (Windows, ASP.Net, Add-ins for
etc) and each need to retrieve connections strings, global app settings,
To me, the Active Directory as a storage location for application settings
sounds too complex for generic use. Yes, you can use it as a central store
for the settings you mention, but accessing and updating (and maintaining)
the settings requires too much coding in my opinion.
So the question is: is there a specific requirement for you to use AD? If
not, then have you thought of using a simple SQL database for this task?
Some (if not all) your applications are likely to use an SQL database (SQL
Server, Oracle, etc.). The server is also probably in a central location on
your network, and thus you could access is easily.
Additionally, there are many easy programming methods to access SQL database
data. It might prove to be a better central storage for your settings than
the Active Directory.
Hope this helps!