Migration to production
-
I read Grant Fritchey's article on migration to production with great interest. Mainly because I wish this were the way things were done everywhere.
Has anyone else worked in an environment where changes are made to live mission critical systems and where there is no identical test setup because of the "cost"?
Nigel Moore
====================== -
Nigel,
I've worked at places where this is a policy, not just a cost cutting measure
Seriously though, where this does happen seems, in my experience, to be in smaller companies that simply have tighter budgets. Obviously everyone would love to be able to throw money at a problem like the heavyweights do - life aint like that though!
Having said that one of my previous projects was at a large UK retail bank (I won't say which one but it was one of the big 4) which had an E-commerce setup. We were responsible for the data mart built on the ack of it. Any changes we had to make had to be made direct to production - no testing or anything like that. Hilarious really!
Regards
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson -
Yup, 2 1/2 years at an internet stock trading company about number of years ago ... some examples:
1) Release candidate of Win 2K Enterprise server put into production on the external web clusters hours after being available for download. (same for IIS too !).
2) SQL v7.0 Beta, in production on a handful of servers 2 hours after release on the website to Premier customers.
3) Developers had direct 'dbo' access to production for rollouts at will any time of the day or night !
The environment had 60+ SQL Servers. After 2 1/2 years of constant fires (and headaches) I executed "sp_update_resume" and "sp_distribute_resume" giving the results set of "normal and fulfilling life".
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply