Copying dBs

I am running SQL 2000 (using replication) & Win
2000.
We are getting a new production sever and would like to
know the best practice for moving all the SQL data from
the Old Server to the New Server. There are a few
questions the concern me.
- Will I have to setup replication on the new server?
- Will all the dB defaults be preserved?
Larry,
if the server names are the same, and you have backups of all databases, then you should be able torestore them on the new production server. If you're doing transactional replication, then make sure the distribution database is synchronized with the prod
uction database. If the server names are different, then I'd script out the publications and recreate on the new server. Provided no subscribers are allowed to do any data changes during this time, you should be able to add the subscriptions without apply
ing the data snapshot (@.sync_type ='none').
HTH,
Paul Ibison
|||In the long run you would be best to drop the subscriptions and publications
on the current production server. Back it up and restore it to the new
publisher.
Recreate the publications from scripts and then do create a nosync
subscription to your existing subscriber.
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:238c01c427b5$7a2e6040$a501280a@.phx.gbl...
> I am running SQL 2000 (using replication) & Win
> 2000.
> We are getting a new production sever and would like to
> know the best practice for moving all the SQL data from
> the Old Server to the New Server. There are a few
> questions the concern me.
> - Will I have to setup replication on the new server?
> - Will all the dB defaults be preserved?
>

Copying database to same machine?

Hi all,
I've read a lot of posts about copying a SQL database to a separate machine;
but, what about to the same machine.
In practice for others who have done what is the simplest reliable method?
Also, is there any reason not to detach the database, copy the physical
files (mdf and log) to a different name and reattach it under that other name?
Thanks!
gman997 wrote:
> Hi all,
> I've read a lot of posts about copying a SQL database to a separate
> machine; but, what about to the same machine.
> In practice for others who have done what is the simplest reliable
> method?
> Also, is there any reason not to detach the database, copy the
> physical
> files (mdf and log) to a different name and reattach it under that
> other name?
> Thanks!
If you need this totally scripted, you should create the new database and
use backup/restore. If you don't mind taking the database offline and making
a copy, you can use detach/attach. Detach is probably faster if your
database can be taken offline. In any case, I would perform a full backup
before doing anything, and in that respect, it might just pay to restore to
a new database...
David Gugick
Quest Software

Copying database to same machine?

Hi all,
I've read a lot of posts about copying a SQL database to a separate machine;
but, what about to the same machine.
In practice for others who have done what is the simplest reliable method?
Also, is there any reason not to detach the database, copy the physical
files (mdf and log) to a different name and reattach it under that other nam
e?
Thanks!gman997 wrote:
> Hi all,
> I've read a lot of posts about copying a SQL database to a separate
> machine; but, what about to the same machine.
> In practice for others who have done what is the simplest reliable
> method?
> Also, is there any reason not to detach the database, copy the
> physical
> files (mdf and log) to a different name and reattach it under that
> other name?
> Thanks!
If you need this totally scripted, you should create the new database and
use backup/restore. If you don't mind taking the database offline and making
a copy, you can use detach/attach. Detach is probably faster if your
database can be taken offline. In any case, I would perform a full backup
before doing anything, and in that respect, it might just pay to restore to
a new database...
David Gugick
Quest Software

Copying database to same machine?

Hi all,
I've read a lot of posts about copying a SQL database to a separate machine;
but, what about to the same machine.
In practice for others who have done what is the simplest reliable method?
Also, is there any reason not to detach the database, copy the physical
files (mdf and log) to a different name and reattach it under that other name?
Thanks!gman997 wrote:
> Hi all,
> I've read a lot of posts about copying a SQL database to a separate
> machine; but, what about to the same machine.
> In practice for others who have done what is the simplest reliable
> method?
> Also, is there any reason not to detach the database, copy the
> physical
> files (mdf and log) to a different name and reattach it under that
> other name?
> Thanks!
If you need this totally scripted, you should create the new database and
use backup/restore. If you don't mind taking the database offline and making
a copy, you can use detach/attach. Detach is probably faster if your
database can be taken offline. In any case, I would perform a full backup
before doing anything, and in that respect, it might just pay to restore to
a new database...
--
David Gugick
Quest Software