Just a ‘thank you’ note to Stephen, Manish and crew for the MSSql11 migration last night - seems to have gone flawlessly from my perspective and am very happy that its getting new hardware; hoping some of the ‘ghosts in the machine’ that seem to appear for me on this server can finally rest in peace!
now view from the inside
It actually looked like we’d have it up 5 minutes early, (before 4am) as we had data copied across, but there was an issue in started the SQL server. had to debug and get it fixed. I was glad at that point we posted the delay as it took a little longer than I’d hoped.
Overall it went extremely well, and was a very successful migration process. I certainly can’t complain, and some good education along the way for Manish and the other windows staff.
With the changes I was making, I knew there was some chance data could be corrupted on user DBs, so I had to stop at 4am and take a backup on the new server, I knew that it woudl be faster than moving anything else from the old server again. It took just 12 minutes to backup what we’d spent around 4 hours moving 
Well almost flawless it seems. 
Am encountering one issue post-upgrade (ticket HKQ-54880-713) -I knew it seemed to go a little too smoothly from my end!
I have put it on hold while I investigate this, odd one. I have a few errands to run right now however. This one at least is not a show stopper.
Yup, not a huge problem (and part of the learning experience I guess). No big rush Stephen.
We’ve been ‘bitten’ by a new SQL 2005 ‘feature’
Rename a Computer That Hosts a Stand-Alone Instance of SQL Server - SQL Server | Microsoft Learn
it doens’t auto detect like MSSQL 2000 and prior did.
posted scheduled restart of service.
Ahhh, learn something new again. Thanks Stephen.
got to bookmark this one, looks important for the future.
Should be in good shape now!
Things seem AOK now, thanks again!