Downgrade Install Plan

We are upgrading an application that is not yet supported on SQL Server 2005. The upgrade involves new hardware (including a new sql server). Any gotchas or advice regarding this plan:

1. Install Windows 2003 64 bit, configure hardware appropriately for running SQL Server.

2. Install SQL Server 2000 64 bit using the 2005 license key (is that how you 'downgrade'? I didn't see a 'how-to' article regarding this).

3. Restore backups of system databases from current SQL Server to new SQL Server (note: current SQL Server is running 32 bit - I realize that I need to make sure that I have the same service pack on the new server as that on the current server).

4. Apply sp4.

5. Restore user databases.

Not sure if the 32 vs. 64 bit thing is of any concern or if 'downgrading' is as simple as this.

Thanks!

Michelle

1. What is the version of current SQL Server? SQL Server 2005 requires SP1 for Windows 2003 Enterprise Edittion on x64 machines.

2. I do not think you can install SQL Server 2000 with SQL Server 2005 product key.

The following issues are clear.

1. SQL Server 2000 and SQL Server 2005 can be installed side by side successfully.

2. 32-bit SQL Server 2000/2005 can be installed side by side successfully on x64 machines.

3. 32-bit SQL Server 2005 and 64-bit SQL Server 2005 can be installed successfully on x64 machines.

|||I did talk to our Microsoft Solution Specialist and he explained that

we should already have the required license and media to install SQL

Server 2000 with our most recent media kit shipment. I don't think that

I will be prompted for a license key at all.

I'm hoping that the server admin team will be finished with the

hardware/os in the next couple of days so that I can start on my

portion. I'll document any issues that I have.

Thanks,

Michelle|||

Michelle,

Did you have any problems with your original installation plan? We are trying to do the same installation and it is unclear how to install 2000 with 2005 disks and keys. There is no prompting on install.

|||I did not have any problems but in hindsight had wished that I had

installed SQL Server 2005 as the default instance and 2000 as a named

instance. I believe that this would have made the upgrade to 2005

simpler. We have since built other machines this way.

Downgrade Install Plan

We are upgrading an application that is not yet supported on SQL Server 2005. The upgrade involves new hardware (including a new sql server). Any gotchas or advice regarding this plan:

1. Install Windows 2003 64 bit, configure hardware appropriately for running SQL Server.

2. Install SQL Server 2000 64 bit using the 2005 license key (is that how you 'downgrade'? I didn't see a 'how-to' article regarding this).

3. Restore backups of system databases from current SQL Server to new SQL Server (note: current SQL Server is running 32 bit - I realize that I need to make sure that I have the same service pack on the new server as that on the current server).

4. Apply sp4.

5. Restore user databases.

Not sure if the 32 vs. 64 bit thing is of any concern or if 'downgrading' is as simple as this.

Thanks!

Michelle

1. What is the version of current SQL Server? SQL Server 2005 requires SP1 for Windows 2003 Enterprise Edittion on x64 machines.

2. I do not think you can install SQL Server 2000 with SQL Server 2005 product key.

The following issues are clear.

1. SQL Server 2000 and SQL Server 2005 can be installed side by side successfully.

2. 32-bit SQL Server 2000/2005 can be installed side by side successfully on x64 machines.

3. 32-bit SQL Server 2005 and 64-bit SQL Server 2005 can be installed successfully on x64 machines.

|||I did talk to our Microsoft Solution Specialist and he explained that we should already have the required license and media to install SQL Server 2000 with our most recent media kit shipment. I don't think that I will be prompted for a license key at all.
I'm hoping that the server admin team will be finished with the hardware/os in the next couple of days so that I can start on my portion. I'll document any issues that I have.
Thanks,
Michelle
|||

Michelle,

Did you have any problems with your original installation plan? We are trying to do the same installation and it is unclear how to install 2000 with 2005 disks and keys. There is no prompting on install.

|||I did not have any problems but in hindsight had wished that I had installed SQL Server 2005 as the default instance and 2000 as a named instance. I believe that this would have made the upgrade to 2005 simpler. We have since built other machines this way.

Does the Sql Server 2005 EVAL distribution support run of packages under DtExec?

I believe I have made a complete install of Sql Server 2005 on my dev. machine, including all client tools, and can run SSIS packages from the dev. environment.

However DtExec refuses to run any package and always throws the "insufficient version" error (as does the "RunPackage" component, probably for the same reason).

I have repeatedly attempted to find something more to install from the Sql Server 2005 eval release that will allow DTExec to run without the "insufficient version" error, but can find nothing else to install from the eval. The install wizard (and the "change" wizard) indicates everything is installed and will not build a list of any additional components to install.

Are we sure that DtExec will install and run from a sql server 2005 eval distribution?

Licenses are in the pipeline (not that pipleine) but we need to start testing our SSIS solution in the meantime.

p.s. Kudos to the dev. team, it really is an excellent tool!

Thanks,

Ken

This sounds like the SSIS services feature is missing, you may just have the workstation components. If running on a workstation OS, then this can be an issue-

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=112469&SiteID=1

|||

Thanks for the reply Darren.

The O.S. is Windows 2000 Advanced Server, and to the best of my ability I have confirmed and reconfirmed that every possible installable component and piece of software provided in the Sql Server 2005 eval. distro. has been fully installed in the runtime environment in question.

I recently used the same Sql Server 2005 distro. to perform an identical install onto an XP Pro machine and DtExec seems to run fine.

So I will assume I have some kind of flawed installation on the win2k advanced server box and will try a complete deinstall and reinstall as my last resort.