Basically your snapshot does not contain enough information in it to deploy
a new subscriber and then backfill it with changes which have occurred on
the publisher so the subscriber can merge with the publisher.
To do this you need a new snapshot. You might need to change your retention
period to something larger.
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
"Jonas Jegler" <jonas.jegler@.siegel-edv.de> wrote in message
news:OSTIybWNHHA.3944@.TK2MSFTNGP06.phx.gbl...
> We have a SQL Server 2005 Merge Replication to an SQL Server 2005 EXPRESS
> EDITION.
> After indefinable time intervals the error message:
> "They must again implement the Snapshot, since the current Snapshotfiles
> became outdated"
> comes.
> Can someone say something to me about the error message?
>
how frequently is your snapshot generated?
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
"Jonas Jegler" <jonas.jegler@.siegel-edv.de> wrote in message
news:Oc$SQejNHHA.4912@.TK2MSFTNGP02.phx.gbl...
> thankyou for your answer.
> we can do the Replication in each direction. but after indefinable time we
> becomes the error message:
> "They must again implement the Snapshot, since the current Snapshotfiles
> became outdated"
> where can i change the retention period?
>
Showing posts with label old. Show all posts
Showing posts with label old. Show all posts
Wednesday, March 28, 2012
Friday, March 9, 2012
Replication - Publisher moving to a different server
My disclaimer: Ive never done this. These are just
theories.
I would have to imagine that as long as the new box has
the same name as the old, and the data files go to the
same location on the destination as they were on the
source, you should be good. You should be able just to
backup/ restore master/ msdb and the user db's should be
alive and in-tact. No matter what advice you get here, do
this in a test environment and get backups before you do
anything.
>--Original Message--
>Hi,
>I need to move my publisher to a different database as
the current server on
>which it is running is slow compared to my current
requirements.
>But I have 2 subscribers to this server. I have merge
replication in SQL
>Server 2k with sp3 on.
>Can someone advice me as to how to have a smooth
transition? I cannot just
>replace the harddisk as the new server has a much
powerful harddisk.
>Is it possible for me to just restore the backup of the
current publisher on
>the new server alongwith the master and msdb, and
replication starts? I will
>take care to name the new server as the old one and
remove the old one from
>the network.
>Can someone please help me with the same?
>Thank you in advance.
>Regards,
>Karthik
>
>.
>
Hi Chris,
Thank you for the advice. I will test it on on a different machine and let
you know as to how things went.
Thank you once again.
Regards,
Karthik
"ChrisR" wrote:
> My disclaimer: Ive never done this. These are just
> theories.
> I would have to imagine that as long as the new box has
> the same name as the old, and the data files go to the
> same location on the destination as they were on the
> source, you should be good. You should be able just to
> backup/ restore master/ msdb and the user db's should be
> alive and in-tact. No matter what advice you get here, do
> this in a test environment and get backups before you do
> anything.
>
>
> the current server on
> requirements.
> replication in SQL
> transition? I cannot just
> powerful harddisk.
> current publisher on
> replication starts? I will
> remove the old one from
>
theories.
I would have to imagine that as long as the new box has
the same name as the old, and the data files go to the
same location on the destination as they were on the
source, you should be good. You should be able just to
backup/ restore master/ msdb and the user db's should be
alive and in-tact. No matter what advice you get here, do
this in a test environment and get backups before you do
anything.
>--Original Message--
>Hi,
>I need to move my publisher to a different database as
the current server on
>which it is running is slow compared to my current
requirements.
>But I have 2 subscribers to this server. I have merge
replication in SQL
>Server 2k with sp3 on.
>Can someone advice me as to how to have a smooth
transition? I cannot just
>replace the harddisk as the new server has a much
powerful harddisk.
>Is it possible for me to just restore the backup of the
current publisher on
>the new server alongwith the master and msdb, and
replication starts? I will
>take care to name the new server as the old one and
remove the old one from
>the network.
>Can someone please help me with the same?
>Thank you in advance.
>Regards,
>Karthik
>
>.
>
Hi Chris,
Thank you for the advice. I will test it on on a different machine and let
you know as to how things went.
Thank you once again.
Regards,
Karthik
"ChrisR" wrote:
> My disclaimer: Ive never done this. These are just
> theories.
> I would have to imagine that as long as the new box has
> the same name as the old, and the data files go to the
> same location on the destination as they were on the
> source, you should be good. You should be able just to
> backup/ restore master/ msdb and the user db's should be
> alive and in-tact. No matter what advice you get here, do
> this in a test environment and get backups before you do
> anything.
>
>
> the current server on
> requirements.
> replication in SQL
> transition? I cannot just
> powerful harddisk.
> current publisher on
> replication starts? I will
> remove the old one from
>
Subscribe to:
Posts (Atom)