October 24, 2011 at 8:14 am
Hi Everyone..
Hope all is well
I am planning on scheduling an upgrade of SQL Server 2008 Standard Edition to SQL Server 2008 R2 Standard Edition. I am doing this for my production environment. My question is should I go with in-place upgrade or side-by-side upgrade? which is the better option?
If I go with in-place should I still take a full backup of all my databases before the upgrade?
Thanks much for your inputs.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
October 24, 2011 at 8:21 am
Whichever method you will eventually choose, it is always recommended to take a back up of all the DB. I prefer migrating to another server since there is a good and easy rollback plan.
-Roy
October 24, 2011 at 12:06 pm
Hi,
I was trying to do an in place upgrade on my test environment but ended up with the following errors:
Error:
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Event Viewer Logs:
Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 598, state 1, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
I am sure that the sa login has not been renamed or locked out for security purposes. Currently I am only able to get into SSMS with DAC. I have also verified the data root, default data and log file paths in the registry and they all look good. Any ideas how to get rid of them.
Thanks in advance
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
October 24, 2011 at 12:33 pm
It recommends looking at previous entries in the error log for more details. Anything there?
- 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
October 24, 2011 at 12:47 pm
I think I know this error...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2011 at 2:15 pm
Thanks for the info Gail. The default log file path was incorrect. Its now upgraded to R2.
Thanks again everyone.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
October 24, 2011 at 2:28 pm
Sapen (10/24/2011)
Thanks for the info Gail. The default log file path was incorrect. Its now upgraded to R2.
Intereting. Not the same error. Glad the info helped (if it did)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply