May 29, 2015 at 8:52 am
Last night, I applied (successfully according to the UI) SP1 to a default SQL 2008 R2 instance. When I rebooted the server, the SQL service would not stay started (no errors and it would start and stop 5 seconds later). Checked error logs and discovered the master db had been corrupted (no system database backups - not my server/system). Tried using the setup bootstrap utility w/the "/action=rebuilddatabase" switch and that ran - error free, but was still unable to start the service and keep it running. 2 hours later, I was able to get SQL running again using the "-T902" switch on the service in the SQL configuration manager's additional parameters for the service. My understanding is this switch just bypasses the upgrade scripts on the system databases. SSMS now indicates it's on 10.50.2500.0 (SP1), but I'm sure it can't keep running on that "-T902" switch and I still need to apply SP2 and SP3.
Any thoughts or ideas on what my next steps should be or how to start the service normally? Thanks in advance!
May 29, 2015 at 9:21 am
You have to figure out what's wrong in the upgrade script and fix it. There's no other way around it. Your ERRORLOG should show you what's wrong.
-- Gianluca Sartori
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply