Migrating a single SQL2K Install to a SQL Clustered install.

Is it possible to to migrate a single standalone installation of SQL 2000
Enterprise Edition to be part of a clustered SQL installation. My initial
guess is that as SQL installs by default registering to the Server IP
address, and a clustered install requires its own IP address to be installed
under. Therefore I would have to unistall any SQL install and start from
scratch?
Thanks
Hi
You are correct, you first ahve to un-install and re-install. No other way.
Regards
Mike
"Siz Choudhury" wrote:

> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be installed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks
|||Be sure to back up all of your databases, so can restore them to the
cluster..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Siz Choudhury" <Siz Choudhury@.discussions.microsoft.com> wrote in message
news:E14A249A-0E2B-467D-80B6-BFCDE8B9C778@.microsoft.com...
> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be
installed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks
sql

Migrating a single SQL2K Install to a SQL Clustered install.

Is it possible to to migrate a single standalone installation of SQL 2000
Enterprise Edition to be part of a clustered SQL installation. My initial
guess is that as SQL installs by default registering to the Server IP
address, and a clustered install requires its own IP address to be installed
under. Therefore I would have to unistall any SQL install and start from
scratch?
ThanksHi
You are correct, you first ahve to un-install and re-install. No other way.
Regards
Mike
"Siz Choudhury" wrote:
> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be installed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks|||Be sure to back up all of your databases, so can restore them to the
cluster..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Siz Choudhury" <Siz Choudhury@.discussions.microsoft.com> wrote in message
news:E14A249A-0E2B-467D-80B6-BFCDE8B9C778@.microsoft.com...
> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be
installed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks

Migrating a single SQL2K Install to a SQL Clustered install.

Is it possible to to migrate a single standalone installation of SQL 2000
Enterprise Edition to be part of a clustered SQL installation. My initial
guess is that as SQL installs by default registering to the Server IP
address, and a clustered install requires its own IP address to be installed
under. Therefore I would have to unistall any SQL install and start from
scratch?
ThanksHi
You are correct, you first ahve to un-install and re-install. No other way.
Regards
Mike
"Siz Choudhury" wrote:

> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be install
ed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks|||Be sure to back up all of your databases, so can restore them to the
cluster..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Siz Choudhury" <Siz Choudhury@.discussions.microsoft.com> wrote in message
news:E14A249A-0E2B-467D-80B6-BFCDE8B9C778@.microsoft.com...
> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be
installed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks

Migrate SQL 2000 to New SQL 2005 Installation.

Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.

1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost

2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?

Thanks for any assistance with this!

Start by running the SQL Server 2005 upgrade advisor against your SQL 2000 installation. This will give you good information on problems that you might need to address. Also, if your applications are purchased, check with the vendors for advice on compatibility. But the bottom line is that every application is unique and the only way you'll know for sure is by carefully testing.

Sorry, I don't know the answer to your question on mirroring.

Paul

|||Thanks for the response Paul, Doesn't the upgrade advisor only tell me info in regards to actually upgrading the database? I'm looking at keeping them at 8.0 compatibility on SQL 2005. Basically, I'm looking at keeping the databases at the SQL2000 level on a SQL2005 box. I guess my real question is: Are databases that are running in SQL2000 compatibility mode on a SQL2005 box fully backwards compatible?|||

Most applications will upgrade with no problems but there are a small number of breaking changes in 9.0, even if you stay in 8.0 compat mode. Look up "compatibility" and "sp_dbcmptlevel" in BOL for details.

|||

hi Tynman

Yes u can always keep SQL2000 database compatibility level i.e. 80 in sql 2005 by specifying compatibility level in system stored procedure "sp_dbcmptlevel" and give compatibility level as 80 with database name.

Ur command will be: sp_dbcmplevel dbname, 80

|||

BUMP!

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode (compatibility level 80)?

Do anyone have an answer to this question?

|||I am trying to restore a SQL 2005 DB into SQL 2000 and it errors out "too many objects on 64 allowed......blah..blah..blah.." something to that effect.

Migrate SQL 2000 to New SQL 2005 Installation.

Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.

1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost

2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?

Thanks for any assistance with this!

Start by running the SQL Server 2005 upgrade advisor against your SQL 2000 installation. This will give you good information on problems that you might need to address. Also, if your applications are purchased, check with the vendors for advice on compatibility. But the bottom line is that every application is unique and the only way you'll know for sure is by carefully testing.

Sorry, I don't know the answer to your question on mirroring.

Paul

|||Thanks for the response Paul, Doesn't the upgrade advisor only tell me info in regards to actually upgrading the database? I'm looking at keeping them at 8.0 compatibility on SQL 2005. Basically, I'm looking at keeping the databases at the SQL2000 level on a SQL2005 box. I guess my real question is: Are databases that are running in SQL2000 compatibility mode on a SQL2005 box fully backwards compatible?|||

Most applications will upgrade with no problems but there are a small number of breaking changes in 9.0, even if you stay in 8.0 compat mode. Look up "compatibility" and "sp_dbcmptlevel" in BOL for details.

|||

hi Tynman

Yes u can always keep SQL2000 database compatibility level i.e. 80 in sql 2005 by specifying compatibility level in system stored procedure "sp_dbcmptlevel" and give compatibility level as 80 with database name.

Ur command will be: sp_dbcmplevel dbname, 80

|||

BUMP!

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode (compatibility level 80)?

Do anyone have an answer to this question?

|||I am trying to restore a SQL 2005 DB into SQL 2000 and it errors out "too many objects on 64 allowed......blah..blah..blah.." something to that effect.sql

Migrate SQL 2000 to New SQL 2005 Installation.

Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.

1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost

2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?

Thanks for any assistance with this!

Start by running the SQL Server 2005 upgrade advisor against your SQL 2000 installation. This will give you good information on problems that you might need to address. Also, if your applications are purchased, check with the vendors for advice on compatibility. But the bottom line is that every application is unique and the only way you'll know for sure is by carefully testing.

Sorry, I don't know the answer to your question on mirroring.

Paul

|||Thanks for the response Paul, Doesn't the upgrade advisor only tell me info in regards to actually upgrading the database? I'm looking at keeping them at 8.0 compatibility on SQL 2005. Basically, I'm looking at keeping the databases at the SQL2000 level on a SQL2005 box. I guess my real question is: Are databases that are running in SQL2000 compatibility mode on a SQL2005 box fully backwards compatible?|||

Most applications will upgrade with no problems but there are a small number of breaking changes in 9.0, even if you stay in 8.0 compat mode. Look up "compatibility" and "sp_dbcmptlevel" in BOL for details.

|||

hi Tynman

Yes u can always keep SQL2000 database compatibility level i.e. 80 in sql 2005 by specifying compatibility level in system stored procedure "sp_dbcmptlevel" and give compatibility level as 80 with database name.

Ur command will be: sp_dbcmplevel dbname, 80

|||

BUMP!

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode (compatibility level 80)?

Do anyone have an answer to this question?

|||I am trying to restore a SQL 2005 DB into SQL 2000 and it errors out "too many objects on 64 allowed......blah..blah..blah.." something to that effect.

Migrate from Single-Server to Cluster

I have a SharePoint installation that currently uses a single SQL Server and
connects to the default instance. I want to migrate to a cluster without
doing a full backup/move/restore. I'm thinking if I set up the cluster with
the same name as the current SQL server it should be transparent to
SharePoint. Has anyone tried this?
This is not a good idea, not even a great one. SPS can get picky. I would
due a true migration, with a tested backup/restore, then move the DB's.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Milan Gross" <MilanGross@.discussions.microsoft.com> wrote in message
news:19F19F3B-7721-4301-9303-B7ECF518B4A2@.microsoft.com...
>I have a SharePoint installation that currently uses a single SQL Server
>and
> connects to the default instance. I want to migrate to a cluster without
> doing a full backup/move/restore. I'm thinking if I set up the cluster
> with
> the same name as the current SQL server it should be transparent to
> SharePoint. Has anyone tried this?

Microsoft SQL Server Upgrade Wizard

I need to convert from SQL Server 7 to 2000 and I have the 2000 installation
media - but where do I find the Microsoft SQL Server Upgrade Wizard ? Is it
included in the installation cd? or do I need to get a different product?Are you installing on a new server or upgrading an existing SQL 7 box?
In either case, you should have the option to install the upgrade wizard =
during the installation.
Moving databases from SQL7 to SQL2k is easy -- simply back them up and =
restore them to the 2k box. Note: it is not possible to go the other =
way! (at least not with BACKUP and RESTORE).
--=20
Keith
"confused" <anonymous@.discussions.microsoft.com> wrote in message =
news:44F65E3A-8EC2-45C5-8E1B-23B9868DF4D1@.microsoft.com...
> I need to convert from SQL Server 7 to 2000 and I have the 2000 =
installation media - but where do I find the Microsoft SQL Server =
Upgrade Wizard ? Is it included in the installation cd? or do I need to =
get a different product?

Microsoft SQL Server Setup Support Files (English) -- Installation failed

I'm trying in vain to upgrade sql server 2000 to 2005 with great headache and pain.

I (finally) have removed all Beta, and other incompatible version of .NET, Visual Studio and any other offending components, and made it to the first page of the install shield.

The .NET 2.0 components installed fine - but I get a fatal error trying to install the SQL Server Set Support Files.

I do have a log file - and have tired searching on the various error codes in it, but am coming up blank. Please advise - this is taking forever!

sample of error msgs in log file:

MSI (s) (B0:E0) [12:33:06:613]: Note: 1: 1935 2: 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.NetEnterpriseServers.ExceptionMessageBox,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:613]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.

MSI (s) (B0:E0) [12:33:06:613]: Executing op: ComponentRegister(ComponentId={52723CBD-3400-458C-988A-4D012E6CAEDB},KeyPath=<\Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:629]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:E0) [12:33:06:629]: Assembly Error:Function not defined in specified DLL.

MSI (s) (B0:E0) [12:33:06:629]: Note: 1: 1935 2: {52723CBD-3400-458C-988A-4D012E6CAEDB} 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:629]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}

Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
MSI (s) (B0:E0) [12:33:06:629]: User policy value 'DisableRollback' is 0
MSI (s) (B0:E0) [12:33:06:629]: Machine policy value 'DisableRollback' is 0
Action ended 12:33:06: InstallFinalize. Return value 3.

mandpenny

Please read this blog and see if it helps with the problem.

http://blogs/jdbaker/archive/2006/04/20/10684.aspx

|||

Thanks for the reply Raja, but I can't get to that URL - pg. cannot be displayed error...

Mandy

|||

I had a similar problem - removing the beta version of SQL Native Client (which came with the 2005 CTP) fixed it

Dave

Microsoft SQL Server Setup Support Files (English) -- Installation failed

I'm trying in vain to upgrade sql server 2000 to 2005 with great headache and pain.

I (finally) have removed all Beta, and other incompatible version of .NET, Visual Studio and any other offending components, and made it to the first page of the install shield.

The .NET 2.0 components installed fine - but I get a fatal error trying to install the SQL Server Set Support Files.

I do have a log file - and have tired searching on the various error codes in it, but am coming up blank. Please advise - this is taking forever!

sample of error msgs in log file:

MSI (s) (B0:E0) [12:33:06:613]: Note: 1: 1935 2: 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.NetEnterpriseServers.ExceptionMessageBox,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:613]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.

MSI (s) (B0:E0) [12:33:06:613]: Executing op: ComponentRegister(ComponentId={52723CBD-3400-458C-988A-4D012E6CAEDB},KeyPath=<\Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:629]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:E0) [12:33:06:629]: Assembly Error:Function not defined in specified DLL.

MSI (s) (B0:E0) [12:33:06:629]: Note: 1: 1935 2: {52723CBD-3400-458C-988A-4D012E6CAEDB} 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:629]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}

Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
MSI (s) (B0:E0) [12:33:06:629]: User policy value 'DisableRollback' is 0
MSI (s) (B0:E0) [12:33:06:629]: Machine policy value 'DisableRollback' is 0
Action ended 12:33:06: InstallFinalize. Return value 3.

mandpenny

Please read this blog and see if it helps with the problem.

http://blogs/jdbaker/archive/2006/04/20/10684.aspx

|||

Thanks for the reply Raja, but I can't get to that URL - pg. cannot be displayed error...

Mandy

|||

I had a similar problem - removing the beta version of SQL Native Client (which came with the 2005 CTP) fixed it

Dave