|
|
|
SSCrazy Eights
        
Group: General Forum Members
Last Login: Saturday, May 04, 2013 11:13 AM
Points: 9,855,
Visits: 9,374
|
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Today @ 8:44 AM
Points: 89,
Visits: 684
|
|
| On the topic of "obsolete" objects, dropping them if they haven't been accessed in 3 months or a year is a big mistake. I've seen objects that are only accessed on leap years and if dropped would cause serious implications. My advice on objects that you think are obsolete, leave them alone unless you are absolutely, 100% certain they will never be used again. Otherwise you could be setting yourself or someone else up for big problems.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: 2 days ago @ 7:35 AM
Points: 515,
Visits: 1,016
|
|
| I'd get the separate dev and test app and database environments set up and working and run the everyday, period end, month end, year end and any other time procedures on that with profiler to find what is used and document it as well as running profiler on live to find out what gets connected to from outside the apps.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Saturday, November 03, 2012 8:04 PM
Points: 37,
Visits: 123
|
|
Really good article. I guess list could be end less as the time pass by requirements or usage change. But at least when you just been handed a DB and if you know even the only options listed here should be ok for a start. Other good suggestions could follow as given by others...
Also this could be asked in DBA interviews as at times basics are not followed getting lost in advance features..
Thanks
|
|
|
|