Home Dashboard Directory Help

Allow User objects to be deprecated by way0utwest


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Suggestion
ID: 490420
Opened: 9/17/2009 7:35:17 AM
Access Restriction: Public


One of the issues that we often find in mature databases is old code. Often people are unwilling to remove objects at a point in time because of the possibility that they might be used in the future. However this becomes an issue in keeping track of items.

It would be good for users to be able to somehow manage these objects that might need to be pruned from the system.

Sign in to post a comment.
Posted by Microsoft on 3/24/2011 at 4:34 PM

Thank you for submitting this suggestion, but given its priority relative to the many other items in our queue, it is unlikely that we will actually complete it. As such, we are closing this suggestion as “won’t fix”. If you feel that this is worth reconsidering, feel free to respond to this message and we will take another look.

SQL Server Engine
Posted by Kevin Wagner on 1/16/2010 at 5:52 PM
Interesting, would need to update some of the .net objects to understand object depreciation. Could be at design time as well to alert the developer of the pending depreciation. It would also mean new exception objects/classes to elegantly handle the "missing" database objects.
Posted by PuzzledDBA on 10/8/2009 at 12:57 PM
This would be a Godsend. Being able to say once and for all that a DB object was no-longer used would be invaluable.

Some of our legacy databases have thousands of objects and no-one is willing to trawl through the millions of lines of legacy spaghetti code to identify whether or not they are used. Short of running a trace over an extended period of time (not feasible in our production systems) it is virtually impossible to deprecate anything.
Posted by Tim Mitchell on 10/8/2009 at 8:24 AM
Good idea. This would be a useful addition to the SQL Server feature set.
Posted by Microsoft on 9/21/2009 at 2:08 PM

This is indeed an interesting idea, and it dovetails nicely with some thoughts we've been having around managing the surface area of database apps. No promises for this release, but it is definitely something we will consider.

Posted by Adam Machanic on 9/17/2009 at 9:47 AM
That's a very cool idea! Although it could just as easily be hand-rolled using SQL Audit.
Sign in to post a workaround.