Keeping Track of Details

SQL Server Best Practices
SQL Server Best Practices
After creating a few new SQL accounts this morning, I thought I would share how I keep track of minor details like this.  We use SharePoint for our department to track documents, procedures, processes, etc.  This is a great place to track minute SQL Server details like accounts and databases.  For example, we have over 280 databases across 32 servers.  Some of the applications may have five or ten databases and I cannot keep 280 databases in my head as far as where they are, what application they are used for, who the business owner is, and if they are production, acceptance, or development.

I setup a SharePoint spreadsheet (ok its called a datasheet, but it is just a spreadsheet), for tracking SQL user name and passwords and of course I limit the access on this sheet, in case you were thinking about that.  This is handy so that we do not have to reset them when the application administrator forgets it and wants to reset it and throw the application into turmoil.

Continue reading on

(0 votes. Average 0 of 5)
Leave a reply

Your email address will not be published. Required fields are marked *