Search results for query: *

Spend 8 hours last firday to get this server up & running again. Modifying the registry went well but didn't solve the problem. So I tried the re-install option but that reulted in a error and after that I couldn't get the server online again. No other option than to hop in the car and drive...

>>sp_addserver and sp_dropserver << I'm not sure but I think this is what got me into this trouble. I simulated a server rename at home and all went well. But in production, a colleague ran these two SP's and after that, the trouble began. >>If it detects the machine name has changed then it...

I don't get this. Re-installing doesn't really re-install? I could imagine an intelligent installation that doesn't overwrite same or newer files. But since a servicepack is applied to the original installation I doubt if this will work well? But then again, if syncing the name is all it does...

Re-installing is not my favorite option. The I would go back 3 servicepacks and then re-apply the servicepack. My current strategy is nog to modify the registry by hand to replace all occurrences of OLD to NEW. There are still quite a few entries referring to the old name. I have no idea if...

We had a problem free SQL Server 200 running on a machine call OLD with the instance of SLIM. I could connect the enterprise manager to OLD\SLIM and everything worked fine. The the name OLD was changed to NEW and the problems began. The server is still running and users can connect without...