September 13, 2014 at 11:41 am
Comments posted to this topic are about the item The Ten Commandments for DBAs
September 15, 2014 at 9:23 am
I would agree that new versions should be tested before upgrading production systems. However, I'm always concerned about my systems getting too far behind in terms of versions. I've worked with system that when they finally need to be upgraded (and that will eventually happen) the upgrade process is a nightmare either from too many changes or having to upgrade in multiple steps (because you can't migrate directly to the new version).
A little extra work now saves a whole lot of pain later.
September 15, 2014 at 9:42 am
Great list as a guide. Would have preferred it will a little less of an Olde English flavour 😉
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
September 15, 2014 at 9:57 am
I think there's one commandment missing:
Thou shalt not covet thy neighbor's database(s).
Sorry, couldn't resist. 😛
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 15, 2014 at 10:06 am
Alvin Ramard (9/15/2014)
I think there's one commandment missing:Thou shalt not covet thy neighbor's database(s).
Sorry, couldn't resist. 😛
ROFL
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 15, 2014 at 1:47 pm
Timely Manner is definitely a subjective term. I've worked in shops where it's a nightmare to upgrade systems because they risk no longer being supported by MS. I've also worked in a place where Beta was considered production ready. I tend to stick to the SP1 rule and don't like to get more than one version behind if possible.
Aigle de Guerre!
September 16, 2014 at 8:15 am
Great list. Reason rules, so of course one would research/test any proposed updates, and timely is subjective as others have noted. Automated restore to test backups is something I focus on first with new clients. I may not end up doing it (at request of client), but I at least want to make sure I have covered it with them.
The more you are prepared, the less you need it.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply