I am running into problems when attempting to move
databases from SQL 6.5 to SQL 2K. There is a known bug in
SQL2K, SP3a when using the migration wizard. The work
around involved installing 6.5 on a Windows 2000 Server
but we ran into problems with that as well. Microsoft
actually removed their White Paper on this subject from
their site. Does anyone know of a good information source
for instructions on how to do this?Try to detach the databases from source 6.5 server, copy
the your database mdf and ldf file to your destination
server server and attach the database. Also look into
moving your logins account to that server
>--Original Message--
>I am running into problems when attempting to move
>databases from SQL 6.5 to SQL 2K. There is a known bug
in
>SQL2K, SP3a when using the migration wizard. The work
>around involved installing 6.5 on a Windows 2000 Server
>but we ran into problems with that as well. Microsoft
>actually removed their White Paper on this subject from
>their site. Does anyone know of a good information
source
>for instructions on how to do this?
>.
>
Showing posts with label sp3a. Show all posts
Showing posts with label sp3a. Show all posts
Friday, March 23, 2012
Wednesday, March 7, 2012
Move Distribution
Hi All,
I have 1 server as publisher and distributor with SQL 2000 sp3a and I have about 100 subscribers.
I have to move my distribution database and my published database on another physical location on the same server.
I tried to use sp_detach_db stored procedure but an error occurred: Server: Msg 3724 (Cannot drop the database 'distribution' because it is being used for replication).
Somebody knows how can I move my databases without reconfigure all my merge replication.
thanks in advance,
You can't do this.
You must disable replication on your publisher, enable it on your distributor, and allow this publisher to publish to this distributor. Then reinstall replication on your publisher and have it use the distributors database.
Then rebuild your publications and susbcriptions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||I have a quicker way of moving the files of any database used for replication (including distribution database) :
Just backup the database, then restore it using SQLEM, with following subtelties :
- "Force restore over existing database" option ticked,
- and edit the paths of the .MDF and .LDF.
It keeps all replication stuff alive.
Only pay attention that no user is connected, of course (go to Management > Current Activity > Process Info to view active connections to the database you're backuping/restoring).
Note:
You may even use this procedure upon disaster recovery, when the database does not exist anymore :
- create a new database (with _same_ _name_ as the crashed database, of course)
- enable it for publication (even if it is the subscriber database), using Replication>Configure publishing etc.
- restore the backup, with "Force restore over existing database"
Hope this helps,
--Rico
I have 1 server as publisher and distributor with SQL 2000 sp3a and I have about 100 subscribers.
I have to move my distribution database and my published database on another physical location on the same server.
I tried to use sp_detach_db stored procedure but an error occurred: Server: Msg 3724 (Cannot drop the database 'distribution' because it is being used for replication).
Somebody knows how can I move my databases without reconfigure all my merge replication.
thanks in advance,
You can't do this.
You must disable replication on your publisher, enable it on your distributor, and allow this publisher to publish to this distributor. Then reinstall replication on your publisher and have it use the distributors database.
Then rebuild your publications and susbcriptions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||I have a quicker way of moving the files of any database used for replication (including distribution database) :
Just backup the database, then restore it using SQLEM, with following subtelties :
- "Force restore over existing database" option ticked,
- and edit the paths of the .MDF and .LDF.
It keeps all replication stuff alive.
Only pay attention that no user is connected, of course (go to Management > Current Activity > Process Info to view active connections to the database you're backuping/restoring).
Note:
You may even use this procedure upon disaster recovery, when the database does not exist anymore :
- create a new database (with _same_ _name_ as the crashed database, of course)
- enable it for publication (even if it is the subscriber database), using Replication>Configure publishing etc.
- restore the backup, with "Force restore over existing database"
Hope this helps,
--Rico
Labels:
database,
distribution,
distributor,
microsoft,
mysql,
oracle,
publisher,
server,
sp3a,
sql,
subscribers
move db Win2000 SQL2000sp2 to Server 2003 sp3a
On my current install of Win 2000 Sql Server sp2 I tried to install sp3a. A
fter repeated attempts the server did not update. I got no errors and it lo
oked like it had installed on the default database but every time I check th
e version, I was on sp2. S
o now I have a new server with Server 2003 installed and will be moving my d
atabases over there. So I have installed Sql Server 2000 sp2. I will then
be installing sp3a. Will there be any problems with restoring the master, t
emp, and all over databases
from Win 2000 sp2 server TO Server 2003 sp3a server?
Thanks for any guidance you can provide.I would have thought doing this would be a bad idea, as the restored master,
temp, msdb db's etc would be a different version to most of the server.
You are probably better off trying to update it after restoring your dbs.
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||Can not really do that because Server 2003 needs to have Sql Server 2000 sp3
a installed.
fter repeated attempts the server did not update. I got no errors and it lo
oked like it had installed on the default database but every time I check th
e version, I was on sp2. S
o now I have a new server with Server 2003 installed and will be moving my d
atabases over there. So I have installed Sql Server 2000 sp2. I will then
be installing sp3a. Will there be any problems with restoring the master, t
emp, and all over databases
from Win 2000 sp2 server TO Server 2003 sp3a server?
Thanks for any guidance you can provide.I would have thought doing this would be a bad idea, as the restored master,
temp, msdb db's etc would be a different version to most of the server.
You are probably better off trying to update it after restoring your dbs.
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||Can not really do that because Server 2003 needs to have Sql Server 2000 sp3
a installed.
move db Win2000 SQL2000sp2 to Server 2003 sp3a
On my current install of Win 2000 Sql Server sp2 I tried to install sp3a. After repeated attempts the server did not update. I got no errors and it looked like it had installed on the default database but every time I check the version, I was on sp2. So now I have a new server with Server 2003 installed and will be moving my databases over there. So I have installed Sql Server 2000 sp2. I will then be installing sp3a. Will there be any problems with restoring the master, temp, and all over databases from Win 2000 sp2 server TO Server 2003 sp3a server?
Thanks for any guidance you can provide.I would have thought doing this would be a bad idea, as the restored master,
temp, msdb db's etc would be a different version to most of the server.
You are probably better off trying to update it after restoring your dbs.
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||Can not really do that because Server 2003 needs to have Sql Server 2000 sp3a installed.
Thanks for any guidance you can provide.I would have thought doing this would be a bad idea, as the restored master,
temp, msdb db's etc would be a different version to most of the server.
You are probably better off trying to update it after restoring your dbs.
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||Can not really do that because Server 2003 needs to have Sql Server 2000 sp3a installed.
Subscribe to:
Posts (Atom)