 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Replication / October 2006Not for Replication in merge replication - help needed
Hello, I have a merge Replication database with 50 tables. Almost all my tables have identity columns. Now the subscribers of this Publication database cannot "Insert" or "Delete" data on tables that have identity columns. My question is , Would it be better to set the "Not for Replication" on , on every identity column ?Would this make the Whole Replication issue to work faster and better. Thanks a lot. Savvas Christodoulou It would make it work. AFAIK you will not get any performance benefits though.  SignatureHilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 > Hello, > [quoted text clipped - 9 lines] > > Savvas Christodoulou Well if i set the "Not For Replication" to False so the identity columns will be used in the subscribers , would this create any issues when I update , insert new , or delete rows in the Publicated database? And another question I have a table with 130.000 rows on the subscriber with the "Not For Replication" set to true and this table has no indexes, and i expirience slow performance in reading or writing in this table , is this cause by the fact that i dont have any indexes on this table or by the fact that the "Not for replication" is set to true. The table has about 35 columns. Thanks You need the not for replication property on your subscriber tables if the replication process will be inserting identity values into your tables. If the replication process will not, you are ok. So with the not for replication property inserts on the publisher work on the publisher and the replication process replicating these inserts to the subscriber will work. If you do not have this property the replicated inserts applied on the subscriber will fail, but succeed on the subscriber. SignatureHilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 > Well if i set the "Not For Replication" to False so the identity > columns will be used in the subscribers , would this create any issues [quoted text clipped - 10 lines] > > Thanks Hello again, About the speed issue that i have in a table let me tell you more thinks about that its a table that has about 35 columns most int fields and decimal fields and about 15.000 Rows. I used the Query Analyser 3.0 on the Handeheld and i compact the database After that my slow query (3secs) went to maybe 0.5 secs. That was the fault on the speed? Can i compact programmatically the database, using vb.net? Are there any implications on synchronization after the compacting?Seems that there are not cause i sync. ok after that Regards Savvas |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.