October 16, 2009 at 7:26 am
How/What do you document about a SQL Server (as a whole and on individual instance)?
Most of the post I have come across reference documentation on the development or design of a database side of SQL Server. I would like to find out what information DBAs take note of for documenting the configuration of SQL Server itself. Sort of the Administration side of things.
I would believe you want to provide enough documentation to satisfy management in that they know I can give them the pertinent information about a SQL instance when they ask for it. However how deep should you go with this? Them would level of documentation you need depend on the circumstances, maybe for disaster recovery, vendor support, or to be able to provide information for someone replacing you?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 19, 2009 at 7:34 am
I'd start with this information:
SQL Server Specs - licensing model (# of licenses), version, edition (standard, enterprise, etc...), SP level, services installed (SSRS, SSIS, SSAS, Full-text), options enabled/disabled (xp_cmdshell, clr, etc...)
Logins
Databases - users, roles
Jobs - when, why, what
Schedules
Alerts
Operators
Those are just some things I can think of off the top of my head.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
October 19, 2009 at 8:14 am
Jack has a good list, I also used to log the sp_configure options.
I'd set up a database for this stuff, make it a standard name (I used dba_admin) and then create some tables to hold this stuff. If you can script the logging, I'd log it every day and include this db in the backups. Can be very handy for DR situations.
October 20, 2009 at 9:18 am
Thanks for the assistance!
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 20, 2009 at 10:36 am
Might I add:
Service accounts used for each service, and any non-standard permissions for them.
Rich Mechaber
January 21, 2010 at 1:07 pm
Jack,
Do you have a draft copy? I'd love to have a peak at your handiwork on such a doc.
Zee - General Dynamics, Atlanta GA
🙂
January 22, 2010 at 10:13 am
Hi,
I use these headings, they might give you some ideas:
Instance Name
Current Version
Status
Additional ?Components
Databases
Backup Strategy ?(DB, Log, Server)?
Maintenance Plans
Authentication
Notes
I usually note the location of the system and user DBs. I'm not responsible for the server machine itself. Status is like 'Production', 'Test', 'Offline'. HTH
May 2, 2011 at 11:59 am
Have you looked at BIDocumenter Tool to document Sql Server Database
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply