June 2, 2008 at 1:40 pm
Idera has a BETA of the Admin Tool belt. It can document and save config info for the servers and databases. You can define groups and document all your production servers in one XML file, which you can use to compare and highlight differences. Very sweet tool
June 3, 2008 at 7:01 am
SchemaToDoc (http://www.schematodoc.com) will document your database's tables, fields (type, size, defaults, nullable), indexes, check constraints, foreign keys, triggers, views, stored procedures and functions. It has Word and HTML output. It also lets you easily annotate your tables, fields, and views.
June 3, 2008 at 7:07 am
Robert Bedick (6/3/2008)
SchemaToDoc (http://www.schematodoc.com) will document your database's tables, fields (type, size, defaults, nullable), indexes, check constraints, foreign keys, triggers, views, stored procedures and functions. It has Word and HTML output. It also lets you easily annotate your tables, fields, and views.
It doesn't look like it covers security, though. Or does it?
K. Brian Kelley
@kbriankelley
June 3, 2008 at 8:21 am
Well, since the topic has completely shifted from documentation of a server to documenting SQL Server you may want to consider SQLClue. (Please pardon the long winded plug, but seems like useful and apropos info.) This tool has it's roots in my DMO based DDL Archive Utility that you could get from SSC for many years. SQLClue documents all SQL Server DDL and all other Configuration meta data from as many '00, '05 and '08 SQL Instances as you like to a central database that can be SQLExpress '05 or '08 - has it's own scheduler. It includes security - by default permissions are attached to both the securables and principals - but is completely configurable. Has a library of canned RS reports, and includes a compare tool with complete Regular Expression and SMO Scripter user control. Lets you compare any of meta data on the Instance, any version from the archive and source control working folders.
One of many features is the ability to enable DDL events and Trace events to a local queue that is periodically slurped up by the central service. That means on '05 and '08 Instances you get all the EVENTDATA (the change script, the logged in user, the meta data, the time changed, etc.) for every change that can be detected by EVENTS (not all can you know).
Between the Health and History Tool and SQLClue, I don't think there is much config missing and it is all in central data stores that can be queried, replicated, merged, and as desired.
Also includes a few other capabilities that I find essential: Query Baseline automation for '00, '05, '08 and a SQL Runbook that will work as well for Oracle or MySQL.
SQLClue is still pre-release (alpha?). Let me if you'd like to take a peek, especially if you'd be willing to give a little feedback about what else you need.
Bill
Bill Wunder
June 3, 2008 at 9:33 am
I would be willing to look at SQLClue & SQLRunbook. Not sure what they do, but we do have Oracle and MySQL along with SQL Server.
Everyone has provided quite a bit of information. Thanks for the response. I am surprised that we don't have an enterprise documentation system with a consolidated tool set.
Greg
June 6, 2008 at 12:58 pm
I finally put together all my scripts and install steps for using SYDI-Server with SQL 2005 :cool:. I posted it on my blog for anybody who's interested:
http://kendalvandyke.blogspot.com/2008/06/network-documentation-with-sql-2005-and.html
Kendal Van Dyke
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply