Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » SQL Server 2005 » SQL Server 2005 General Discussion » Documenting SQL as a Administrator not...
Add to briefcase

Documenting SQL as a Administrator not Developer Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
Shawn Melton
Posted Friday, October 16, 2009 7:26 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Saturday, May 11, 2013 8:56 PM
Points: 754, Visits: 1,891
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
@wshawnmelton
Post #804150
Jack Corbett
Posted Monday, October 19, 2009 7:34 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 12:22 PM
Points: 10,571, Visits: 11,871
I'd start with this information:


    Server Specs - CPU's, memory, drive configuration, OS, SP level
    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

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

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
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #805020
Steve Jones - SSC Editor
Posted Monday, October 19, 2009 8:14 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: 2 days ago @ 1:47 PM
Points: 31,406, Visits: 13,722
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.






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #805064
Shawn Melton
Posted Tuesday, October 20, 2009 9:18 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Saturday, May 11, 2013 8:56 PM
Points: 754, Visits: 1,891
Thanks for the assistance!

--------------------------------------------------------------
Shawn Melton
@wshawnmelton
Post #805815
rmechaber
Posted Tuesday, October 20, 2009 10:36 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 7:43 AM
Points: 656, Visits: 2,921
Might I add:
Service accounts used for each service, and any non-standard permissions for them.

Rich Mechaber
Post #805889
ZeeAtl
Posted Thursday, January 21, 2010 1:07 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Saturday, June 23, 2012 9:48 AM
Points: 59, Visits: 259
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
Post #851535
Nice Marmot
Posted Friday, January 22, 2010 10:12 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, May 09, 2013 7:52 AM
Points: 392, Visits: 619
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
Post #852171
SSIS Guy
Posted Monday, May 02, 2011 11:59 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, May 03, 2011 11:25 AM
Points: 51, Visits: 175
Have you looked at BIDocumenter Tool to document Sql Server Database
Post #1101832
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.