Downgrade SQL 2005 Entreprise to Workgroup Edition ?

Hi

I have the following problem :

I have licensed a german version of sbs 2003 premium. With the upgrade to sbs 2003 r2, I will buy the rights to use the sql 2005 workgroup edition. But the german sbs 2003 r2 is not available by now.

I could go in production with the sql 2005 trial, this is an entreprise edition.

My question is : can I downgrade the sql server 2005 from this trial edition (entreprise) to the workgroup edition ? Is it possible ? easy ? any recommendations ?

Many thanks !

Ferrarirosso

You can upgrade Trial SQL Server 2005 to Workgroup edition but it must happen before the trial edition expires.

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.

Don't delete data from linkedserver table .

when our system upgrade to sql server 2005 ,and create a linked server to localhost database , the script of create linkedserver is :

/****** Object: LinkedServer [localhost_boston] Script Date: 05/07/2006 18:37:15 ******/
EXEC master.dbo.sp_addlinkedserver @.server = N'localhost_boston',@.srvproduct='', @.provider=N'SQLNCLI', @.datasrc=N'localhost', @.provstr=N'UID=sa;PWD=007;', @.catalog=N'boston'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'collation compatible', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'data access', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'dist', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'pub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'rpc', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'rpc out', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'sub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'connect timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'collation name', @.optvalue=null
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'lazy schema validation', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'query timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'use remote collation', @.optvalue=N'true'

when I run the sql on local server :

delete a from localhost_boston.boston.dbo.Spot as a,
bica.tmpspot as b where a.spotid=b.spotid

it display 7 rows have deleted ,but when I run:

select * from localhost_boston.boston.dbo.Spot as a
join bica. tmpspot as b on a.spotid=b.spotid

find the 7 rows have not delete,I check the localhost_boston.boston.dbo.Spot

table ,and find 7 rows have deleted that it is not a.spotid=b.spotid ,why ?

If I run :

delete from localhost_boston.boston.dbo.Spot where spotid=28147

and the row can deleted .why ?

anyone can talk me how to do I can !

Thanks.

Your delete syntax is improper. You should use a subquery to constrain your deleted rows, not a join.

Code Snippet

delete localhost_boston.boston.dbo.Spot where spotid in (select spotid from bica.tmpspot)

Joins create a result set and using a generic join syntax you can get unexpected result sets. Always test your joins in a select statement 1st to make sure you are getting the results you expect.

Don't delete data from linkedserver table .

when our system upgrade to sql server 2005 ,and create a linked server to localhost database , the script of create linkedserver is :

/****** Object: LinkedServer [localhost_boston] Script Date: 05/07/2006 18:37:15 ******/
EXEC master.dbo.sp_addlinkedserver @.server = N'localhost_boston',@.srvproduct='', @.provider=N'SQLNCLI', @.datasrc=N'localhost', @.provstr=N'UID=sa;PWD=007;', @.catalog=N'boston'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'collation compatible', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'data access', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'dist', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'pub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'rpc', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'rpc out', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'sub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'connect timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'collation name', @.optvalue=null
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'lazy schema validation', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'query timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'localhost_boston', @.optname=N'use remote collation', @.optvalue=N'true'

when I run the sql on local server :

delete a from localhost_boston.boston.dbo.Spot as a,
bica.tmpspot as b where a.spotid=b.spotid

it display 7 rows have deleted ,but when I run:

select * from localhost_boston.boston.dbo.Spot as a
join bica. tmpspot as b on a.spotid=b.spotid

find the 7 rows have not delete,I check the localhost_boston.boston.dbo.Spot

table ,and find 7 rows have deleted that it is not a.spotid=b.spotid ,why ?

If I run :

delete from localhost_boston.boston.dbo.Spot where spotid=28147

and the row can deleted .why ?

anyone can talk me how to do I can !

Thanks.

Your delete syntax is improper. You should use a subquery to constrain your deleted rows, not a join.

Code Snippet

delete localhost_boston.boston.dbo.Spot where spotid in (select spotid from bica.tmpspot)

Joins create a result set and using a generic join syntax you can get unexpected result sets. Always test your joins in a select statement 1st to make sure you are getting the results you expect.