February 22, 2010 at 9:42 am
Hi all,
I have a single node cluster with 1 x sql instance. I amended the start up parameters, incorrectly, via sql config manager so SQL would not start.
I went in & changed the parameters to be correct, but the change won't persist. Every time I try to start SQL again, the incorrect change is automatically written back to the start up parameters (& the reg)
I have tried the following:
Amending via the registry
Amending via SQL config manager
starting via cmd line sqlserver.exe ...
net start & net stop
I can start SQL with the cmd line options but cannot get the parameter changes to stay in place and I cannot start SQL via the cluster or service.
I read this, which sounds like the problem, but the solution does not work for me.
Any ideas?
SQL 25K
Thanks in advance!!
February 22, 2010 at 9:54 am
Aha, this DOES work:
amend params via registry
net start mssqlserver
start sql via cluadmin.exe
stop via cluadmin.exe & start again
changes will persist.
sorry to bother, hope this helps someone.
March 15, 2010 at 4:43 am
This pretty much worked for me though i had to reset the registry entry again before stopping and starting SQL in cluadmin.exe.
October 20, 2011 at 12:26 pm
Apparently this is due to Checkpointing - and MS have an official workaround. Although I still think baby_cheeses method involves far less hacking around.
Rachel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply