Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

DBAs Change Management Best Practice. Expand / Collapse
Author
Message
Posted Thursday, November 18, 2010 12:38 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, June 12, 2012 12:23 PM
Points: 86, Visits: 225
Hi All, I have to give presentation on DBAs Change Control Best Practice. Does anyone has any materail or know anything helpfull please.

I know the following in general:
Any changes on database must be tested successfuly on both dev and QA environment before implementing in production and this has to approved. Once these steps are down then changes should be applied during maintaince window/ Change Windows during off hours. Backup should be done prior to that. There has to be rollback process all the time.

Thanks
Irfan
Post #1023116
Posted Thursday, November 18, 2010 1:02 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 13,872, Visits: 9,596
Mention that 24x7 servers don't have a "window" in some cases, which means rollouts have to either be announced before-hand as non-regular downtime, or have to be done in such a manner that they don't interfere too much with a live database, or you have to work in a clustered environment where one server can be "down" and updated, and then the next. Etc.



- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #1023127
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse