Rolling SQL Server Upgrades: 5 Tips from the Pros

By:


Upgrades happen. Sometimes because business needs dictate them. Sometimes because IT requirements force them. Whether the SQL Server upgrade is just a patch or a full on major upgrade, the risk involved can strike fear into the heart of the database team. The fear even causes some to hold off on upgrades, which can deprive your business of much needed bug fixes or new functionality.

So, how can you implement an upgrade in the best possible way? We convened a Twitter chat recently on upgrades with Argenis Fernandez (@DBArgenis) and Tom LaRock (@SQLRockStar). Five key tips emerged from the enthusiastic discussion:

  • Have a plan
  • Test the plan, repeatedly
  • Have a plan for rollbacks
  • Understand complexities
  • Involve the business stakeholders

You can read the full Twitter chat transcript here.

Tip 1: Have a Plan for the Upgrade—No Excuses!

Without appropriate preparation, you risk firefighting mode, as @DBArgenis points out:

DBArgenis upgrade plans avoid firefighting

Among other considerations, you should extend your planning to include other necessary upgrades. For example, @JDanton points out that, in his opinion, you should always be installing upgrades on the latest version of Windows:

JDanton pro tip install latest windows server

Tip 2: Test the Upgrade Plan–Repeatedly!

According to @DBArgenis and @SQLRockStar, database mirroring is the easiest way to perform a high-availability upgrade, but easy doesn’t negate the need for testing, as @MrDenny again underscored:

MrDenny mirroring makes upgrades easier

Planning, and then testing that plan, several times, is critical. And @tameraclark agrees:

TameraClark practice makes upgrades perfecter

A fatal mistake for many is making the assumption that a plan, being a plan, will just work, as @SQLHA pointed out:

SQLHA assuming doesn't work

 

@LawrenceGarvin reiterated the need to test the plan:

LawrenceGarvin written and tested plans critical

 

Tip 3: Have a Plan for Rollbacks if Needed

Even with planning and testing, upgrades do not always go as planned—and you can’t always account for every scenario. So you must always have a plan to rollback, as @SQLRockstar points out:

SQLRockStar must have rollback plan

This point is so critical, it was restated by many particpants, including @DBArgenis:

DBArgenis must have plan to rollback

 

Tip 4: Understand Complexities

Among the more complex rolling upgrade solutions, @DBArgenis noted that Avaiability Groups pose significant issues, and advised that you must be careful of which replica you upgrade at the time:

DBArgenis upgrades to availability groups complex

@JDanton agreed:

JDanton availability groups complex

@SQLRockStar added that upgrades involving failover clustering can be more costly and complex:

SQLRockStar availability groups and failover clustering complex

Tip 5: Involve the Business Stakeholders

Finally, it may seem tempting to exclude the business from upgrade plans that are initiated by IT for IT reasons, but DBABullDog points out that keeping the business stakeholders involved in the entire upgrade process helps mitigate risk:

DBABullDog must have business in on upgrades

Conclusion

SQL Server upgrades offer the benefit of bug fixes and new functionality. That being said, taking advantage of all the updgrades offer is not a simple task. You must plan. You must test. You must prepare to rollback if something goes wrong. You must work to truly understand the complexities of your particular environment. And you must make sure to include all the stakeholders in an upgrade process, including the business team. Paying attention to each of these tips will help you mitigate the risks involved and deliver the true benefits of the upgrade to your end users.

Read the full datachat transcript here

 

Handle Tweet
SWI_Database Let’s get started…. #datachat Q1 coming right up.
DBArgenis RT @SWI_Database: Let’s get started…. #datachat Q1 coming right up.
SQLRockstar RT @SWI_Database: Let’s get started…. #datachat Q1 coming right up.
SWI_Database Q1: Who typically decides how and when server or application upgrades are performed? #datachat
SQLRockstar RT @SWI_Database: Q1: Who typically decides how and when server or application upgrades are performed? #datachat
mrdenny @SWI_Database could be the business, IT, DBA, etc. Depends on why the upgrade needs to be done. #datachat
SQLRockstar .@SWI_Database A1: The business decides when, and IT decides how (usually). #datachat
DBArgenis @SWI_Database typically there are multiple actors involved. From my experience, they are driven by a business need #datachat
GarethSwan RT @SQLRockstar: @DBArgenis BTW, you are one of the folks that convinced me to earn my #MCM4LIFE, thank you for that good sir. #datachat
SQLSoldier @mrdenny @SWI_Database All of the above, to some degree. #datachat
DBArgenis @SWI_Database rather than technical factors 2/2 #datachat
SQLRockstar .@SWI_Database A1: But I’ve also seen IT decide some upgrades are necessary, and force the business to agree. #datachat
patrick_luther @DBArgenis @SWI_Database #datachatIs an upgrade considered the same thing as a simple patch?
SQLRockstar RT @patrick_luther: @DBArgenis @SWI_Database #datachatIs an upgrade considered the same thing as a simple patch?
DBArgenis @SQLRockstar @SWI_Database A1: I absolutely agree there. Some upgrades are driven by pure technical debt. #datachat
SWI_Database RT @mrdenny: @SWI_Database could be the business, IT, DBA, etc. Depends on why the upgrade needs to be done. #datachat
SWI_Database RT @DBArgenis: @SWI_Database typically there are multiple actors involved. From my experience, they are driven by a business need #datachat
DBArgenis @patrick_luther @SWI_Database I consider anything that increases the #SQLServer build number to be an upgrade. 1/2 #datachat
SWI_Database RT @patrick_luther: @DBArgenis @SWI_Database #datachatIs an upgrade considered the same thing as a simple patch?
DBArgenis @patrick_luther @SWI_Database it might not seem a big deal, but every change in engine bits can make a big difference #datachat
SQLRockstar .@patrick_luther @DBArgenis @SWI_Database I’d say “yes”, as a patch should be moving you forward, not backwards. #datachat
patrick_luther @DBArgenis @SWI_Database Thanks for the clarification.  There was a lot of talk about this particular subj. this week  #datachat
DBArgenis @patrick_luther @SWI_Database most folks don’t test when rolling Cumulative Updates. Plan regressions can be a pain to 1/2 #datachat
Eshbaugh @SWI_Database A1 sometimes third party applications will dictate an upgrade #datachat
DBArgenis @patrick_luther @SWI_Database deal with after you have deployed to prod…I hate putting out fires created by lack of testing #datachat
SWI_Database Q2: For beginning admins, what would you recommend as a rolling upgrade solution and why? #datachat
SWI_Database @Eshbaugh Welcome back Jerry! #datachat
DBArgenis @SWI_Database honestly, I think Database Mirroring is the easiest way to perform a HA upgrade – even though it’s been deprecated #datachat
SQLRockstar RT @Eshbaugh: @SWI_Database A1 sometimes third party applications will dictate an upgrade #datachat
SQLRockstar RT @SWI_Database: Q2: For beginning admins, what would you recommend as a rolling upgrade solution and why? #datachat
SWI_Database RT @tameraclark: @SWI_Database practice, practice, practice that is what all those non-prod tiers are for #datachat
DBArgenis @SWI_Database you would think that Mirroring is hard to setup, but it’s actually not. #datachat
SQLRockstar .@SWI_Database Q2: I’d go with database mirroring as the easiest. #datachat
mrdenny @DBArgenis @SWI_Database A2: I agree with Argenis, mirroring makes it really easy and safe. But start in Dev, then QA then Prod. #datachat
DBArgenis @SWI_Database When I run into issues with Mirroring I just search for @SQLSoldier’s blog #datachat
redi311 RT @SQLRockstar: @DBArgenis BTW, you are one of the folks that convinced me to earn my #MCM4LIFE, thank you for that good sir. #datachat
SQLRockstar .@DBArgenis @SWI_Database Well, it *used* to be, because the SQL 2005 GUI didn’t work and you had to script it all out. #datachat
SWI_Database RT @mrdenny: @DBArgenis @SWI_Database A2: I agree with Argenis, mirroring makes it really easy and safe. But start in Dev, then QA then Pro…
DBArgenis @mrdenny practice, practice, practice! #datachat
mrdenny @DBArgenis yep, there’s no such thing as to many practice upgrades before doing production. #datachat
DBArgenis @SQLRockstar @SWI_Database well, if you remember Mirroring wasn’t introduced until 2005 SP1 (!) – a major feature shipped with SP1 #datachat
DBArgenis @SQLRockstar @SWI_Database it was sort of still half baked on 2005 SP1, even. #datachat
AirborneGeek @mrdenny @DBArgenis @SWI_Database Both to practice the upgrade and to make sure nothing screwball happens b/c of the patch #datachat
SQLRockstar .@DBArgenis @SWI_Database Exactly, even after SP1 I found the GUI still had issues. Scripting worked though. #datachat
mrdenny @DBArgenis @SQLRockstar @SWI_Database don’t remind me of SQL 2005, client this week has a 2005 server. #datachat
DBArgenis @mrdenny however, due to marvelous DATA DUPLICATION, Mirroring offers a plausible plan of rolling back. #datachat
SQLRockstar .@mrdenny @DBArgenis @SWI_Database Sounds like a good opportunity to raise your rates. #datachat
DBArgenis . @mrdenny I talk about that A LOT on my “Rolling Upgrades” talk that I’ll be doing for @SWI_Database next week #datachat
SWI_Database @AirborneGeek Welcome back Kerry! #datachat
SWI_Database RT @lutef1sk: @mrdenny @DBArgenis @SQLRockstar @SWI_Database lemme guess, they want to upgrade to 2008? #datachat
mrdenny @SWI_Database @lutef1sk @DBArgenis @SQLRockstar sadly this isn’t an upgrade project. #datachat
SWI_Database RT @SirWill: @SWI_Database RE Q2: How about going from 1 SQL 2008 Standard to new 2012 Enterprise AG cluster? #datachat
DBArgenis By the way, @SWI_Database and @SQLRockstar, thanks for having me again at #datachat – it’s truly an honor to drink and tweet with you 🙂
SQLRockstar RT @DBArgenis: By the way, @SWI_Database and @SQLRockstar, thanks for having me again at #datachat – it’s truly an honor to drink and tweet…
DBArgenis @SWI_Database @SirWill well, you have many ways to get there. My recommendation is: log ship first, then move onto Mirroring #datachat
DBArgenis @SWI_Database @SirWill then failover to 2012, then take backups and create your AG #datachat
SWI_Database Q4: If log shipping were an actor/actress, who would it be and why? #datachat
SWI_Database Q3: Which rolling upgrade solution has the most complexity and why? #datachat
SQLRockstar RT @SWI_Database: Q3: Which rolling upgrade solution has the most complexity and why? #datachat
DBArgenis @SWI_Database Availability Groups, bar none. You need to be careful of which replica you upgrade at the time. #datachat
jdanton @SWI_Database a3:  I’m gonna leave SQL Server for a minute and go with Oracle RAC. Oy. #datachat
SQLRockstar .@SWI_Database Availability Groups, or Failover Clustering, no question. More complex, more costs, etc. #datachat
SQLRockstar RT @jdanton: @SWI_Database a3:  I’m gonna leave SQL Server for a minute and go with Oracle RAC. Oy. #datachat
Eshbaugh @mrdenny channge your rates! #SQLServer 2008R2 -> 2014:$200/hour, 2005:$400/hour, 2000:$800 / hour and watch them upgrade fast! #datachat
YlberAponte RT @SQLRockstar: .@SWI_Database Availability Groups, or Failover Clustering, no question. More complex, more costs, etc. #datachat
SQLRockstar .@jdanton @SWI_Database Why RAC? Just the cost? #datachat
SQLRockstar RT @Eshbaugh: @mrdenny channge your rates! #SQLServer 2008R2 -> 2014:$200/hour, 2005:$400/hour, 2000:$800 / hour and watch them upgrade fas…
jdanton @SQLRockstar @SWI_Database It’s just a lot more complex. SQL rel easy–patch inactive, failover, patch formerly actiive, failback #datachat
SirWill @DBArgenis @SWI_Database restore, reconfigured apps, turned apps back on.  about 5 minutes down time 500GB database.   #datachat
jdanton @DBArgenis I just don’t find SQL rolling upgrades to be that hard. #datachat
SQLRockstar .@jdanton @SWI_Database I was told RACs were easy though, just point and click? #datachat
jdanton @SQLRockstar @SWI_Database I’d ROTF and LMAO, but I’m in an airport lounge and the floor is kind of dirty. #datachat
DBArgenis @SirWill @SWI_Database that’s interesting. I’ve done that same exact Mirroring setup, no issues. #datachat
SQLRockstar .@jdanton @SWI_Database Puh-lease, I’ve seen you on many an airport lounge floor, just not laughing. #datachat
sqlstudent144 Question: How often do you see companies “upgrading” to versions multiple years out of date? (2008 R2 for example) #datachat
DBArgenis @SQLRockstar @jdanton @SWI_Database true story, just replace “airport” with “a big corporation’s HQ” #datachat
jdanton .@SWI_Database In SQL though, I’d go with AGs. Was at a client today because they had issues with reboot order for updates #datachat
mrdenny @sqlstudent144 just upgraded a client from 2005 to 2008 R2 this year. Happens all the time. Usually 3rd party apps .#datachat
SQLHA @jdanton @SWI_Database Reboot + quorum = fun #datachat
SQLRockstar .@sqlstudent144 It happens, but in my experience we were forced to stay no more than 1 major version behind. #datachat
DBArgenis @sqlstudent144 all the time. It’s the rule, not the exception. #datachat
SQLHA @SQLRockstar @sqlstudent144 Happens more than you think, usually app related. Or IT departments that move at a glacial pace. #datachat
mrdenny @DBArgenis @sqlstudent144 @SQLRockstar we’ve now given all 3 answers in 45 seconds. #datachat
DBArgenis @sqlstudent144 and with #SQLServer’s new, more aggresive release schedule, I see more and more people not upgrading as fast. #datachat
sqlstudent144 @SQLHA @SQLRockstar Glad to hear it. We are being forced to stick with R2 on almost half our servers due to DTS #datachat
LawrenceGarvin @sqlstudent144 4sure. In ’08 I finished a 2 yr upg project to SQL’05. And now there’s 4 new SQLs since then. Hope they kept up! #datachat
SQLRockstar RT @sqlstudent144: @SQLHA @SQLRockstar Glad to hear it. We are being forced to stick with R2 on almost half our servers due to DTS #datachat
jdanton It’s always a bad sign when you walk into a shop and see the XP screensaver. #datachat
DBArgenis There are too many CIOs with a “if it works, don’t upgrade it” mentality out there #datachat
SQLRockstar .@sqlstudent144 @SQLHA Is that a 3rd party app? #datachat
SQLRockstar RT @LawrenceGarvin: @sqlstudent144 4sure. In ’08 I finished a 2 yr upg project to SQL’05. And now there’s 4 new SQLs since then. Hope they …
SQLRockstar .@LawrenceGarvin @sqlstudent144 I hope they kept your number, and you’ve increased your rates. #datachat
SQLRockstar RT @jdanton: It’s always a bad sign when you walk into a shop and see the XP screensaver. #datachat
SQLHA @DBArgenis And then they realize how screwed they are 5 years later #datachat
Eshbaugh RT @DBArgenis: There are too many CIOs with a “if it works, don’t upgrade it” mentality out there #datachat
SQLRockstar .@jdanton You say “bad”, and I say “opportunity”. #datachat
SWI_Database @SQLHA Welcome back Allan. Tom was wondering if you might be late joining us #datachat
DBArgenis @SQLHA it’s called technical debt. Don’t pay it quickly, and compound technical interest is against you #datachat
sqlstudent144 . @SQLRockstar @SQLHA Pre SSIS legacy DTS that no one will upgrade despite years of me “mentioning” it. #datachat
jdanton @SQLRockstar there are good projects and there are bad projects. I’d rather do the good ones. But if the money is green. #datachat
SQLHA @SQLRockstar @jdanton Opportunity, yes. But pain for everyone including those who would be helping. #datachat
SQLRockstar .@SQLHA @DBArgenis The problem is they *aren’t* screwed, because they’ve moved on by then. #datachat
DBArgenis @SQLRockstar @jdanton yeah, that’s a consultant’s dream come true. Especially if scope = security 🙂 #datachat
SQLHA RT @DBArgenis: @SQLHA it’s called technical debt. Don’t pay it quickly, and compound technical interest is against you #datachat
DBABullDog @SWI_Database Q3 if all DBs in rolling upgrade require i, u, d & reads solution becomes more complex. Our data is out business. #datachat
SWI_Database now the real Q4: If log shipping were an actor/actress, who would it be and why?  #datachat
LawrenceGarvin @DBArgenis This mentality is not exclusive to database servers either!!! #datachat
SQLRockstar RT @SWI_Database: now the real Q4: If log shipping were an actor/actress, who would it be and why?  #datachat
DBArgenis @SWI_Database why Emily Blunt, of course. Most underrated actress ever. She’s kinda awesome 🙂 #datachat
SQLHA @SWI_Database They are complex. FCIs arguably the most with multiple instances on a single WSFC. #datachat
SWI_Database 🙂 RT @SQLHA: @SWI_Database Was out to dinner with a friend. Need to escape the laptop every now and then. #datachat
SQLRockstar .@SWI_Database A4: Matthew McConaughey. You don’t think he’s got the goods, but he always gets the job done. #datachat
SQLHA @SWI_Database They are all complex. FCIs arguably the most with multiple instances on a single WSFC. #datachat
SWI_Database @LawrenceGarvin Welcome back Lawrence! #datachat
DBArgenis @SQLRockstar alright, alright, alright #datachat
SQLRockstar RT @DBArgenis: @SQLRockstar alright, alright, alright #datachat
jdanton @SWI_Database @SQLRockstar a4: Meryl Streep. The best supporting actress ever. #datachat
LawrenceGarvin @SWI_Database A4: wow… could be the challenging Q of the day. Betty White.. cuz it’s just that old. #datachat
SQLRockstar RT @jdanton: @SWI_Database @SQLRockstar a4: Meryl Streep. The best supporting actress ever. #datachat
SQLRockstar RT @DBArgenis: @SWI_Database why Emily Blunt, of course. Most underrated actress ever. She’s kinda awesome 🙂 #datachat
SQLRockstar RT @LawrenceGarvin: @SWI_Database A4: wow… could be the challenging Q of the day. Betty White.. cuz it’s just that old. #datachat
Eshbaugh @jdanton @SQLRockstar   I have made a lot more money on bad projects than good,  but a bad client has never been worth the money. #datachat
SQLRockstar RT @Eshbaugh: @jdanton @SQLRockstar   I have made a lot more money on bad projects than good,  but a bad client has never been worth the mo…
SWI_Database RT @LawrenceGarvin: @SWI_Database A4: wow… could be the challenging Q of the day. Betty White.. cuz it’s just that old. #datachat
DBArgenis @LawrenceGarvin oldie but goodie! #datachat
SQLHA @SWI_Database @SQLRockstar I think log shipping is Clint Howard. That guy in every movie you remember w bit part, totally solid. #datachat
SQLRockstar @DBArgenis Don’t forget his performance in Sahara, either. #datachat
SQLRockstar RT @SQLHA: @SWI_Database @SQLRockstar I think log shipping is Clint Howard. That guy in every movie you remember w bit part, totally solid.…
LawrenceGarvin @SWI_Database Thanks! Sorry I was late to the party. Got distracted. #datachat
DBArgenis @SQLRockstar now you’re making me want to go watch Interstellar. #datachat
SQLHA @SQLRockstar @SWI_Database And like log shipping, he’s always got work. #datachat
SQLRockstar RT @SQLHA: @SQLRockstar @SWI_Database And like log shipping, he’s always got work. #datachat
SQLRockstar .@SQLHA @SWI_Database And drives a Lincoln, but not because they’re cool. #datachat
SQLHA @SQLRockstar @SWI_Database I was talking about Clint Howard, not Matthew. #datachat
LawrenceGarvin @SQLRockstar @SQLHA @SWI_Database AND.. drives it in #AUSTIN 🙂 #datachat
patrick_luther @SQLRockstar @SQLHA @SWI_Database While rolling boogers in his fingers#datachat
DBArgenis @SQLRockstar @SQLHA @SWI_Database let’s face it. He drives a Lincoln because he GOT PAID!!! #datachat
SQLRockstar RT @patrick_luther: @SQLRockstar @SQLHA @SWI_Database While rolling boogers in his fingers#datachat
SQLRockstar RT @DBArgenis: @SQLRockstar @SQLHA @SWI_Database let’s face it. He drives a Lincoln because he GOT PAID!!! #datachat
LawrenceGarvin @DBArgenis @SQLRockstar @neiltyson  Pshaw.. NT is a cynic. #datachat. I’ve lost all faith in his opinions.
SWI_Database Q5: What are some common mistakes when it comes to rolling upgrades? #datachat
DBArgenis @jdanton @SQLRockstar @SQLHA @SWI_Database yep. I’ll use Enterprise Manager, sure…but for a fee. #datachat
wnylibrarian RT @jdanton: It’s always a bad sign when you walk into a shop and see the XP screensaver. #datachat
jdanton @DBArgenis @SQLRockstar @SQLHA @SWI_Database I even have an Access rate. #datachat
LawrenceGarvin @SWI_Database A5.. Not having a written and TESTED plan! #datachat
DBArgenis @SWI_Database NOT HAVING A PLAYBOOK! You need to be PREPARED for GOOD outcomes as well as when something goes WRONG #datachat
SQLRockstar .@DBArgenis @jdanton @SQLHA @SWI_Database See, I give the first touch of EM for free, but the 2nd one I charge. #datachat
SQLHA @SWI_Database Not thinking through the failover/failure situations, not testing the process, and assuming it will just work. #datachat
DBArgenis @SQLRockstar @jdanton @SQLHA @SWI_Database you #sqlcrackdealer #datachat
SQLRockstar RT @SWI_Database: Q5: What are some common mistakes when it comes to rolling upgrades? #datachat
SQLHA @SWI_Database And if using a cluster, understanding quorum. #datachat
shirleman RT @SWI_Database: Q5: What are some common mistakes when it comes to rolling upgrades? #datachat
mrdenny @SWI_Database A5: Not planning for failure! #datachat
jdanton @SWI_Database a5: being on an older version of windows that doesn’t support cluster aware updating. #datachat
SQLRockstar .@SWI_Database A5: Not having a rollback plan. Too many times I’ve seen the “we can’t roll back” excuse. #datachat
mrdenny @SQLRockstar you’re learning. #datachat
DBArgenis @SWI_Database I emphasize that you need to understand what to do if you need to rollback. Have scripts ready! #datachat
SWI_Database RT @DBArgenis: @SWI_Database I emphasize that you need to understand what to do if you need to rollback. Have scripts ready! #datachat
jdanton Pro tip: Always install SQL on the latest version of Windows. If your ISV tells you it needs to on an older version-they’re lying. #datachat
SWI_Database RT @jdanton: Pro tip: Always install SQL on the latest version of Windows. If your ISV tells you it needs to on an older version-they’re ly…
LawrenceGarvin @jdanton Or they haven’t actually tested their own product… <sigh> #datachat
DBArgenis @jdanton I would add “as long as that version of Windows Server has a start button!” LOL #datachat
SQLRockstar .@DBArgenis @SQLHA @jdanton @SWI_Database Don’t be dissin’ the QA, that’s Gert’s baby! #datachat
SQLRockstar RT @LawrenceGarvin: @jdanton Or they haven’t actually tested their own product… <sigh> #datachat
SQLHA @DBArgenis @jdanton That’s what Server Core is for 😛 #datachat
SWI_Database RT @mike_walsh @SWI_Database Chuck Norris. Sort of rugged, ugly, been around.. But good at what he’s typecast for & always around #datachat
DBArgenis @SQLRockstar @SQLHA @jdanton @SWI_Database Gert doesn’t care anymore 🙂 #datachat
DBABullDog @SWI_Database A5 not having the business involved in the upgrade validating thru entire process. #datachat
SQLRockstar RT @DBABullDog: @SWI_Database A5 not having the business involved in the upgrade validating thru entire process. #datachat
mike_walsh RT @jdanton: Pro tip: Always install SQL on the latest version of Windows. If your ISV tells you it needs to on an older version-they’re ly…
SQLHA @SQLRockstar @DBArgenis @jdanton @SWI_Database The old tools really did just work. Then they had to go F it up with .NET. 😉 #datachat
SQLHA @jdanton @mike_walsh Well, latest supported version of Windows for that version of SQL Server 🙂 #datachat
SWI_Database RT @DBABullDog: @SWI_Database A5 not having the business involved in the upgrade validating thru entire process. #datachat
mike_walsh RT @SQLHA: @jdanton @mike_walsh Well, latest supported version of Windows for that version of SQL Server 🙂 #datachat
SWI_Database Q6: Does virtualization make architecting a rolling upgrade solution easier, or harder? #datachat
LawrenceGarvin Did my Tweetdeck break? #datachat
SQLRockstar RT @SWI_Database: Q6: Does virtualization make architecting a rolling upgrade solution easier, or harder? #datachat
DBArgenis @LawrenceGarvin we copy you #datachat
mrdenny @SWI_Database A6: No difference. It’s all the same physical or virtual. #datachat
SQLRockstar @LawrenceGarvin Yes. #datachat
DBArgenis @SWI_Database well, IT DEPENDS. Some failover maneuvers can be finnicky when dealing with virtualized servers #datachat
SQLHA @SWI_Database @SQLRockstar You still need to deal with in guest. Unless you’re just upgrading the hypervisor, SSDD. #datachat
jdanton .@SWI_Database I’d say neutral. You have the ability to snapshot, but lose failover clustering at SQL level. #datachat
LawrenceGarvin @SWI_Database A6. Gotta be easier. For one, rollback via snapshots. Two, because VM gives you better testing ops. #datachat
SQLRockstar .@SWI_Database A6: It makes some solutions, like clustering, harder. You need to understand the tech. #datachat
SWI_Database RT @LawrenceGarvin: @SWI_Database A6. Gotta be easier. For one, rollback via snapshots. Two, because VM gives you better testing ops. #data…
mike_walsh @SWI_Database yes. #datachat.. With fools running the VM side? Harder.. Good vm folks? Different story.
SQLHA @LawrenceGarvin @SWI_Database Snapshots are a tricky subject with SQL VMs … #datachat
SQLRockstar RT @SQLHA: @LawrenceGarvin @SWI_Database Snapshots are a tricky subject with SQL VMs … #datachat
sqlstudent144 @mrdenny @SWI_Database We’ve used virtual to make copies & test upgrades. Can make life much easier. #datachat
DBArgenis @SQLHA @LawrenceGarvin @SWI_Database very much so #datachat
LawrenceGarvin @SQLHA @SWI_Database Yes, they are. #datachat
mike_walsh RT @mrdenny: @SWI_Database A6: No difference. It’s all the same physical or virtual. #datachat
SQLRockstar .@SQLHA @LawrenceGarvin @SWI_Database Yeah, snapshots are tricky because the term “snapshots” is overloaded. #datachat
DBArgenis Virtualization is awesome, very awesome, except when it’s not. #datachat
SQLRockstar RT @DBArgenis: Virtualization is awesome, very awesome, except when it’s not. #datachat
SQLHA @SQLRockstar @LawrenceGarvin @SWI_Database No, in how MS supports them for VMs with SQL. Terminology a whole other issue. #datachat
DBArgenis Now granted, nowadays a lot more systems can be fully virtualized – even Tier 1 workloads. That we can all agree on #datachat
tradney RT @DBArgenis: Now granted, nowadays a lot more systems can be fully virtualized – even Tier 1 workloads. That we can all agree on #datachat
SQLRockstar .@DBArgenis Agreed. #datachat
mike_walsh RT @SQLRockstar: .@SQLHA @LawrenceGarvin @SWI_Database Yeah, snapshots are tricky because the term “snapshots” is overloaded. #datachat
SWI_Database Wao. Thanks for another amazing #datachat…. Last Q tonigh: Q7: How could rolling upgrades have saved your bacon early in your career?
SQLHA @SWI_Database I would say not as much – backups moreso, but rolling upgrades, meh. #datachat
SWI_Database #insider RT @SQLHA: @SWI_Database Like the fact you rolled bacon in there 😉 #datachat
DBArgenis @SWI_Database I could have looked like a rockstar much earlier in my career 🙁 #datachat
SQLRockstar .@GEEQL @SQLHA @LawrenceGarvin @SWI_Database Where? #datachat
SWI_Database RT @jdanton: .@DBArgenis @SWI_Database Earlier in my career I didn’t have enough pull to get HA. #datachat
DBArgenis @jdanton the thing with HA is that once you demo it properly configured, it sells itself. #datachat
SQLRockstar RT @SWI_Database: Wao. Thanks for another amazing #datachat…. Last Q tonigh: Q7: How could rolling upgrades have saved your bacon early i…
SQLHA @DBArgenis @jdanton Until they ask how much it costs 🙂 #datachat
DBArgenis @SQLHA @jdanton well, y’know. It’s like a fancy car 🙂 #datachat
SQLRockstar .@SWI_Database Q7: Easy – database mirroring or snapshots would have helped with each and every major deployment. #datachat
SQLHA @DBArgenis @jdanton They really want the Porsche, but wind up with the Bug. Same auto group 🙂 #datachat
SWI_Database RT @SQLRockstar: .@SWI_Database Q7: Easy – database mirroring or snapshots would have helped with each and every major deployment. #datachat
SQLRockstar .@SWI_Database Q7: Lots of times we got “stuck” and had to press forward and make things work. #datachat
SQLSoldier RT @DBArgenis: @SWI_Database When I run into issues with Mirroring I just search for @SQLSoldier’s blog #datachat
DBArgenis @SQLRockstar yes, indeed. Mirroring would have made a lot of upgrades much, much simpler. cc/@SWI_Database #datachat
LawrenceGarvin @SWI_Database A7. Maybe today. My only real ‘upgrade’ was ’00 to ’05 in ’08. Did it on 1 physical box over a weekend. God Bless Me #datachat
SQLRockstar RT @LawrenceGarvin: @SWI_Database A7. Maybe today. My only real ‘upgrade’ was ’00 to ’05 in ’08. Did it on 1 physical box over a weekend. G…
SWI_Database RT @LawrenceGarvin: @SWI_Database A7. Maybe today. My only real ‘upgrade’ was ’00 to ’05 in ’08. Did it on 1 physical box over a weekend. G…
SQLHA @DBArgenis @SQLRockstar @SWI_Database I don’t know. Even back in the day, log shipping was very effective. #datachat
tradney Who needs upgrades, SQL2000 is awesome #datachat
SQLRockstar RT @tradney: Who needs upgrades, SQL2000 is awesome #datachat
SQLSoldier @SQLHA @DBArgenis @SQLRockstar @SWI_Database +1 for log shipping! #datachat
SQLRockstar RT @SQLSoldier: @SQLHA @DBArgenis @SQLRockstar @SWI_Database +1 for log shipping! #datachat
SQLHA @SQLSoldier @SQLRockstar @DBArgenis @SWI_Database Like I said, Clint Howard. He’s just always there. #datachat
tradney @jdanton @DBArgenis if it ain’t broke don’t fix it. #datachat
DBArgenis @tradney @jdanton unlike you, I believe if it’s unsupported it’s 100% broken. #datachat
SWI_Database Another awesome #datachat tonight! Special thanks to @DBArgenis @SQLRockstar – Look for the follow up article and upcoming webinar.
DBArgenis RT @SWI_Database: Another awesome #datachat tonight! Special thanks to @DBArgenis @SQLRockstar – Look for the follow up article and upcomin…
tradney @DBArgenis @jdanton we all agree there. #datachat
Eshbaugh RT @SWI_Database: Another awesome #datachat tonight! Special thanks to @DBArgenis @SQLRockstar – Look for the follow up article and upcomin…
SWI_Database More about Rolling Upgrades for #SQLServer? Join 11/19 webinar w/ @DBArgenis & @SQLRockstar  http://t.co/Dt3KhZrfKD #datachat
DBArgenis RT @SWI_Database: More about Rolling Upgrades for #SQLServer? Join 11/19 webinar w/ @DBArgenis & @SQLRockstar  http://t.co/Dt3KhZrfKD #data…
Eshbaugh RT @SWI_Database: More about Rolling Upgrades for #SQLServer? Join 11/19 webinar w/ @DBArgenis & @SQLRockstar  http://t.co/Dt3KhZrfKD #data…
DBArgenis @SWI_Database @SQLRockstar I promise the demos are simple and awesome! #datachat
patrick_luther @SWI_Database @DBArgenis @SQLRockstar Thanks!!  Like most great discussions, I now have more questions to investigate.  #datachat
SQLRockstar .@SWI_Database @DBArgenis #datachat http://t.co/WJygJPKNvq
kleegeek RT @SWI_Database: More about Rolling Upgrades for #SQLServer? Join 11/19 webinar w/ @DBArgenis & @SQLRockstar  http://t.co/Dt3KhZrfKD #data…
tradney @DBArgenis @jdanton I know a company who rolled out Win7 with XP running on a VM on those PC’s. Talk about progress. #datachat
DBArgenis RT @SQLRockstar: .@SWI_Database @DBArgenis #datachat http://t.co/WJygJPKNvq
SQLSoldier @tradney @DBArgenis @jdanton Also, if you have to run it on an old compatibility level, it’s broken. #datachat
SQLRockstar RT @SWI_Database: More about Rolling Upgrades for #SQLServer? Join 11/19 webinar w/ @DBArgenis & @SQLRockstar  http://t.co/Dt3KhZrfKD #data…
SQLSoldier RT @SWI_Database: Another awesome #datachat tonight! Special thanks to @DBArgenis @SQLRockstar – Look for the follow up article and upcomin…
SWI_Database One more thing..we started #systchat 11/18 @ 7:30 PM CT Topic: IT Systems Monit Guest host @standaloneSA > http://t.co/DKUFlEQCP4 #datachat
SQLRockstar RT @SWI_Database: One more thing..we started #systchat 11/18 @ 7:30 PM CT Topic: IT Systems Monit Guest host @standaloneSA > http://t.co/DK…
tradney @DBArgenis @jdanton do you consider extended support as still supported or only mainstream? SQL2005? #datachat
SWI_Database One more thing..we started #syschat 11/18 @ 7:30 PM CT Topic: IT Systems Monit Guest host @standaloneSA > http://t.co/DKUFlEQCP4 #datachat
LawrenceGarvin RT @SWI_Database: One more thing..we started #syschat 11/18 @ 7:30 PM CT Topic: IT Systems Monit Guest host @standaloneSA > http://t.co/DKU…
LawrenceGarvin @tradney @DBArgenis @jdanton ExtSupp only gets SecUpdates. If you need CSS/PSS, then don’t exceed Mainstream dates. #datachat
SQLRockstar RT @LawrenceGarvin: @tradney @DBArgenis @jdanton ExtSupp only gets SecUpdates. If you need CSS/PSS, then don’t exceed Mainstream dates. #da…
tradney @DBArgenis @LawrenceGarvin @jdanton best to stay as current as possible but working with third party apps makes that tough. #datachat
jdanton @tradney @DBArgenis @LawrenceGarvin I also think there’s a lack of guys in corp IT to push software vendors to adapt. #datachat
LawrenceGarvin @jdanton @tradney @DBArgenis Absolutely AGREE!! #1 problem with ISVs is that customers won’t stand up for themselves! #datachat
SQLRockstar Thanks to everyone for a great #datachat tonight. I’ll stick around for a bit if anyone has additional questions.
SWI_Database #bacon RT @SQLRockstar: Thanks to everyone for a great #datachat tonight. I’ll stick around for a bit if anyone has additional questions.
SWI_Database RT @DBArgenis: . @SQLRockstar I shall counter-attack: http://t.co/1wf4xI6xuy #datachat
kleegeek RT @SWI_Database: RT @DBArgenis: . @SQLRockstar I shall counter-attack: http://t.co/1wf4xI6xuy #datachat
Vishal_BI RT @SWI_Database: RT @DBArgenis: . @SQLRockstar I shall counter-attack: http://t.co/1wf4xI6xuy #datachat
LawrenceGarvin Was late to the game, but always enjoy hanging with #datachat. See ya’ll next time! And don’t forget #syschat next week!! 🙂
SQLRockstar So, here’s a question that didn’t make it to #datachat tonight. Anyone want to see? It’s like a DVD extra.
LawrenceGarvin @SQLRockstar Oh.. I love DVD extras….. gimme gimme! #datachat
SQLRockstar Q7: If you could do a rolling upgrade to yourself, what would it be and why? #datachat
sql_handle RT @LawrenceGarvin: @tradney @DBArgenis @jdanton ExtSupp only gets SecUpdates. If you need CSS/PSS, then don’t exceed Mainstream dates. #da…
TopWebiners RT @SWI_Database: More about Rolling Upgrades for #SQLServer? Join 11/19 webinar w/ @DBArgenis & @SQLRockstar  http://t.co/Dt3KhZrfKD #data…
SWI_Database RT @SQLRockstar: Q7: If you could do a rolling upgrade to yourself, what would it be and why? #datachat .
LawrenceGarvin @SQLRockstar I’d upgrade myself to a 36 hour waking day with 6 hrs of sleep so I could do 2x the work I do now. #datachat
SQLRockstar RT @LawrenceGarvin: @SQLRockstar I’d upgrade myself to a 36 hour waking day with 6 hrs of sleep so I could do 2x the work I do now. #datach…
SWI_Database RT @tameraclark: @SQLRockstar I would be 50 lbs lighter because I got rid of bloat ware #datachat
SQLHA @SWI_Database @SQLRockstar I would try to not sweat things that I know long term won’t matter. Hard to do that in the moment. #datachat
DBArgenis @SQLRockstar can I upgrade myself to Tesla? The dude, not the car. #datachat
SQLRockstar RT @DBArgenis: @SQLRockstar can I upgrade myself to Tesla? The dude, not the car. #datachat
SQLRockstar RT @SQLHA: @SWI_Database @SQLRockstar I would try to not sweat things that I know long term won’t matter. Hard to do that in the moment. #d…
LawrenceGarvin @SQLHA Great point Allan!!! #datachat
SQLRockstar OK, last one… Q8: If your could do a rolling upgrade on Star Wars prequels, what would you do first and why? #datachat
yannr RT @SQLRockstar: OK, last one… Q8: If your could do a rolling upgrade on Star Wars prequels, what would you do first and why? #datachat
DBArgenis @SQLRockstar KILL EFFIN JAR JAR #datachat
SWI_Database RT @SQLRockstar: OK, last one… Q8: If your could do a rolling upgrade on Star Wars prequels, what would you do first and why? #datachat
SQLRockstar RT @DBArgenis: @SQLRockstar KILL EFFIN JAR JAR #datachat
LawrenceGarvin @SQLRockstar Uhhhh.. there were prequels? #datachat
SQLHA @SQLRockstar @SWI_Database Make sure that George Lucas did not write the script. #datachat
SQLRockstar RT @LawrenceGarvin: @SQLRockstar Uhhhh.. there were prequels? #datachat
lutef1sk @SQLRockstar uninstall episode 1. Decommission server. No upgrade necessary. #datachat
SQLRockstar RT @lutef1sk: @SQLRockstar uninstall episode 1. Decommission server. No upgrade necessary. #datachat

Leave a Reply