January 10, 2006 at 7:01 pm
Hi there,
Just wanting to sap off someone's experiences - when doing a side by side migration (ie have SQL2000 installed, install SQL2K5 as a seperate instance), does the 2005 install make any changes whatso ever to the operations/configuration/etc of your SQL2000 install?
I am thinking and hopeing not - but keen to hear peoples experiences before going ahead with this.
Cheers
Troy
January 11, 2006 at 11:37 am
Troy,
I tried to install SQL Server 2005 Standard Edition on my Windows XP SP1 workstation. First it told me to install IIS, which I did. Then it told me to install SP2, which I did too.Then I got a blue screen with STOP error during the reboot. I looked up this particular stop error, there are many reasons including that it could happen when older Visual basic files are conflicting with newer versions of the same files. See
http://www.kbalertz.com/Feedback.aspx?kbNumber=330314
My workstation was loaded with misc. older stuff as well as newer stuff.
Essentially what I am trying to say: Does your computer meets the pre-requisites for 2005? Do you run anything that is really old on your system? Then I would not do it if it is a production system or you have to ensure the computer is backed up well
Regards,Yelena Varsha
January 11, 2006 at 12:35 pm
Thanks Yelena for the response,
Our server is currently 2003std, service packed/patched and is currently running IIS and only SQL2000std. Nothing else.
Sounds as though hopefully this could be a good candidate for the side by side migration then - but I have to admit your blue screen doesn't inspire confidence, as this is a production server, so if it turns it's toes up, it may mean some rather heated conversations
*gulp*
Thanks
Troy
January 11, 2006 at 1:49 pm
Troy,
why don't you test first even if on your workstation?
For the production box: perform ASR backup and full file system backup after SQL database backup.
Regards,Yelena Varsha
January 15, 2006 at 7:36 pm
Hi Ya,
Thanks for the responses, I had been testing SQL2K5 on a seperate machine - but not a side by side scenario - sort of dumb considering this is what we ended up doing.
So I started again and installed side by side in test - all looked fine and functional which is good, so did the same in live, and again everything is all good....
Until I got this message:
DTSRun.exe - Unable To Locate Component : This application has failed to start because SqlResourceLoader.dll was not found. Re-installing the application may fix this problem
However a simple reboot resolved this - although not ideal in a production environment it was a minor hickup.
Just in case anyone has a similar question/issue in the future.
Cheers
Troy
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply