Moving a SQL Server to a new domain?

Can anyone point me in the right direction here?
What do I need to be aware of when moving a SQL 2000 server from a 2000 to a
different 2003 domain (not upgrading the existing domain)? The server has
roughly 40 SQL users and they are all configured to use SQL Authentication.
Is it as simple as removing the server from one domain and joining the other
with some possible workstation configuration changes to reflect the new FQDN?
Thanks in advance!If it was 6.5, then you would have lots of work. But 2000 is fairly
transparent. The only thing you can have to do is recreate the login because
their GUID changed on the new domain.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"FombyJambox" wrote:
> Can anyone point me in the right direction here?
> What do I need to be aware of when moving a SQL 2000 server from a 2000 to a
> different 2003 domain (not upgrading the existing domain)? The server has
> roughly 40 SQL users and they are all configured to use SQL Authentication.
> Is it as simple as removing the server from one domain and joining the other
> with some possible workstation configuration changes to reflect the new FQDN?
> Thanks in advance!

Moving a SQL Server 2K cluster to new subet

Hi, I need to move a MSCS cluster running SQL Server 2000 Enterprise
Edition to a new subnet. Can anyone point me to or list what items I need to
be aware of in order for me to move my cluster?
Thanks
It's really not that bad, see http://support.microsoft.com/?id=244980 for
the clicks.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Jose Lopez-Alvarez" <jose.lopez-alvarez@.ftb.ca.gov> wrote in message
news:%23dlhyChkEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi, I need to move a MSCS cluster running SQL Server 2000 Enterprise
> Edition to a new subnet. Can anyone point me to or list what items I need
> to
> be aware of in order for me to move my cluster?
>
> Thanks
>
>
sql

Moving a Full-Text Catalog from a single server to a Cluster

Hi,
I was wondering if anyone could point me in the right direction with a
problem I'm having moving a full-text catalog from one server to
another.
In a nutshell, I want to take a database with full-text indexing
enabled and move it and the catalog to a new server. The existing
system is a single server build but the new one will be clustered in
an active/passive configuration which complicates things a little.
Obviously I've read and tried the instructions in Q240867 but this
doesnt seem to have worked and a full population starts as soon as I
enable the funtionality again (so either I'm doing something wrong or
it's not possible to do it).
I've tried to follow the instructions on each of the nodes in the
cluster and on the virtual server but it doesnt seem to work.
Any help anyone can give me in this would be really appreciated.
Regards,
Mike
Are the database IDs identical on the server you are moving the catalogs to?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mike" <mike.metcalf@.4projects.com> wrote in message
news:678e073d.0410180336.37c55f97@.posting.google.c om...
> Hi,
> I was wondering if anyone could point me in the right direction with a
> problem I'm having moving a full-text catalog from one server to
> another.
> In a nutshell, I want to take a database with full-text indexing
> enabled and move it and the catalog to a new server. The existing
> system is a single server build but the new one will be clustered in
> an active/passive configuration which complicates things a little.
> Obviously I've read and tried the instructions in Q240867 but this
> doesnt seem to have worked and a full population starts as soon as I
> enable the funtionality again (so either I'm doing something wrong or
> it's not possible to do it).
> I've tried to follow the instructions on each of the nodes in the
> cluster and on the virtual server but it doesnt seem to work.
> Any help anyone can give me in this would be really appreciated.
> Regards,
> Mike
|||Hi Hillary,
I've had a look and the DBID's are the same (I thought they were but
it's always worth double-checking), the only thing that should be
diffent is that the new build will be clustered (the old one isnt) and
the FTDATA directory is being moved from the c: to the shared d: (I've
updated the registry keys to reflect the new location)
What I'm really looking for is someone to tell me where I need to apply
the registry settings I took on the original system to (node 1, node 2,
virtual server, virtual SQL Server or some mix of everything), or
failing that if someone could say if and why it wasn't possible (I'm
fairly sure it is) that would be ok too.
There's probably something different (or extra) that needs doing on a
clustered installation that hasnt been documented yet.
Mike
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Mike,
I researched and wrote the original KB article Q240867 (before it was
modified for SP3) and because you're moving from a non-clustered environment
to a clustered environment, this modified KB article's cluster related
procedures assumes that you are already in a clustered environment before
moving or copying the FT Catalog folder & files.
I'd recommend that you review KB article 812666 - "How to recover a failed
full-text search resource on a clustered instance of SQL Server 2000" at
http://support.microsoft.com/default.aspx?kbid=812666 if re-installation of
FTS is required. If not, I'd recommend that you consider setting up your
clustered environment first and then copy over the SQL000<dbid>000<ftcatid>
folder assuming the same dibd & ftcatid is on your clustered environment. If
this is not possible, then you most likely will have to run a Full
Population and take the hit on a long population period as I'm assuming that
is why you are copying to the new build from the old non-clustered build.
Regards,
John
"Mike Metcalf" <mike.metcalf@.4projects.com> wrote in message
news:uSzxk0StEHA.1400@.TK2MSFTNGP11.phx.gbl...
> Hi Hillary,
> I've had a look and the DBID's are the same (I thought they were but
> it's always worth double-checking), the only thing that should be
> diffent is that the new build will be clustered (the old one isnt) and
> the FTDATA directory is being moved from the c: to the shared d: (I've
> updated the registry keys to reflect the new location)
> What I'm really looking for is someone to tell me where I need to apply
> the registry settings I took on the original system to (node 1, node 2,
> virtual server, virtual SQL Server or some mix of everything), or
> failing that if someone could say if and why it wasn't possible (I'm
> fairly sure it is) that would be ok too.
> There's probably something different (or extra) that needs doing on a
> clustered installation that hasnt been documented yet.
> Mike
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi John,
Thanks for your suggestions, I had a look at the article over the
weekend and a combination of the two led me to the correct solution,
I've tested it 3 times and it's worked each time so I know it's not a
fluke.
Thanks again,
Mike
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You're welcome, Mike,
I guess a little bit of persistence goes a long way!
John
"Mike Metcalf" <mike.metcalf@.4projects.com> wrote in message
news:#49OMjmuEHA.2832@.tk2msftngp13.phx.gbl...
> Hi John,
> Thanks for your suggestions, I had a look at the article over the
> weekend and a combination of the two led me to the correct solution,
> I've tested it 3 times and it's worked each time so I know it's not a
> fluke.
> Thanks again,
> Mike
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
>
sql

Moving a database from Sort order 44 to Sort order 52

Can anyone point me in the right direction on the best way to take a SQL 6.5
sort order 44 database and move it and the data to a SQL 7.0 sort order 52
database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
sort order change has me dizzy...It's been a while since I did any 6.5 upgrades but if I remember correctly
you can't upgrade between sort orders. You have to BCP out all the data,
recreate the schema with the correct sort order on 7.0 and then BCP it back
in. Why upgrade to 7.0 anyway? Why not 2000?
Andrew J. Kelly SQL MVP
"Nick" <Test@.test.com> wrote in message
news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Can anyone point me in the right direction on the best way to take a SQL
6.5
> sort order 44 database and move it and the data to a SQL 7.0 sort order 52
> database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
> sort order change has me dizzy...
>|||Hi,
Upgrade wizard can not be used if the sort order id is different. The easy
way is :-
1. From SQL 6.5 Enterprise manager -- Object Menu -- Generate SQL Script.
2. Generate the script for all objects
3. COpy the Script to destination SQL 7 server
4. Create a new database in SQL 7 and execute the script. Ensure no error
occured
5. Use the DTS utility or BCP OUT/ IN to load the data into SQL 7
If you have huge volume of data it is recommended to go for BCP OUT, copy
the files to local SQl 7 server
and BCP IN.
Thanks
Hari
MCDBA
"Nick" <Test@.test.com> wrote in message
news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Can anyone point me in the right direction on the best way to take a SQL
6.5
> sort order 44 database and move it and the data to a SQL 7.0 sort order 52
> database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
> sort order change has me dizzy...
>|||I'm planning to go to SQL 2K. However, I just needed help getting from one
sort order to another...
Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
Thanks to all for the help.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
> It's been a while since I did any 6.5 upgrades but if I remember correctly
> you can't upgrade between sort orders. You have to BCP out all the data,
> recreate the schema with the correct sort order on 7.0 and then BCP it
back
> in. Why upgrade to 7.0 anyway? Why not 2000?
> --
> Andrew J. Kelly SQL MVP
>
> "Nick" <Test@.test.com> wrote in message
> news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> 6.5
52[vbcol=seagreen]
>|||Nick,
There is no issue going from SQL6.5 to SQL2k. In fact, it is much
preferred over SQL7. Ensure that you apply SQL2k SP3a after the upgrade.
It will be worthwhile to do some reading before you perform this work.
Check out these:
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/pr...oy/sqlugrd.mspx
Upgrading Databases from SQL Server 6.5 (Upgrade Wizard)
http://msdn.microsoft.com/library/d... />
e_5dko.asp
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Nick wrote:
> I'm planning to go to SQL 2K. However, I just needed help getting from one
> sort order to another...
> Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
> Thanks to all for the help.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
>
> back
>
> 52
>
>|||According to one of the links Mark listed it seems you might be able to
upgrade to a different sort order after all. As always I would try it first
and make sure you have proper and tested backups before starting.
Andrew J. Kelly SQL MVP
"Nick" <Test@.test.com> wrote in message
news:ebt5sjCZEHA.3476@.tk2msftngp13.phx.gbl...
> I'm planning to go to SQL 2K. However, I just needed help getting from one
> sort order to another...
> Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
> Thanks to all for the help.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
correctly[vbcol=seagreen]
data,[vbcol=seagreen]
> back
SQL[vbcol=seagreen]
order[vbcol=seagreen]
> 52
this[vbcol=seagreen]
>|||Mark,
This is the upgrade issue I was referring to.
http://support.microsoft.com/defaul...kb;en-us;818550
However, there are workarunds.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:OfPYD%23CZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Nick,
> There is no issue going from SQL6.5 to SQL2k. In fact, it is much
> preferred over SQL7. Ensure that you apply SQL2k SP3a after the upgrade.
> It will be worthwhile to do some reading before you perform this work.
> Check out these:
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/pr...oy/sqlugrd.mspx
> Upgrading Databases from SQL Server 6.5 (Upgrade Wizard)
>
http://msdn.microsoft.com/library/d...pgrade_5dko.asp
[vbcol=seagreen]
>
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Nick wrote:
one[vbcol=seagreen]
correctly[vbcol=seagreen]
data,[vbcol=seagreen]
SQL[vbcol=seagreen]
this[vbcol=seagreen]sql

Moving a database from Sort order 44 to Sort order 52

Can anyone point me in the right direction on the best way to take a SQL 6.5
sort order 44 database and move it and the data to a SQL 7.0 sort order 52
database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
sort order change has me dizzy...It's been a while since I did any 6.5 upgrades but if I remember correctly
you can't upgrade between sort orders. You have to BCP out all the data,
recreate the schema with the correct sort order on 7.0 and then BCP it back
in. Why upgrade to 7.0 anyway? Why not 2000?
--
Andrew J. Kelly SQL MVP
"Nick" <Test@.test.com> wrote in message
news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Can anyone point me in the right direction on the best way to take a SQL
6.5
> sort order 44 database and move it and the data to a SQL 7.0 sort order 52
> database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
> sort order change has me dizzy...
>|||Hi,
Upgrade wizard can not be used if the sort order id is different. The easy
way is :-
1. From SQL 6.5 Enterprise manager -- Object Menu -- Generate SQL Script.
2. Generate the script for all objects
3. COpy the Script to destination SQL 7 server
4. Create a new database in SQL 7 and execute the script. Ensure no error
occured
5. Use the DTS utility or BCP OUT/ IN to load the data into SQL 7
If you have huge volume of data it is recommended to go for BCP OUT, copy
the files to local SQl 7 server
and BCP IN.
--
Thanks
Hari
MCDBA
"Nick" <Test@.test.com> wrote in message
news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Can anyone point me in the right direction on the best way to take a SQL
6.5
> sort order 44 database and move it and the data to a SQL 7.0 sort order 52
> database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
> sort order change has me dizzy...
>|||I'm planning to go to SQL 2K. However, I just needed help getting from one
sort order to another...
Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
Thanks to all for the help.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
> It's been a while since I did any 6.5 upgrades but if I remember correctly
> you can't upgrade between sort orders. You have to BCP out all the data,
> recreate the schema with the correct sort order on 7.0 and then BCP it
back
> in. Why upgrade to 7.0 anyway? Why not 2000?
> --
> Andrew J. Kelly SQL MVP
>
> "Nick" <Test@.test.com> wrote in message
> news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> > Can anyone point me in the right direction on the best way to take a SQL
> 6.5
> > sort order 44 database and move it and the data to a SQL 7.0 sort order
52
> > database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
> > sort order change has me dizzy...
> >
> >
>|||Nick,
There is no issue going from SQL6.5 to SQL2k. In fact, it is much
preferred over SQL7. Ensure that you apply SQL2k SP3a after the upgrade.
It will be worthwhile to do some reading before you perform this work.
Check out these:
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
Upgrading Databases from SQL Server 6.5 (Upgrade Wizard)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_upgrade_5dko.asp
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Nick wrote:
> I'm planning to go to SQL 2K. However, I just needed help getting from one
> sort order to another...
> Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
> Thanks to all for the help.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
>>It's been a while since I did any 6.5 upgrades but if I remember correctly
>>you can't upgrade between sort orders. You have to BCP out all the data,
>>recreate the schema with the correct sort order on 7.0 and then BCP it
> back
>>in. Why upgrade to 7.0 anyway? Why not 2000?
>>--
>>Andrew J. Kelly SQL MVP
>>
>>"Nick" <Test@.test.com> wrote in message
>>news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
>>Can anyone point me in the right direction on the best way to take a SQL
>>6.5
>>sort order 44 database and move it and the data to a SQL 7.0 sort order
> 52
>>database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
>>sort order change has me dizzy...
>>
>>
>|||According to one of the links Mark listed it seems you might be able to
upgrade to a different sort order after all. As always I would try it first
and make sure you have proper and tested backups before starting.
--
Andrew J. Kelly SQL MVP
"Nick" <Test@.test.com> wrote in message
news:ebt5sjCZEHA.3476@.tk2msftngp13.phx.gbl...
> I'm planning to go to SQL 2K. However, I just needed help getting from one
> sort order to another...
> Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
> Thanks to all for the help.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
> > It's been a while since I did any 6.5 upgrades but if I remember
correctly
> > you can't upgrade between sort orders. You have to BCP out all the
data,
> > recreate the schema with the correct sort order on 7.0 and then BCP it
> back
> > in. Why upgrade to 7.0 anyway? Why not 2000?
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "Nick" <Test@.test.com> wrote in message
> > news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> > > Can anyone point me in the right direction on the best way to take a
SQL
> > 6.5
> > > sort order 44 database and move it and the data to a SQL 7.0 sort
order
> 52
> > > database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But
this
> > > sort order change has me dizzy...
> > >
> > >
> >
> >
>|||Mark,
This is the upgrade issue I was referring to.
http://support.microsoft.com/default.aspx?scid=kb;en-us;818550
However, there are workarunds.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:OfPYD%23CZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Nick,
> There is no issue going from SQL6.5 to SQL2k. In fact, it is much
> preferred over SQL7. Ensure that you apply SQL2k SP3a after the upgrade.
> It will be worthwhile to do some reading before you perform this work.
> Check out these:
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlugrd.mspx
> Upgrading Databases from SQL Server 6.5 (Upgrade Wizard)
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_upgrade_5dko.asp
>
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Nick wrote:
> > I'm planning to go to SQL 2K. However, I just needed help getting from
one
> > sort order to another...
> > Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
> >
> > Thanks to all for the help.
> >
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
> >
> >>It's been a while since I did any 6.5 upgrades but if I remember
correctly
> >>you can't upgrade between sort orders. You have to BCP out all the
data,
> >>recreate the schema with the correct sort order on 7.0 and then BCP it
> >
> > back
> >
> >>in. Why upgrade to 7.0 anyway? Why not 2000?
> >>
> >>--
> >>Andrew J. Kelly SQL MVP
> >>
> >>
> >>"Nick" <Test@.test.com> wrote in message
> >>news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> >>
> >>Can anyone point me in the right direction on the best way to take a
SQL
> >>
> >>6.5
> >>
> >>sort order 44 database and move it and the data to a SQL 7.0 sort order
> >
> > 52
> >
> >>database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But
this
> >>sort order change has me dizzy...
> >>
> >>
> >>
> >>
> >
> >

Moving a database from Sort order 44 to Sort order 52

Can anyone point me in the right direction on the best way to take a SQL 6.5
sort order 44 database and move it and the data to a SQL 7.0 sort order 52
database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
sort order change has me dizzy...
It's been a while since I did any 6.5 upgrades but if I remember correctly
you can't upgrade between sort orders. You have to BCP out all the data,
recreate the schema with the correct sort order on 7.0 and then BCP it back
in. Why upgrade to 7.0 anyway? Why not 2000?
Andrew J. Kelly SQL MVP
"Nick" <Test@.test.com> wrote in message
news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Can anyone point me in the right direction on the best way to take a SQL
6.5
> sort order 44 database and move it and the data to a SQL 7.0 sort order 52
> database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
> sort order change has me dizzy...
>
|||Hi,
Upgrade wizard can not be used if the sort order id is different. The easy
way is :-
1. From SQL 6.5 Enterprise manager -- Object Menu -- Generate SQL Script.
2. Generate the script for all objects
3. COpy the Script to destination SQL 7 server
4. Create a new database in SQL 7 and execute the script. Ensure no error
occured
5. Use the DTS utility or BCP OUT/ IN to load the data into SQL 7
If you have huge volume of data it is recommended to go for BCP OUT, copy
the files to local SQl 7 server
and BCP IN.
Thanks
Hari
MCDBA
"Nick" <Test@.test.com> wrote in message
news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Can anyone point me in the right direction on the best way to take a SQL
6.5
> sort order 44 database and move it and the data to a SQL 7.0 sort order 52
> database ? The 6.5 to 7.0 part I got down (SQL Upgrade wizard). But this
> sort order change has me dizzy...
>
|||I'm planning to go to SQL 2K. However, I just needed help getting from one
sort order to another...
Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
Thanks to all for the help.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
> It's been a while since I did any 6.5 upgrades but if I remember correctly
> you can't upgrade between sort orders. You have to BCP out all the data,
> recreate the schema with the correct sort order on 7.0 and then BCP it
back[vbcol=seagreen]
> in. Why upgrade to 7.0 anyway? Why not 2000?
> --
> Andrew J. Kelly SQL MVP
>
> "Nick" <Test@.test.com> wrote in message
> news:elDz5$5YEHA.3664@.TK2MSFTNGP12.phx.gbl...
> 6.5
52
>
|||Nick,
There is no issue going from SQL6.5 to SQL2k. In fact, it is much
preferred over SQL7. Ensure that you apply SQL2k SP3a after the upgrade.
It will be worthwhile to do some reading before you perform this work.
Check out these:
How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
Upgrading Databases from SQL Server 6.5 (Upgrade Wizard)
http://msdn.microsoft.com/library/de...grade_5dko.asp
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Nick wrote:
> I'm planning to go to SQL 2K. However, I just needed help getting from one
> sort order to another...
> Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
> Thanks to all for the help.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
>
> back
>
> 52
>
>
|||According to one of the links Mark listed it seems you might be able to
upgrade to a different sort order after all. As always I would try it first
and make sure you have proper and tested backups before starting.
Andrew J. Kelly SQL MVP
"Nick" <Test@.test.com> wrote in message
news:ebt5sjCZEHA.3476@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> I'm planning to go to SQL 2K. However, I just needed help getting from one
> sort order to another...
> Isn't there a problem upgrading from SQL 6.5 directly to SQL 2K ?
> Thanks to all for the help.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eeTEeX7YEHA.992@.TK2MSFTNGP10.phx.gbl...
correctly[vbcol=seagreen]
data,[vbcol=seagreen]
> back
SQL[vbcol=seagreen]
order[vbcol=seagreen]
> 52
this
>
|||Mark,
This is the upgrade issue I was referring to.
http://support.microsoft.com/default...b;en-us;818550
However, there are workarunds.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:OfPYD%23CZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Nick,
> There is no issue going from SQL6.5 to SQL2k. In fact, it is much
> preferred over SQL7. Ensure that you apply SQL2k SP3a after the upgrade.
> It will be worthwhile to do some reading before you perform this work.
> Check out these:
> How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
> http://www.microsoft.com/technet/pro...y/sqlugrd.mspx
> Upgrading Databases from SQL Server 6.5 (Upgrade Wizard)
>
http://msdn.microsoft.com/library/de...grade_5dko.asp[vbcol=seagreen]
>
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Nick wrote:
one[vbcol=seagreen]
correctly[vbcol=seagreen]
data,[vbcol=seagreen]
SQL[vbcol=seagreen]
this[vbcol=seagreen]

Move test data to production SQL Server

Hi All,
Could someone point me to a white paper/best practices on how to move/update
data from test sql server to a production sql server?
Both of the server have the same schema.
I would like to know if there is a way to synchronize the two databases.
Would SQL Server Replication be a good idea?
Many thanks,
See http://www.red-gate.com for the SQL Data Compare product. We use Red
Gate's SQL Compare and SQL Data Compare (mostly in development, testing, and
production prep -- not transitioning to production). SQL Data Compare
quickly compares and allows you to synchronize two databases.
A more robust solution that accounts for "production data" being preserved
while merging in updated lookup tables, et. al., simply requires analyzing
your needs (which takes _time_) and then, in our case, maintaining a central
script for the lookup tables (which also takes _time_). Our script is
simply a 1) disable constraints 2) delete, repopulate lookup tables, 3)
re-enable constraints (and run DBCC CHECKCONSTRAINTS to make sure nothing
unexpected happened!)
"Amine" <Amine@.discussions.microsoft.com> wrote in message
news:D92C4BF2-4EE9-4B64-BA32-D39D4BC21D15@.microsoft.com...
> Hi All,
> Could someone point me to a white paper/best practices on how to
move/update
> data from test sql server to a production sql server?
> Both of the server have the same schema.
> I would like to know if there is a way to synchronize the two databases.
> Would SQL Server Replication be a good idea?
> Many thanks,
>
>
|||Mike:
What do you mean by lookup tables?
"Mike Jansen" wrote:

> See http://www.red-gate.com for the SQL Data Compare product. We use Red
> Gate's SQL Compare and SQL Data Compare (mostly in development, testing, and
> production prep -- not transitioning to production). SQL Data Compare
> quickly compares and allows you to synchronize two databases.
> A more robust solution that accounts for "production data" being preserved
> while merging in updated lookup tables, et. al., simply requires analyzing
> your needs (which takes _time_) and then, in our case, maintaining a central
> script for the lookup tables (which also takes _time_). Our script is
> simply a 1) disable constraints 2) delete, repopulate lookup tables, 3)
> re-enable constraints (and run DBCC CHECKCONSTRAINTS to make sure nothing
> unexpected happened!)
> "Amine" <Amine@.discussions.microsoft.com> wrote in message
> news:D92C4BF2-4EE9-4B64-BA32-D39D4BC21D15@.microsoft.com...
> move/update
>
>
|||By lookup tables I simply meant tables that are read-only, that the
application doesn't update.
I've got to run, but if you need more info on what I mean, let me know and
I'll try to be more detailed.
"Amine" <Amine@.discussions.microsoft.com> wrote in message
news:6C29CC4B-9B2C-4930-8269-2D3B371D28B9@.microsoft.com...[vbcol=seagreen]
> Mike:
> What do you mean by lookup tables?
>
> "Mike Jansen" wrote:
Red[vbcol=seagreen]
and[vbcol=seagreen]
preserved[vbcol=seagreen]
analyzing[vbcol=seagreen]
central[vbcol=seagreen]
nothing[vbcol=seagreen]
databases.[vbcol=seagreen]

Move test data to production SQL Server

Hi All,
Could someone point me to a white paper/best practices on how to move/update
data from test sql server to a production sql server?
Both of the server have the same schema.
I would like to know if there is a way to synchronize the two databases.
Would SQL Server Replication be a good idea?
Many thanks,See http://www.red-gate.com for the SQL Data Compare product. We use Red
Gate's SQL Compare and SQL Data Compare (mostly in development, testing, and
production prep -- not transitioning to production). SQL Data Compare
quickly compares and allows you to synchronize two databases.
A more robust solution that accounts for "production data" being preserved
while merging in updated lookup tables, et. al., simply requires analyzing
your needs (which takes _time_) and then, in our case, maintaining a central
script for the lookup tables (which also takes _time_). Our script is
simply a 1) disable constraints 2) delete, repopulate lookup tables, 3)
re-enable constraints (and run DBCC CHECKCONSTRAINTS to make sure nothing
unexpected happened!)
"Amine" <Amine@.discussions.microsoft.com> wrote in message
news:D92C4BF2-4EE9-4B64-BA32-D39D4BC21D15@.microsoft.com...
> Hi All,
> Could someone point me to a white paper/best practices on how to
move/update
> data from test sql server to a production sql server?
> Both of the server have the same schema.
> I would like to know if there is a way to synchronize the two databases.
> Would SQL Server Replication be a good idea?
> Many thanks,
>
>|||Mike:
What do you mean by lookup tables?
"Mike Jansen" wrote:
> See http://www.red-gate.com for the SQL Data Compare product. We use Red
> Gate's SQL Compare and SQL Data Compare (mostly in development, testing, and
> production prep -- not transitioning to production). SQL Data Compare
> quickly compares and allows you to synchronize two databases.
> A more robust solution that accounts for "production data" being preserved
> while merging in updated lookup tables, et. al., simply requires analyzing
> your needs (which takes _time_) and then, in our case, maintaining a central
> script for the lookup tables (which also takes _time_). Our script is
> simply a 1) disable constraints 2) delete, repopulate lookup tables, 3)
> re-enable constraints (and run DBCC CHECKCONSTRAINTS to make sure nothing
> unexpected happened!)
> "Amine" <Amine@.discussions.microsoft.com> wrote in message
> news:D92C4BF2-4EE9-4B64-BA32-D39D4BC21D15@.microsoft.com...
> > Hi All,
> > Could someone point me to a white paper/best practices on how to
> move/update
> > data from test sql server to a production sql server?
> >
> > Both of the server have the same schema.
> > I would like to know if there is a way to synchronize the two databases.
> > Would SQL Server Replication be a good idea?
> > Many thanks,
> >
> >
> >
> >
>
>|||By lookup tables I simply meant tables that are read-only, that the
application doesn't update.
I've got to run, but if you need more info on what I mean, let me know and
I'll try to be more detailed.
"Amine" <Amine@.discussions.microsoft.com> wrote in message
news:6C29CC4B-9B2C-4930-8269-2D3B371D28B9@.microsoft.com...
> Mike:
> What do you mean by lookup tables?
>
> "Mike Jansen" wrote:
> > See http://www.red-gate.com for the SQL Data Compare product. We use
Red
> > Gate's SQL Compare and SQL Data Compare (mostly in development, testing,
and
> > production prep -- not transitioning to production). SQL Data Compare
> > quickly compares and allows you to synchronize two databases.
> >
> > A more robust solution that accounts for "production data" being
preserved
> > while merging in updated lookup tables, et. al., simply requires
analyzing
> > your needs (which takes _time_) and then, in our case, maintaining a
central
> > script for the lookup tables (which also takes _time_). Our script is
> > simply a 1) disable constraints 2) delete, repopulate lookup tables, 3)
> > re-enable constraints (and run DBCC CHECKCONSTRAINTS to make sure
nothing
> > unexpected happened!)
> >
> > "Amine" <Amine@.discussions.microsoft.com> wrote in message
> > news:D92C4BF2-4EE9-4B64-BA32-D39D4BC21D15@.microsoft.com...
> > > Hi All,
> > > Could someone point me to a white paper/best practices on how to
> > move/update
> > > data from test sql server to a production sql server?
> > >
> > > Both of the server have the same schema.
> > > I would like to know if there is a way to synchronize the two
databases.
> > > Would SQL Server Replication be a good idea?
> > > Many thanks,
> > >
> > >
> > >
> > >
> >
> >
> >sql

Move test data to production SQL Server

Hi All,
Could someone point me to a white paper/best practices on how to move/update
data from test sql server to a production sql server?
Both of the server have the same schema.
I would like to know if there is a way to synchronize the two databases.
Would SQL Server Replication be a good idea?
Many thanks,
Setting up replication between test server and production server is a very
bad idea. Don't even think about it.
"Amine" wrote:

> Hi All,
> Could someone point me to a white paper/best practices on how to move/update
> data from test sql server to a production sql server?
> Both of the server have the same schema.
> I would like to know if there is a way to synchronize the two databases.
> Would SQL Server Replication be a good idea?
> Many thanks,
|||I concur with Jack, however if you are going in the opposite direction, it
could be a good idea.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:3AE6B9EF-089F-4D1D-8BEB-967CC32C0004@.microsoft.com...[vbcol=seagreen]
> Setting up replication between test server and production server is a very
> bad idea. Don't even think about it.
> "Amine" wrote:
move/update[vbcol=seagreen]
|||Amine,
like Jack and Hilary I'm struggling to see why you would want replication
from test to proiduction. However, perhaps you are loading (cleansed) data
as part of a build? In this case you could use DTS to transfer the data as a
one-off. If the environments are disconnected, then there are 3rd party
tools to take data and generate insert statements from it.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Move test data to production SQL Server

Hi All,
Could someone point me to a white paper/best practices on how to move/update
data from test sql server to a production sql server?
Both of the server have the same schema.
I would like to know if there is a way to synchronize the two databases.
Would SQL Server Replication be a good idea?
Many thanks,See http://www.red-gate.com for the SQL Data Compare product. We use Red
Gate's SQL Compare and SQL Data Compare (mostly in development, testing, and
production prep -- not transitioning to production). SQL Data Compare
quickly compares and allows you to synchronize two databases.
A more robust solution that accounts for "production data" being preserved
while merging in updated lookup tables, et. al., simply requires analyzing
your needs (which takes _time_) and then, in our case, maintaining a central
script for the lookup tables (which also takes _time_). Our script is
simply a 1) disable constraints 2) delete, repopulate lookup tables, 3)
re-enable constraints (and run DBCC CHECKCONSTRAINTS to make sure nothing
unexpected happened!)
"Amine" <Amine@.discussions.microsoft.com> wrote in message
news:D92C4BF2-4EE9-4B64-BA32-D39D4BC21D15@.microsoft.com...
> Hi All,
> Could someone point me to a white paper/best practices on how to
move/update
> data from test sql server to a production sql server?
> Both of the server have the same schema.
> I would like to know if there is a way to synchronize the two databases.
> Would SQL Server Replication be a good idea?
> Many thanks,
>
>|||Mike:
What do you mean by lookup tables?
"Mike Jansen" wrote:

> See http://www.red-gate.com for the SQL Data Compare product. We use Red
> Gate's SQL Compare and SQL Data Compare (mostly in development, testing, a
nd
> production prep -- not transitioning to production). SQL Data Compare
> quickly compares and allows you to synchronize two databases.
> A more robust solution that accounts for "production data" being preserved
> while merging in updated lookup tables, et. al., simply requires analyzing
> your needs (which takes _time_) and then, in our case, maintaining a centr
al
> script for the lookup tables (which also takes _time_). Our script is
> simply a 1) disable constraints 2) delete, repopulate lookup tables, 3)
> re-enable constraints (and run DBCC CHECKCONSTRAINTS to make sure nothing
> unexpected happened!)
> "Amine" <Amine@.discussions.microsoft.com> wrote in message
> news:D92C4BF2-4EE9-4B64-BA32-D39D4BC21D15@.microsoft.com...
> move/update
>
>|||By lookup tables I simply meant tables that are read-only, that the
application doesn't update.
I've got to run, but if you need more info on what I mean, let me know and
I'll try to be more detailed.
"Amine" <Amine@.discussions.microsoft.com> wrote in message
news:6C29CC4B-9B2C-4930-8269-2D3B371D28B9@.microsoft.com...[vbcol=seagreen]
> Mike:
> What do you mean by lookup tables?
>
> "Mike Jansen" wrote:
>
Red[vbcol=seagreen]
and[vbcol=seagreen]
preserved[vbcol=seagreen]
analyzing[vbcol=seagreen]
central[vbcol=seagreen]
nothing[vbcol=seagreen]
databases.[vbcol=seagreen]