March 31, 2008 at 12:31 pm
1. Can I upgrade from SQL 2000 32 bit to SQL Server 2005 64 bit on a Windows x64 bit machine?
2. Also can I upgrade from SQL Server 2005 32 bit to SQL Server 64 bit?
If so does anyone have a link or location where I can read about this?
Thanks
March 31, 2008 at 1:06 pm
I believe the answers are Yes and Yes. Start here:
http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx
That has what Microsoft has to say about the subject and how to go about doing it. (It's more of a marketing piece than a technical piece, but it's a good place to start anyway.)
(Edit: But I was wrong, as per the post below this one!)
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
March 31, 2008 at 1:17 pm
This is what I found from a little more digging.
Can I do an "in-place" upgrade on the x64 OS?
Well, it certainly has been awhile since my last blog. In that time we have seen several conferences come and go: PDC, PASS, and the HP Tech Forum (which I just got back from). At these conferences, Microsoft has laid out before us a lot of great knowledge --and even some breaking news (as in the case of database mirroring).
While at PASS, I took the opportunity to get an answer to a question that has plagued me for some time now. An increasingly common question I am getting when I am working at client sites is:
Will we be allowed to do a direct in-place upgrade of a 32-bit SQL 2000/sp4 instance running on an AMD Opteron server running the x64 operating system - - > to the x64 version of SQL 2005, or will customers "have to" use another method? One such methods is installing the x64 version of Yukon (2005) as a named instance, and then using the Copy Database Wizard (CDW) to bring the Shiloh (2000) 32-bit default instance's databases over to the x64 Yukon named instance.
I have seen this question asked in the private newsgroup and on Microsoft's internal DL previously, but no one from Microsoft has ever answered the question in a clear and concise manner. Though Books Online (BOL) does not indicate that an in-place upgrade of this nature is possible, the question still seems to hang out there in the user community, without being answered in a strong and clear manner. So I took it upon myself to see if we could get a straight up official word on this scenario from a setup/upgrade person, and finally put this question to rest.
The answer from the Microsoft SQL Server 2005 Release Team's Michael Raheem was a disappointing, NO. The in-place upgrade is only available for the same version bits. You can only upgrade from SQL Server 2000 32-bit to SQL Server 2005 32-bit and from SQL Server 2000 64-bit Itanium to SQL Server 2005 64-bit Itanium. A SQL Server 2000 32-bit to SQL Server 2005 64-bit x64 represents a "cross-bit" upgrade, and that is not supported. The upgrade path for x64 is the same as if the upgrade was from 32-bit to 64-bit Itanium.
Yet to be fair to people asking this question, I can understand their confusion. Prohibiting a "cross-bit" upgrade from 32-bit to 64-bit Itanium makes perfect sense since, 32-bit SQL could not be installed on the Itanium hardware in the first place, but the 32-bit version can installed on the x64 OS.
Unfortunately, to do a "cross-bit" upgrade on the same machine, you have to resort to one of the classic migration techniques that you would use if you were performing a two-machine upgrade such as; backup/restore, detach/attach, or using the Copy Database Wizard (CDW) to bring the Shiloh (2000) 32-bit instance's user databases over to an x64 Yukon instance.
March 31, 2008 at 1:19 pm
I am sorry when I said upgrade I meant and in-place upgrade.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply