Hi,
I am considering upgrading to SQL Server service pack 4 and would just like
to clarify.
In the readme file for SP 4 if find the following:
“Note If an instance of SQL Server is not part of a replication topology,
you can back up a user database and restore it on any other release of SQL
Server 2000.”
Does this mean that I will not be able to restore a user database from a
instance running SP3 to a instance running sp 4 if it is part of a
replication topology? And if this is the case is there a workaround? Like a
script that upgrades the user databases to sp 4?
Scenario: Two environments: testing and production. I upgrade test to SP4
and then restore user databases from production (sp3). Replication is used
both in test and production, so the restored user databases that are involved
in replication will not longer work, because they are from an instance that
is sp3? Right?
Many Thanks,
Nina
You cannot restore a backup of a replicated database from a different version
of SQL Server 2000. This is because replication updates user databases
(rather than just system databases) when the service pack is applied, and a
restored SP3 database may have replication metadata that is incompatible with
SP4 replication. User databases participating in a replication topology must
be online and accessible during upgrade to SP4 so that updates can be made.
I'm not sure if there is a separate script just to update user databases to
SP4, it may be part of the overall replication upgrade scripts. At any rate,
the recommended process is to let SP4 Setup perform the upgrade.
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nina" wrote:
> Hi,
> I am considering upgrading to SQL Server service pack 4 and would just like
> to clarify.
> In the readme file for SP 4 if find the following:
> “Note If an instance of SQL Server is not part of a replication topology,
> you can back up a user database and restore it on any other release of SQL
> Server 2000.”
> Does this mean that I will not be able to restore a user database from a
> instance running SP3 to a instance running sp 4 if it is part of a
> replication topology? And if this is the case is there a workaround? Like a
> script that upgrades the user databases to sp 4?
> Scenario: Two environments: testing and production. I upgrade test to SP4
> and then restore user databases from production (sp3). Replication is used
> both in test and production, so the restored user databases that are involved
> in replication will not longer work, because they are from an instance that
> is sp3? Right?
> Many Thanks,
> Nina
>
Showing posts with label pack. Show all posts
Showing posts with label pack. Show all posts
Friday, March 9, 2012
Wednesday, March 7, 2012
REPLICATION
DEAR ALL,
I SET UP A PUBLICATION SERVER (SQL 2005) AND A SUBSCRIPTION SERVER SQL2005 BOTH WITH SERVICE PACK. THE SETTINGS SEEM TO BE OK , AND I ALREADY SET THE TABLE WHICH I WANT TO REPLICATE. I AM USING THE TRANSACTIONAL MODE. AT THE BEGINING I COULD INSERT RECORD IN PUBLIC SERVER AND THERE WERE VISIBLE IN SUB SERVER. NEVERTHELESS WHEN I WAS TRYING TO INSERT IN THE TABLE FROM THE SUB SERVER I WAS NOT ABLE TO VIEW THE CHANGES IN PUBLISHER. ANY IDEAS PLS ?
MOREOVER, NOW I CAN NOT REPLICATE AT ALL. I DO NO KNOW IF I CHANGED ANYTHING, BUT I CAN NOT FIND IT. ANY HELP ON THIS PLS
THANKS IN ADVANCE FOR YOUR TIME
GREG
You need to use merge replication. With transactional replication you should not make changes on your subscriber - you should treat is as read only. Also check to see if your change on the subscriber has caused the distribution agent to fail.You might want to switch to the continue on data consitency error profile to clear the problem.
Labels:
database,
dear,
microsoft,
mysql,
oracle,
pack,
publication,
replication,
server,
service,
settings,
sql,
sql2005,
subscription
Subscribe to:
Posts (Atom)