I have three locations each with multiple SQL 2000 databases that need to
stay in constant sync with the other locations. Which is the best type of
replication? Merge Replication or 2-way Transactional Replication?
TIA,
Kevin
Probably peer to peer in SQL 2005. However bi-directional transactional
would probably be best. Keep in mind you are locked into a schema with this.
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
"Kevin Eckart" <eckart_612@.hotmail.com> wrote in message
news:e4PRqHGTHHA.3428@.TK2MSFTNGP04.phx.gbl...
>I have three locations each with multiple SQL 2000 databases that need to
>stay in constant sync with the other locations. Which is the best type of
>replication? Merge Replication or 2-way Transactional Replication?
> TIA,
> Kevin
>
|||Schema issues are the reason I posted this question in the first place. In
my test scenario, I have 3 servers doing merge replication back and forth to
each other. Each server subscribes to the other two. Everything was working
fine until I tried to add a column for testing. I got the following error
message:
Schema replication failed because database X on server X is not the original
Publisher of table
Any ideas?
Kevin
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uMWCuhGTHHA.5016@.TK2MSFTNGP05.phx.gbl...
> Probably peer to peer in SQL 2005. However bi-directional transactional
> would probably be best. Keep in mind you are locked into a schema with
> this.
> --
> 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
>
> "Kevin Eckart" <eckart_612@.hotmail.com> wrote in message
> news:e4PRqHGTHHA.3428@.TK2MSFTNGP04.phx.gbl...
>
|||Do you have a hierarchy? IE Server A publishes to Server B which publishes
to Server C? Is so you must make the schema change at the top of the
hierarchy.
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
"Kevin Eckart" <eckart_612@.hotmail.com> wrote in message
news:emdknlGTHHA.2256@.TK2MSFTNGP02.phx.gbl...
> Schema issues are the reason I posted this question in the first place. In
> my test scenario, I have 3 servers doing merge replication back and forth
> to each other. Each server subscribes to the other two. Everything was
> working fine until I tried to add a column for testing. I got the
> following error message:
> Schema replication failed because database X on server X is not the
> original Publisher of table
> Any ideas?
> Kevin
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uMWCuhGTHHA.5016@.TK2MSFTNGP05.phx.gbl...
>
|||I do not have a heirarchy. The topology I would like to use is a sort of
triangle, with no one server being the master and all transactions shared.
Thanks,
kevin
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OXSz4XHTHHA.1200@.TK2MSFTNGP02.phx.gbl...
> Do you have a hierarchy? IE Server A publishes to Server B which publishes
> to Server C? Is so you must make the schema change at the top of the
> hierarchy.
> --
> 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
>
> "Kevin Eckart" <eckart_612@.hotmail.com> wrote in message
> news:emdknlGTHHA.2256@.TK2MSFTNGP02.phx.gbl...
>
|||You are talking about a multi-master topology which merge replication does
not support. You will need to use peer-to-peer in SQL Server 2005 for this.
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
"Kevin Eckart" <eckart_612@.hotmail.com> wrote in message
news:eemppbHTHHA.1036@.TK2MSFTNGP03.phx.gbl...
>I do not have a heirarchy. The topology I would like to use is a sort of
>triangle, with no one server being the master and all transactions shared.
> Thanks,
> kevin
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OXSz4XHTHHA.1200@.TK2MSFTNGP02.phx.gbl...
>
|||Kevin - just checking why you don't set up one merge publisher and 2 merge
subscribers. Is it because we don't have alternative sync partners anymore
and you can't guarantee connectivity with the publisher?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Yes Paul, I need sort of a triangle setup with each node working
independently and then sharing information with the other two.
Hilary, is Peer-to-Peer replication available in 2005 Standard? I took a
quick look at the replication options on our 2005 boxes on Friday and didn't
see anything about Peer-to-Peer.
Kevin
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:e3pPvcITHHA.4756@.TK2MSFTNGP06.phx.gbl...
> Kevin - just checking why you don't set up one merge publisher and 2 merge
> subscribers. Is it because we don't have alternative sync partners anymore
> and you can't guarantee connectivity with the publisher?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
|||It is only available on the Enterprise Editions of SQL Server 2005.
You will be able to get it working using pure bi-directional transactional
replication but will probably have to do some filtering to get it to work
correctly.
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
"Kevin Eckart" <eckart_612@.hotmail.com> wrote in message
news:e08ed4qTHHA.600@.TK2MSFTNGP05.phx.gbl...
> Yes Paul, I need sort of a triangle setup with each node working
> independently and then sharing information with the other two.
> Hilary, is Peer-to-Peer replication available in 2005 Standard? I took a
> quick look at the replication options on our 2005 boxes on Friday and
> didn't see anything about Peer-to-Peer.
> Kevin
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:e3pPvcITHHA.4756@.TK2MSFTNGP06.phx.gbl...
>
|||Kevin,
what you are proposing is not in conflict with the merge setup, as you
mention the data is exchanges with the other 2 nodes. If this is a
prerequisite, then the connectivity must exist and the merge setup remains
an option. It doesn't perform any where near as well as peer to peer (only
enterpriose as you mentioned
http://msdn2.microsoft.com/en-us/library/ms143761.aspx) , but has the
advantage of easily adapting to schema changes and conflicts.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Showing posts with label sync. Show all posts
Showing posts with label sync. Show all posts
Friday, March 30, 2012
Replication Test\Check 6.5 & 2000 are in sync
Hi,
I am having MSSQL 6.5 with batch driven transactions
I am upgrading to 2000 and plan to do some black box
testing.
To test the batch jobs,I am planning to run the job on 6.5
and 2000 and test the rowcounts and records added/updated
based on datetime.(I don't have delete..so checking the
data on the basis of timestamp works)
However my rowcount and timestamp queries take a long time
to run on 6.5.(More than 50 mins as data volume and no of
tables are high)
I can't wait that long as the production server 6.5 has
jobs that run after every 30 mins.Is there a way just to
check whether 6.5 and 2000 data are in sync using some
built in utility or better algortithm(I don't want to
compare using SQL,but comparison at the lower level such
as file etc would do)
Basically do something like what replication or mirroring
does but not actually move the data but just check
Thanks
RakeshTake a look at the sp sp_replcounters... It shows how many records in the
log are awaiting replication...
"ar" <ambewadkarrakesh@.johndeere.com> wrote in message
news:05fb01c344f6$cb8265b0$a501280a@.phx.gbl...
> Hi,
> I am having MSSQL 6.5 with batch driven transactions
> I am upgrading to 2000 and plan to do some black box
> testing.
> To test the batch jobs,I am planning to run the job on 6.5
> and 2000 and test the rowcounts and records added/updated
> based on datetime.(I don't have delete..so checking the
> data on the basis of timestamp works)
> However my rowcount and timestamp queries take a long time
> to run on 6.5.(More than 50 mins as data volume and no of
> tables are high)
> I can't wait that long as the production server 6.5 has
> jobs that run after every 30 mins.Is there a way just to
> check whether 6.5 and 2000 data are in sync using some
> built in utility or better algortithm(I don't want to
> compare using SQL,but comparison at the lower level such
> as file etc would do)
> Basically do something like what replication or mirroring
> does but not actually move the data but just check
> Thanks
> Rakesh
I am having MSSQL 6.5 with batch driven transactions
I am upgrading to 2000 and plan to do some black box
testing.
To test the batch jobs,I am planning to run the job on 6.5
and 2000 and test the rowcounts and records added/updated
based on datetime.(I don't have delete..so checking the
data on the basis of timestamp works)
However my rowcount and timestamp queries take a long time
to run on 6.5.(More than 50 mins as data volume and no of
tables are high)
I can't wait that long as the production server 6.5 has
jobs that run after every 30 mins.Is there a way just to
check whether 6.5 and 2000 data are in sync using some
built in utility or better algortithm(I don't want to
compare using SQL,but comparison at the lower level such
as file etc would do)
Basically do something like what replication or mirroring
does but not actually move the data but just check
Thanks
RakeshTake a look at the sp sp_replcounters... It shows how many records in the
log are awaiting replication...
"ar" <ambewadkarrakesh@.johndeere.com> wrote in message
news:05fb01c344f6$cb8265b0$a501280a@.phx.gbl...
> Hi,
> I am having MSSQL 6.5 with batch driven transactions
> I am upgrading to 2000 and plan to do some black box
> testing.
> To test the batch jobs,I am planning to run the job on 6.5
> and 2000 and test the rowcounts and records added/updated
> based on datetime.(I don't have delete..so checking the
> data on the basis of timestamp works)
> However my rowcount and timestamp queries take a long time
> to run on 6.5.(More than 50 mins as data volume and no of
> tables are high)
> I can't wait that long as the production server 6.5 has
> jobs that run after every 30 mins.Is there a way just to
> check whether 6.5 and 2000 data are in sync using some
> built in utility or better algortithm(I don't want to
> compare using SQL,but comparison at the lower level such
> as file etc would do)
> Basically do something like what replication or mirroring
> does but not actually move the data but just check
> Thanks
> Rakesh
Wednesday, March 28, 2012
Replication Sync on Windows Vista
On windows XP there is a Synchronize program in Accessories. When I run our replication scripts on a SQL Server Express on the XP machine and start the Synchronize program there are items there that allow me to replicate as well as set a schedule, etc.
On Windows Vista there is a Sync Center, but replication doesn't show up here.
I've searched high and low on Google and am not coming up with anything useful, which leads me to believe this is something very simple that I'm overlooking...
Does anyone know how to make your replication show up on the Sync Center in vista, or is there another application that I should download?
Thanks,
Brian
I could be wrong, but I do not believe those are the same. I think Sync Manager in Vista is a built-in tool for synchronizing PDA's and thing like that. However, so I do not mis-speak, I am testing that now because we are also at the point of testing synchronization with Vista.
I will let you know what i find.
Scott
|||To add files to Sync Center, on the (Vista) machine you want to have the offline copy on, open explorer and navigate to the network share the original file or directory is on. Right-click and on the context menu select "Always Available Online." The SyncCenter icon will be superimposed on the icon to show it is being copied.Replication Sync on Windows Vista
On windows XP there is a Synchronize program in Accessories. When I run our replication scripts on a SQL Server Express on the XP machine and start the Synchronize program there are items there that allow me to replicate as well as set a schedule, etc.
On Windows Vista there is a Sync Center, but replication doesn't show up here.
I've searched high and low on Google and am not coming up with anything useful, which leads me to believe this is something very simple that I'm overlooking...
Does anyone know how to make your replication show up on the Sync Center in vista, or is there another application that I should download?
Thanks,
Brian
I could be wrong, but I do not believe those are the same. I think Sync Manager in Vista is a built-in tool for synchronizing PDA's and thing like that. However, so I do not mis-speak, I am testing that now because we are also at the point of testing synchronization with Vista.
I will let you know what i find.
Scott
|||To add files to Sync Center, on the (Vista) machine you want to have the offline copy on, open explorer and navigate to the network share the original file or directory is on. Right-click and on the context menu select "Always Available Online." The SyncCenter icon will be superimposed on the icon to show it is being copied.Wednesday, March 21, 2012
Replication problem(integrity violation) - Cannot Sync up emulator -HELP!
Can somebody help please - i keep getting this erro when trying to sycn
up my emulator to my Merged Replication DB.
"The row update or insert cannot be reapplied due to an integrity
violation. [,,,,,]"
Anybody know what this problem could be? I have recently dropped an
recreated a lot of my tables and changed some data types but did not
think it would effect me this badly.
I have also disabled and re-enabled my merge replication db many times.
I am sure all my connection settings are correct and the problem
appears to be deeper than that.
Recently i have changed the constraint on all of my tables to "Not to
enforce relationships on insert / update". It seems like this is what
the emulator is trying to do though?
Suggestions GREATLY appreciated!!!!
Thanks,
Steve
When you disable these constraints it means they will be fired twice.
The first time do to the originating action, the second time due to the
replicated command. This is probably not what you want unless you do not
have cascading updates and deletes on your subscriber.
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
"steroche" <steroche@.gmail.com> wrote in message
news:1125268893.110010.148790@.g44g2000cwa.googlegr oups.com...
> Can somebody help please - i keep getting this erro when trying to sycn
> up my emulator to my Merged Replication DB.
>
> "The row update or insert cannot be reapplied due to an integrity
> violation. [,,,,,]"
> Anybody know what this problem could be? I have recently dropped an
> recreated a lot of my tables and changed some data types but did not
> think it would effect me this badly.
> I have also disabled and re-enabled my merge replication db many times.
> I am sure all my connection settings are correct and the problem
> appears to be deeper than that.
> Recently i have changed the constraint on all of my tables to "Not to
> enforce relationships on insert / update". It seems like this is what
> the emulator is trying to do though?
> Suggestions GREATLY appreciated!!!!
> Thanks,
> Steve
>
up my emulator to my Merged Replication DB.
"The row update or insert cannot be reapplied due to an integrity
violation. [,,,,,]"
Anybody know what this problem could be? I have recently dropped an
recreated a lot of my tables and changed some data types but did not
think it would effect me this badly.
I have also disabled and re-enabled my merge replication db many times.
I am sure all my connection settings are correct and the problem
appears to be deeper than that.
Recently i have changed the constraint on all of my tables to "Not to
enforce relationships on insert / update". It seems like this is what
the emulator is trying to do though?
Suggestions GREATLY appreciated!!!!
Thanks,
Steve
When you disable these constraints it means they will be fired twice.
The first time do to the originating action, the second time due to the
replicated command. This is probably not what you want unless you do not
have cascading updates and deletes on your subscriber.
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
"steroche" <steroche@.gmail.com> wrote in message
news:1125268893.110010.148790@.g44g2000cwa.googlegr oups.com...
> Can somebody help please - i keep getting this erro when trying to sycn
> up my emulator to my Merged Replication DB.
>
> "The row update or insert cannot be reapplied due to an integrity
> violation. [,,,,,]"
> Anybody know what this problem could be? I have recently dropped an
> recreated a lot of my tables and changed some data types but did not
> think it would effect me this badly.
> I have also disabled and re-enabled my merge replication db many times.
> I am sure all my connection settings are correct and the problem
> appears to be deeper than that.
> Recently i have changed the constraint on all of my tables to "Not to
> enforce relationships on insert / update". It seems like this is what
> the emulator is trying to do though?
> Suggestions GREATLY appreciated!!!!
> Thanks,
> Steve
>
Replication problem(integrity violation) - Cannot Sync up emulator -HELP!
Can somebody help please - i keep getting this erro when trying to sycn
up my emulator to my Merged Replication DB. When i look into he error
message via the VS debugger i can see this text in the SqlException
error:
"The row update or insert cannot be reapplied due to an integrity
violation. [,,,,,]"
Anybody know what this problem could be? I have recently dropped an
recreated a lot of my tables and changed some data types but did not
think it would effect me this badly.
I have also disabled and re-enabled my merge replication db many times.
I am sure all my connection settings are correct and the problem
appears to be deeper than that.
Recently i have changed the constraint on all of my tables to "Not to
enforce relationships on insert / update". It seems like this is what
the emulator is trying to do though'
Suggestions GREATLY appreciated!!!!
Thanks,
SteveHi
Is this any help?
http://support.microsoft.com/default.aspx?scid=kb;en-us;889521
You may want to try logging the updates:
http://support.microsoft.com/default.aspx?scid=kb;en-us;312292
John
"steroche" wrote:
> Can somebody help please - i keep getting this erro when trying to sycn
> up my emulator to my Merged Replication DB. When i look into he error
> message via the VS debugger i can see this text in the SqlException
> error:
> "The row update or insert cannot be reapplied due to an integrity
> violation. [,,,,,]"
>
> Anybody know what this problem could be? I have recently dropped an
> recreated a lot of my tables and changed some data types but did not
> think it would effect me this badly.
>
> I have also disabled and re-enabled my merge replication db many times.
> I am sure all my connection settings are correct and the problem
> appears to be deeper than that.
>
> Recently i have changed the constraint on all of my tables to "Not to
> enforce relationships on insert / update". It seems like this is what
> the emulator is trying to do though'
>
> Suggestions GREATLY appreciated!!!!
> Thanks,
> Steve
>|||Im afraid not. I have tried everything at this stage and its driving me
crazy!!!!!
I have re-published my database about 10times i'd say and i always get
an error.
Generally I get one of 2 errors. If i have already created the database
the errors are:
Message "Row data cannot be set. [,,,,,]"
NativeError 28572
and
Message "Invalid row handle"
NativeError 0
However if i dont have it created previous to running it and it creates
it itself I get the error:
message "Run"
NativeError 28557
Message "The row update or insert cannot be reapplied due to an
integrity violation. [,,,,,]
NativeError 28549
What the hell is going on' I have checked all the tables to make sure
that the checkbox "Enforce Relationship for replication" IS checked so
the NOT FOR REPLICATION bug doesn't apply here.
I have checked over all my datatypes and relationships and the data
that they contain to ensure that there can be no FK conflicts.
I know the table is being created as i can see it on the CE Query
analyser but it contains no tables so this probably gives rise to the
second error but why is it not creating the db properly in the first
place'
I heard that compacting the db might help - how do i do that'|||Hi
Unfortunately I am not an expert on replication!
Hilary Cotter who has replied in microsoft.public.sqlserver.replication
knows alot more about replication than I.
John
"steroche" wrote:
> Im afraid not. I have tried everything at this stage and its driving me
> crazy!!!!!
> I have re-published my database about 10times i'd say and i always get
> an error.
> Generally I get one of 2 errors. If i have already created the database
> the errors are:
> Message "Row data cannot be set. [,,,,,]"
> NativeError 28572
> and
> Message "Invalid row handle"
> NativeError 0
> However if i dont have it created previous to running it and it creates
> it itself I get the error:
> message "Run"
> NativeError 28557
> Message "The row update or insert cannot be reapplied due to an
> integrity violation. [,,,,,]
> NativeError 28549
> What the hell is going on' I have checked all the tables to make sure
> that the checkbox "Enforce Relationship for replication" IS checked so
> the NOT FOR REPLICATION bug doesn't apply here.
> I have checked over all my datatypes and relationships and the data
> that they contain to ensure that there can be no FK conflicts.
> I know the table is being created as i can see it on the CE Query
> analyser but it contains no tables so this probably gives rise to the
> second error but why is it not creating the db properly in the first
> place'
> I heard that compacting the db might help - how do i do that'
>|||Check that your subset filters and merge filters in the publication are
correctly constructed.
You are potentially sending down some data on a foreign key that is getting
filtered out.
Rob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:F13AC93E-5354-4A2F-A066-2B3D22AA6D8F@.microsoft.com...
> Hi
> Unfortunately I am not an expert on replication!
> Hilary Cotter who has replied in microsoft.public.sqlserver.replication
> knows alot more about replication than I.
> John
> "steroche" wrote:
>> Im afraid not. I have tried everything at this stage and its driving me
>> crazy!!!!!
>> I have re-published my database about 10times i'd say and i always get
>> an error.
>> Generally I get one of 2 errors. If i have already created the database
>> the errors are:
>> Message "Row data cannot be set. [,,,,,]"
>> NativeError 28572
>> and
>> Message "Invalid row handle"
>> NativeError 0
>> However if i dont have it created previous to running it and it creates
>> it itself I get the error:
>> message "Run"
>> NativeError 28557
>> Message "The row update or insert cannot be reapplied due to an
>> integrity violation. [,,,,,]
>> NativeError 28549
>> What the hell is going on' I have checked all the tables to make sure
>> that the checkbox "Enforce Relationship for replication" IS checked so
>> the NOT FOR REPLICATION bug doesn't apply here.
>> I have checked over all my datatypes and relationships and the data
>> that they contain to ensure that there can be no FK conflicts.
>> I know the table is being created as i can see it on the CE Query
>> analyser but it contains no tables so this probably gives rise to the
>> second error but why is it not creating the db properly in the first
>> place'
>> I heard that compacting the db might help - how do i do that'
>>
up my emulator to my Merged Replication DB. When i look into he error
message via the VS debugger i can see this text in the SqlException
error:
"The row update or insert cannot be reapplied due to an integrity
violation. [,,,,,]"
Anybody know what this problem could be? I have recently dropped an
recreated a lot of my tables and changed some data types but did not
think it would effect me this badly.
I have also disabled and re-enabled my merge replication db many times.
I am sure all my connection settings are correct and the problem
appears to be deeper than that.
Recently i have changed the constraint on all of my tables to "Not to
enforce relationships on insert / update". It seems like this is what
the emulator is trying to do though'
Suggestions GREATLY appreciated!!!!
Thanks,
SteveHi
Is this any help?
http://support.microsoft.com/default.aspx?scid=kb;en-us;889521
You may want to try logging the updates:
http://support.microsoft.com/default.aspx?scid=kb;en-us;312292
John
"steroche" wrote:
> Can somebody help please - i keep getting this erro when trying to sycn
> up my emulator to my Merged Replication DB. When i look into he error
> message via the VS debugger i can see this text in the SqlException
> error:
> "The row update or insert cannot be reapplied due to an integrity
> violation. [,,,,,]"
>
> Anybody know what this problem could be? I have recently dropped an
> recreated a lot of my tables and changed some data types but did not
> think it would effect me this badly.
>
> I have also disabled and re-enabled my merge replication db many times.
> I am sure all my connection settings are correct and the problem
> appears to be deeper than that.
>
> Recently i have changed the constraint on all of my tables to "Not to
> enforce relationships on insert / update". It seems like this is what
> the emulator is trying to do though'
>
> Suggestions GREATLY appreciated!!!!
> Thanks,
> Steve
>|||Im afraid not. I have tried everything at this stage and its driving me
crazy!!!!!
I have re-published my database about 10times i'd say and i always get
an error.
Generally I get one of 2 errors. If i have already created the database
the errors are:
Message "Row data cannot be set. [,,,,,]"
NativeError 28572
and
Message "Invalid row handle"
NativeError 0
However if i dont have it created previous to running it and it creates
it itself I get the error:
message "Run"
NativeError 28557
Message "The row update or insert cannot be reapplied due to an
integrity violation. [,,,,,]
NativeError 28549
What the hell is going on' I have checked all the tables to make sure
that the checkbox "Enforce Relationship for replication" IS checked so
the NOT FOR REPLICATION bug doesn't apply here.
I have checked over all my datatypes and relationships and the data
that they contain to ensure that there can be no FK conflicts.
I know the table is being created as i can see it on the CE Query
analyser but it contains no tables so this probably gives rise to the
second error but why is it not creating the db properly in the first
place'
I heard that compacting the db might help - how do i do that'|||Hi
Unfortunately I am not an expert on replication!
Hilary Cotter who has replied in microsoft.public.sqlserver.replication
knows alot more about replication than I.
John
"steroche" wrote:
> Im afraid not. I have tried everything at this stage and its driving me
> crazy!!!!!
> I have re-published my database about 10times i'd say and i always get
> an error.
> Generally I get one of 2 errors. If i have already created the database
> the errors are:
> Message "Row data cannot be set. [,,,,,]"
> NativeError 28572
> and
> Message "Invalid row handle"
> NativeError 0
> However if i dont have it created previous to running it and it creates
> it itself I get the error:
> message "Run"
> NativeError 28557
> Message "The row update or insert cannot be reapplied due to an
> integrity violation. [,,,,,]
> NativeError 28549
> What the hell is going on' I have checked all the tables to make sure
> that the checkbox "Enforce Relationship for replication" IS checked so
> the NOT FOR REPLICATION bug doesn't apply here.
> I have checked over all my datatypes and relationships and the data
> that they contain to ensure that there can be no FK conflicts.
> I know the table is being created as i can see it on the CE Query
> analyser but it contains no tables so this probably gives rise to the
> second error but why is it not creating the db properly in the first
> place'
> I heard that compacting the db might help - how do i do that'
>|||Check that your subset filters and merge filters in the publication are
correctly constructed.
You are potentially sending down some data on a foreign key that is getting
filtered out.
Rob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:F13AC93E-5354-4A2F-A066-2B3D22AA6D8F@.microsoft.com...
> Hi
> Unfortunately I am not an expert on replication!
> Hilary Cotter who has replied in microsoft.public.sqlserver.replication
> knows alot more about replication than I.
> John
> "steroche" wrote:
>> Im afraid not. I have tried everything at this stage and its driving me
>> crazy!!!!!
>> I have re-published my database about 10times i'd say and i always get
>> an error.
>> Generally I get one of 2 errors. If i have already created the database
>> the errors are:
>> Message "Row data cannot be set. [,,,,,]"
>> NativeError 28572
>> and
>> Message "Invalid row handle"
>> NativeError 0
>> However if i dont have it created previous to running it and it creates
>> it itself I get the error:
>> message "Run"
>> NativeError 28557
>> Message "The row update or insert cannot be reapplied due to an
>> integrity violation. [,,,,,]
>> NativeError 28549
>> What the hell is going on' I have checked all the tables to make sure
>> that the checkbox "Enforce Relationship for replication" IS checked so
>> the NOT FOR REPLICATION bug doesn't apply here.
>> I have checked over all my datatypes and relationships and the data
>> that they contain to ensure that there can be no FK conflicts.
>> I know the table is being created as i can see it on the CE Query
>> analyser but it contains no tables so this probably gives rise to the
>> second error but why is it not creating the db properly in the first
>> place'
>> I heard that compacting the db might help - how do i do that'
>>
Replication problem(integrity violation) - Cannot Sync up emul
Hi
Unfortunately I am not an expert on replication!
Hilary Cotter who has replied in microsoft.public.sqlserver.replication
knows alot more about replication than I.
John
"steroche" wrote:
> Im afraid not. I have tried everything at this stage and its driving me
> crazy!!!!!
> I have re-published my database about 10times i'd say and i always get
> an error.
> Generally I get one of 2 errors. If i have already created the database
> the errors are:
> Message "Row data cannot be set. [,,,,,]"
> NativeError 28572
> and
> Message "Invalid row handle"
> NativeError 0
> However if i dont have it created previous to running it and it creates
> it itself I get the error:
> message "Run"
> NativeError 28557
> Message "The row update or insert cannot be reapplied due to an
> integrity violation. [,,,,,]
> NativeError 28549
> What the hell is going on' I have checked all the tables to make sure
> that the checkbox "Enforce Relationship for replication" IS checked so
> the NOT FOR REPLICATION bug doesn't apply here.
> I have checked over all my datatypes and relationships and the data
> that they contain to ensure that there can be no FK conflicts.
> I know the table is being created as i can see it on the CE Query
> analyser but it contains no tables so this probably gives rise to the
> second error but why is it not creating the db properly in the first
> place'
> I heard that compacting the db might help - how do i do that'
>Check that your subset filters and merge filters in the publication are
correctly constructed.
You are potentially sending down some data on a foreign key that is getting
filtered out.
Rob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:F13AC93E-5354-4A2F-A066-2B3D22AA6D8F@.microsoft.com...
> Hi
> Unfortunately I am not an expert on replication!
> Hilary Cotter who has replied in microsoft.public.sqlserver.replication
> knows alot more about replication than I.
> John
> "steroche" wrote:
>sql
Unfortunately I am not an expert on replication!
Hilary Cotter who has replied in microsoft.public.sqlserver.replication
knows alot more about replication than I.
John
"steroche" wrote:
> Im afraid not. I have tried everything at this stage and its driving me
> crazy!!!!!
> I have re-published my database about 10times i'd say and i always get
> an error.
> Generally I get one of 2 errors. If i have already created the database
> the errors are:
> Message "Row data cannot be set. [,,,,,]"
> NativeError 28572
> and
> Message "Invalid row handle"
> NativeError 0
> However if i dont have it created previous to running it and it creates
> it itself I get the error:
> message "Run"
> NativeError 28557
> Message "The row update or insert cannot be reapplied due to an
> integrity violation. [,,,,,]
> NativeError 28549
> What the hell is going on' I have checked all the tables to make sure
> that the checkbox "Enforce Relationship for replication" IS checked so
> the NOT FOR REPLICATION bug doesn't apply here.
> I have checked over all my datatypes and relationships and the data
> that they contain to ensure that there can be no FK conflicts.
> I know the table is being created as i can see it on the CE Query
> analyser but it contains no tables so this probably gives rise to the
> second error but why is it not creating the db properly in the first
> place'
> I heard that compacting the db might help - how do i do that'
>Check that your subset filters and merge filters in the publication are
correctly constructed.
You are potentially sending down some data on a foreign key that is getting
filtered out.
Rob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:F13AC93E-5354-4A2F-A066-2B3D22AA6D8F@.microsoft.com...
> Hi
> Unfortunately I am not an expert on replication!
> Hilary Cotter who has replied in microsoft.public.sqlserver.replication
> knows alot more about replication than I.
> John
> "steroche" wrote:
>sql
Monday, March 12, 2012
Replication or Log shipping
If i want to my test server database should be in sync with my prod database,
which one is the best. after complete data sync i dont want any data updates.
i am going to setting up only one way, from prod to test.
please advise if any risks or issues
John,
please take a look here and post back with any questions:
http://www.replicationanswers.com/Standby.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I know it Paul, i saw in your web site in the past. just curious if any other
issues or concerns.
thanks to you and Hilary, may god bless you two people for saving so many
DBA's tough time.
thanks once again
"Paul Ibison" wrote:
> John,
> please take a look here and post back with any questions:
> http://www.replicationanswers.com/Standby.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
which one is the best. after complete data sync i dont want any data updates.
i am going to setting up only one way, from prod to test.
please advise if any risks or issues
John,
please take a look here and post back with any questions:
http://www.replicationanswers.com/Standby.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I know it Paul, i saw in your web site in the past. just curious if any other
issues or concerns.
thanks to you and Hilary, may god bless you two people for saving so many
DBA's tough time.
thanks once again
"Paul Ibison" wrote:
> John,
> please take a look here and post back with any questions:
> http://www.replicationanswers.com/Standby.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Wednesday, March 7, 2012
Replication Monitor Question
Hello,
We have some mobile devices that are setup to replicate with our sql 2005 server via web sync. It seems that the devices are added multiple times within replication monitor. Is there a way to purge the bogus items. For example we have a mobile unit labeled as Device12 we have it listed under the subscriptions 5x. I would like to purge four of them as they are not currently being the replicated one.
Device12-A6EE69A0944 is the valid subscription
Device12-EE44D1EF3E24 is an invalid one.
Thanks in advance.
John
You may want to query table dbo.MSsubscriptions in the distribution database to see if it has those extra entries. I'm not saying it's safe to delete them, but I'm guessing that's where sql monitor is pulling those rogue entries from.
Subscribe to:
Posts (Atom)