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 w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
Pablo
Hi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
--
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>

Migrate w/o upgrade wizard

Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>sql

migrate sql2k dts packages to sql2k5

new to sql2k5.
i have some sql2k dts packages i migrated to sql2k5 using wizard and
they showed up under intergration services, stored packages, msdb, but
I can't open or edit any of the package.
For the same packages, if I saved them as external file in sql2k, then
import them in sql2k5, they will show up in SSMS, management, legacy,
DTS folder, and if had downloaded the Microsoft SQL Server 2000 DTS
Designer Components , I can open and edit the packages.
This is all very confusing to me.
first, why the dts showed up at different place in sql2k5 (what's the
difference between import and migrate?)
2nd, how to edit the migrated dts packages?
3rd, in sql2k, dts package is part of msdb, as long as I backup msdb, I
can restore all the pckages, how about in sql2k5, where are dts being
stored and are they still part of msdb?
thank you.=== Steve L === wrote:
> new to sql2k5.
> i have some sql2k dts packages i migrated to sql2k5 using wizard and
> they showed up under intergration services, stored packages, msdb, but
> I can't open or edit any of the package.
> For the same packages, if I saved them as external file in sql2k, then
> import them in sql2k5, they will show up in SSMS, management, legacy,
> DTS folder, and if had downloaded the Microsoft SQL Server 2000 DTS
> Designer Components , I can open and edit the packages.
> This is all very confusing to me.
> first, why the dts showed up at different place in sql2k5 (what's the
> difference between import and migrate?)
> 2nd, how to edit the migrated dts packages?
> 3rd, in sql2k, dts package is part of msdb, as long as I backup msdb, I
> can restore all the pckages, how about in sql2k5, where are dts being
> stored and are they still part of msdb?
> thank you.
>
DTS doesn't exist in SQL 2005, it has been replaced with Integration
Services...|||DTS services is no loginer in sql2k5, but you can still import or
migrate sql2k dts to it. I think you are missing what I asked in my
posting.
Tracy McKibben wrote:
> === Steve L === wrote:
> DTS doesn't exist in SQL 2005, it has been replaced with Integration
> Services...