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

WS2008 R2 in place upgrade and SQL Server 2008 R2 gotchas? Expand / Collapse
Author
Message
Posted Tuesday, December 31, 2013 3:54 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, April 14, 2014 8:08 AM
Points: 12, Visits: 190
Hi,

We have a server that needs more memory but we've hit the 32GB limit imposed by Windows Server 2008 R2 Standard. We plan to perform an in place upgrade which the infrastructure team tell me is quick and easy (command line and a reboot) and a memory upgrade at the same time.

I was just wondering if anyone here had performed such an upgrade and if any side effects or gotchas were noticed with regards to SQL Server.

Just to confirm, the server is running Windows Server 2008 R2 standard and SQL Server 2008 R2 standard.

Thanks in advance,

G.
Post #1526714
Posted Thursday, January 02, 2014 9:15 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: 2 days ago @ 9:15 AM
Points: 604, Visits: 481
I have not done this. If it's a virtual, I'd take a backup prior to doing this upgrade... In theory it would work. It's not something I'd do with my production database without having a fail over node / DR site or a good recovery plan.

.
Post #1527181
Posted Thursday, January 02, 2014 9:43 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, April 14, 2014 8:08 AM
Points: 12, Visits: 190
Hi, thanks for your response.

Unfortunately it's not virtual. Would be nice to have that sort of safety net.

I think I'm going to have to just take the plunge here and hope for the best. I have tried an in place upgrade on as close to a comparable setup as I could and there were no issues that became apparent during testing.

Fingers crossed I guess.

Thanks again,

G.
Post #1527194
Posted Thursday, January 02, 2014 9:54 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: 2 days ago @ 9:15 AM
Points: 604, Visits: 481
Please let us know, I'm rather curious. Also, I would restore a copy of your backups to verify they're good and shut down SQL by hand prior to the install just to help prevent anything from going wrong.

.
Post #1527202
Posted Friday, January 03, 2014 3:14 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:04 AM
Points: 5,970, Visits: 12,865
Ginga (12/31/2013)
Hi,

We have a server that needs more memory but we've hit the 32GB limit imposed by Windows Server 2008 R2 Standard. We plan to perform an in place upgrade which the infrastructure team tell me is quick and easy (command line and a reboot) and a memory upgrade at the same time.

I was just wondering if anyone here had performed such an upgrade and if any side effects or gotchas were noticed with regards to SQL Server.

Just to confirm, the server is running Windows Server 2008 R2 standard and SQL Server 2008 R2 standard.

Thanks in advance,

G.

Changing the edition of the OS is fairly painless, full in place upgrades such as 2003 R2 to 2008 R2, etc have more scope for errors. Are changing just the edition?


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1527417
Posted Friday, January 03, 2014 3:19 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, April 14, 2014 8:08 AM
Points: 12, Visits: 190
Hi,

Yes, it's just a Standard to Enterprise edition change. The test I performed went very well so I'm reasonably confident that it will go smoothly but it's always handy to seek other DBA opinions.

Thanks for taking the time to respond.

G.
Post #1527419
Posted Friday, January 03, 2014 4:28 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:04 AM
Points: 5,970, Visits: 12,865
the only time i would be shaky would be a major platform change, for instance in place upgrade from Windows 2003 Std to Windows 2008 R2 Std, etc

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1527449
Posted Monday, January 06, 2014 8:00 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, April 14, 2014 8:08 AM
Points: 12, Visits: 190
Just thought I'd close this one off.

The in place upgrade went ahead this weekend just gone and it was a simple, albeit lengthy process. I decided to shut down SQL Server for the process, but it came back up with no negative effects and has been functioning well since with a considerable amount more memory :).

Just to confirm this was an in place upgrade to Windows Server 2008 R2 Enterprise from standard. The server is running SQL Server 2008 R2. Single box, no HA/Clustering solution and no issues.

Thanks to all who viewed and offered their thoughts.

G
Post #1528105
Posted Monday, January 06, 2014 8:02 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: 2 days ago @ 9:15 AM
Points: 604, Visits: 481
I'm glad it worked for you. Also, Thanks for responding with how it went. Most times it seems, a response is given and no confirmation of the results. ^.^

.
Post #1528106
Posted Monday, January 06, 2014 11:17 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:04 AM
Points: 5,970, Visits: 12,865
Ginga (1/6/2014)
Just thought I'd close this one off.

The in place upgrade went ahead this weekend just gone and it was a simple, albeit lengthy process. I decided to shut down SQL Server for the process, but it came back up with no negative effects and has been functioning well since with a considerable amount more memory :).

Just to confirm this was an in place upgrade to Windows Server 2008 R2 Enterprise from standard. The server is running SQL Server 2008 R2. Single box, no HA/Clustering solution and no issues.

Thanks to all who viewed and offered their thoughts.

G

Pretty much as I expected, thanks for the update


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1528199
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse