| |
|
|
|
Submitted on: 12/12/2004 11:04:59 PM
By: Chong Long Choo
Level: Advanced
User Rating:
By 8 Users
Compatibility:VB.NET
Users have accessed this code 4949 times.
| |
| | | <p>As SQL Server administrators, we all know how important it is to document our server configurations. Producing and maintaining complete SQL Server documentation is an important job of every SQL Server administrator. Here are just a few of key benefits of producing such documentation: </p>
<BR><BR>- Tracking and documenting SQL object changes during the testing process, or to document changes made after an SQL Server has been put into production.
<BR><BR>- Learning about a new SQL Server that you now have been assigned to maintain.
<BR><BR>- Providing system documentation for disaster recovery.
<p>Every administrator knows how important good documentation is, but how many of them actually do a good job at it? If I had to guess, I would say the percentage is fairly low. So why would a administrator, who knows how important good documentation is, not create and maintain it?
It’s boring. Nobody likes to create, and especially maintain, documentation. Besides that, most administrators I know are so busy that they just don’t have the time to provide and maintain good documentation, even if it wasn’t so boring.</p>
<p>Given the importance of good documentation, but the lack of desire or time to do it, what can be done? That’s the question we always ask ourselves. And the answer I came up with is SQLAnalyzer. </p>
<p>Essentially, SQLAnalyzer is SQL Server documentation tool that can automatically document every object in a SQL Server (such as tables, views, stored procedures, etc......), along with documenting all SQL Server server configuration settings. </p>
<p>In conclusion, the overall advantage is that you don’t have to do the documentation yourself. SQLAnalyzer will do all of the work for you. Now, there is no excuse not to document the SQL Server that you are responsible for maintaining.</p>
<p>Essentially, SQLAnalyzer is SQL Server documentation tool that can automatically document every object in a SQL Server (such as tables, views, stored procedures, etc......), along with documenting all SQL Server server configuration settings. </p>
<p>In conclusion, the overall advantage is that you don’t have to do the documentation yourself. SQLAnalyzer will do all of the work for you. Now, there is no excuse not to document the SQL Server that you are responsible for maintaining.</p>
<p>Features:
<LI>Generate configurations report in HTML format for all SQL Server objects.
<LI>Generate system information that you probably need when recover your SQL Server.
<LI>Compress generated files into a ZIP file.
</p>
| | | | |
 Download code
Note: Due to the size or complexity of this submission, the author has submitted it as a .zip file to shorten your download time. Afterdownloading it, you will need a program like Winzip to decompress it.
Virus note:All files are scanned once-a-day by Planet Source Code for viruses,but new viruses come out every day, so no prevention program can catch 100% of them.
FOR YOUR OWN SAFETY, PLEASE:
1)Re-scan downloaded files using your personal virus checker before using it.
2)NEVER, EVER run compiled files (.exe's, .ocx's, .dll's etc.)--only run source code.
If you don't have a virus scanner, you can get one at many places on the net including:McAfee.com
|
Terms of Agreement:
By using this code, you agree to the following terms...
1) You may use
this code in your own programs (and may compile it into a program and distribute it in compiled format for languages that allow it) freely and with no charge.
2) You MAY NOT redistribute this code (for example to a web site) without written permission from the original author. Failure to do so is a violation of copyright laws.
3) You may link to this code from another website, but ONLY if it is not wrapped in a frame.
4) You will abide by any additional copyright restrictions which the author may have placed in the code or code's description.
| |
|
Other 5 submission(s) by this author
| | | |
 Report Bad Submission | | | | | Your Vote! | |
See Voting Log | | | | Other User Comments |  12/14/2004 1:26:04 AM: Chong Long Choo
1. Please download ICSharpCode.SharpZipLib.dll from
http://www.icsharpcode.net/OpenSource/SharpZipLib/Default.aspx
2. Add reference for
a) Microsoft SQLDMO Object Library
b) Microsoft DTSPackage Object Library
(If this comment was disrespectful, please report it.)
| 12/14/2004 7:41:00 PM: CodeFester
I have all the references you mentioned and it was humming along nicely; then I got this exception. Of course, bogus as .NUT debugging is it stopped where the sun doesn't shine (no source) and the disassembly didn't do me alot of good. It generated some cool docs for part of the first database on my server. I will wait a few days to vote to see how it gets resolved.
Thanks for sharing though.
- System.Exception {"QueryInterface for interface SQLDMO.NameList failed." } System.Exception
(If this comment was disrespectful, please report it.)
| 12/14/2004 8:15:35 PM: Chong Long Choo
hope this will help:
1. http://www.dotnet247.com/247reference/msgs/31/159951.aspx
2. http://www.dotnet247.com/247reference/msgs/31/159951.aspx
3. http://www.error-bank.com/microsoft.public.dotnet.languages.vb.1/207792_Thread.aspx
(If this comment was disrespectful, please report it.)
| 12/14/2004 8:17:54 PM: Chong Long Choo
http://www.sql-server.org/QueryInterface_error_with_SQLDMO_NameList-2718939-3735-a.html
(If this comment was disrespectful, please report it.)
| 11/3/2006 6:44:31 PM: Dr. Y
Sweet App!
(If this comment was disrespectful, please report it.)
| | |
Add Your Feedback! | Note:Not only will your feedback be posted, but an email will be sent to the code's author from the email account you registered on the site, so you can correspond directly.
NOTICE: The author of this code has been kind enough to share it with you. If you have a criticism, please state it politely or it will be deleted.
For feedback not related to this particular code, please click here.
|
To post feedback, first please login.
| |
