View Complete Post
Im running transactional replication sql 2008 and have a couple table names with the same name but different schemas. I want to make sure in the replication that the filegroups stay with the subscriber. Is this possible?
Table AAA.Customer on file group A
Table BBB.Customer on file group B
Is there a way to keep these filegroups without rebuilding the index after it has been moved? I noticed there was an option in the replicaiton options to keep file group but it doesn not seem to help. Can you let me know how. THANKS>
I am newbie to SQL 2005 and doing my first project (I am an exchange/AD Consultant). I am trying to do a transactional replcation across a VPN link. I have humdreds and hundreds of tables to be replicated. I have around 100 tables which are
without any primary key. I am using
http://blogs.techrepublic.com.com/howdoi/?p=123 for configuration.
I am able to replicate the tables which are with Primary keys, can't replicate any tables which are without primary keys. I am sure there must be a work around or some solution for the tables without primary keys.
I have a Database which contains about 15 tables that 10 of them should be replicated to another database which its schema is "EXACTLY" same with the publisher. The 5 tables that are not planed to publish, have no rows all over the time (indeed the subscriber
DB is just a template DB that should be synchronized becuase of some reasons)...
At snapshot definition I just set each table to Truncate All rows at initialization level. But the problem was that it drop all indeces automatically and FK Constrains which causes the different schema in subscriber DB. So I dcided to set to Copy ALL of
related objects (indeces,FKs,cluster indeces,triggers ,...) at initialization level. But the problem is with 5 tables that are not published when all their relations with the other 10 tables will be droped at initialization level....Beside of all these problems
I get FK constraint error at initialization time...
Also I should mentioned that my DB version is 2000 SP4.
Did I miss or misunderstood something? or should I choos another solution? or some problem in SQL 2000 and should migrate to 2005 or 2008?
Thanks for your appreciation
When I try to set up a transactional replication, setting it up works fine, but then I get an error from the snapshot assistant:
the execution stops at the table sysdiagrams with the error message that the filed „definition“ uses the type varbinary(max).
There was no specific error code, i.e. the error code displayed was '0'
If I try to set up a snapshot replication the sysdiagrams table is not included and it runs through just fine.
I am looking to see if we have any way to set on the subcsriber to avoid accidental deletes on subscriber tables to avoid the 20598 error(where the publisher is trying to replicate a record not existing(rather deleted in accident) at the subscriber end).
This is for transactional replication
I have a transactional replication between A and B where A replicates its data into B . the schema of A and B are
EXACTLY same. I have a table "t" in both databases which has an
IDENTITY column with name "c" and it is set to be
NOT FOR REPLICATION in both databases. Indeed I have "A.t.c " and "B.t.c " columns. Also I should mentioned that I never do any changes in
B.t table. It should just get the last data from A.t (but because of some reasons I need to have a same schema).
I do the following steps :
1- Add a new row to A.t . (and see the added row in B.t after a few seconds either )
2- update this added row's c2 column (not the c which is the identity and PK column)
3- an exception I receive in Replication Monitor which says I cannot update the
B.t.c column because it is an Identity column!!!... (I checked the related MS's related update stored procedure)...
the question is why it wants to update the Identity column which is not needed indeed!?