SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Disable or Drop


Disable or Drop

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)

Group: Administrators
Points: 327949 Visits: 20099
Comments posted to this topic are about the item Disable or Drop

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
ncbaras
ncbaras
SSC Rookie
SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)

Group: General Forum Members
Points: 31 Visits: 58
I'm embarrassed to say I did NOT know that disable options were available for that many objects. Thank you for giving me more to research! I guess that means I historically have dropped...

I think the drop/disable decision will often reside in how likely something is anticipated to come back. Disabling objects to push a test case through makes sense, but I can see someone going overboard and keeping tons of disabled objects around because they MIGHT need them again one day. The type-A in me would lean towards dropping more often than not to keep the environment from getting too cluttered.
phonetictalk
phonetictalk
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2146 Visits: 1909
I tend towards dropping for many database objects (such as indexes,discontinued ETLs, stored procs, etc).

Primarily because I don't like having junk sit around in production. If I know today that it's not needed, but I leave it there, will it ever be deleted? My experience tells me it's unlikely. (9 months ago I did a clean-up of obsolete objects in one database, and I dropped 40% of the stored procs.)

However, I do have source control so I don't have to worry about losing something permanently and, for most things, restoring from source control is as fast as re-enabling it.

Leonard
Madison, WI
Steve Jones
Steve Jones
SSC Guru
SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)SSC Guru (327K reputation)

Group: Administrators
Points: 327949 Visits: 20099
phonetictalk - Friday, January 12, 2018 11:34 AM
I tend towards dropping for many database objects (such as indexes,discontinued ETLs, stored procs, etc).

Primarily because I don't like having junk sit around in production. If I know today that it's not needed, but I leave it there, will it ever be deleted? My experience tells me it's unlikely. (9 months ago I did a clean-up of obsolete objects in one database, and I dropped 40% of the stored procs.)

However, I do have source control so I don't have to worry about losing something permanently and, for most things, restoring from source control is as fast as re-enabling it.


Having it in a VCS does make it easy to remove, but I still tend to disable with a reminder (group reminder) to drop/delete after xx days. Usually that's months to a year to be sure something isn't used.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search