Allow comments to be documented with Server configuration and database options. - by Stuart L C

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 785325 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 4/22/2013 2:13:06 PM
Access Restriction Public

Description

I would like to see an option to be able to document server configuration changes and database options. This would basically allow a self-documenting feature for any instance so that a DBA can note when a configuration parameter has been changed from the default and why. 
This would help any new DBA to support the instances as well as it would be good information to have queried as part of any SQL Risk Assessment.
Sign in to post a comment.
Posted by Stuart L C on 10/15/2014 at 9:36 AM
I don't want to use DDL triggers and develop something custom. I'm providing ideas to make your product more flexible, self-documenting and basically give you ways to seperate yourself from the rest of the pack. Having a history of configuration changes, date it was changed and comments by the changer as to why it was modified from the default provides self-documenting, run-book type operational features that would be well received.
Posted by Microsoft on 4/26/2013 at 10:40 AM
Hello Stuart,
Thanks for your feedback. You can use server DDL triggers to do the tracking yourself. So I am closing this as "won't fix" since we don't plan to implement such a tracking feature in the engine.

--
Umachandar, SQL Programmability Team