December 26, 2011 at 7:48 am
Fundamental question:
What is considered to be good solid documentation for a SQL Server admin. We have about 25 instances - and they are different versions (from 2000 to 2008 R2) and editions (Express to Enterprise Edition - 64 bit). Keep in mind I'm just starting out. Any comments/URLs are welcome.
Thank you...
December 26, 2011 at 8:01 am
Didn’t get you. Please elaborate the term ‘Documentation’.
December 26, 2011 at 8:55 am
Documentation – what do you need to document a SQL Server instance. Aside from version / edition, host name and IP, passwords. What do you need? What should you have?
December 26, 2011 at 4:21 pm
In addition to the obvious items you have listed, I would as a start list:
1. Major purpose of server.
a. Mirror sever for .......
(a1). DBs mirrored
b. Used for replication
(b1). DBs replicated.
2. List of DBs on each server.
3. For each DB on the server, purpose of the DB
for example
a. Host for vendor 'ABZ' software package titled 'mno', which is utilized by 'xxx' department.
(1). Vendors product number, revision, date last revised.
(2). Vendor contact name and phone number.
b. Internal contact for each DB.
c. Backup schedule for each DB
d. Date of last test for restoring each DB.
Surely you can go on with your own ideas, just hope the above gets you started.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply