October 31, 2007 at 3:48 am
Im busy doing a inplace upgrade from SQL 2000 32 bit std. to SQL 2005 64 bit Enterprise. I ran Adviser and resolved most of the issues but when i try and upgrade it tells me that my upgrade is blocked. This is the error messege.
Name: Microsoft SQL Server 2000
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Can anybody maybe give me some advice?
November 1, 2007 at 2:01 am
Ok Than let me just ask this...
Is it possible to do a inplace upgrade from 2000 32bit to 2005 64bit?:ermm:
November 1, 2007 at 2:30 am
Stephan,
NO you can't do an in-place upgrade from 32-bit to 64.What you can do is install a 64- bit instance next to your existing 32-bit instance and then dettach the databases from you old instance and attach them to the new instance. But keep in mind that all the objects which are kept in system databases like Logins, Linked Servers, Jobs, Operators, Alerts etc. must be transferred as well. You can use either DTS/SSIS or Scripts to do this.
Markus
[font="Verdana"]Markus Bohse[/font]
November 1, 2007 at 2:53 am
Hi Markus,
Thanx for the advice. The problem with doing a migration is that the scripts im running is using the 32 bit instance as the default instance. Is there a way to make the scripts use the new 64 bit instance as the default?
November 1, 2007 at 3:07 am
What kind of scripts are you talking about?
How do you execute them?
Are they containg hardcoded servernames or what exactly is your problem?
Of course when you use a different named instance you have to adjust connection strings and /or configuration files to point to the new instance. You could create a server alias with the old name in the network configuration tool but that will only work after the old instance has been stopped.
Markus
[font="Verdana"]Markus Bohse[/font]
November 1, 2007 at 3:22 am
Oh yeah... its hardcoded VB aplications.
November 2, 2007 at 4:14 am
There has been a lot of discussion in various forums about the merits of doing either an in-place upgrade or a new install. Most people who have done a number of upgrades highly recommend doing a new install. Google will find many references for this.
I have done some in-place upgrades and some have worked OK, but some have failed leaving SQL totally unusable even where the Windows and SQL builds have been apparently identical. If your upgrade fails you have no choice but to uninstall SQL and start from scratch, but if you have not prepared for this then your Logins, DTS, etc, etc in the system databases are lost.
I strongly advise you uninstall SQL 2000 and do a clean install of SQL 2005. You will need to script out all Logins jobs, DTS, etc from SQL 2000 and load them into SQL 2005, but this is the safest thing to do. This way you also get completely standard file names and registry entries, and a SQL instance that will work as designed.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy