Viewing 9 posts - 1 through 9 (of 9 total)
Thanks Ray.
The script I want to run is from the software provider and will invariably have to run similar scripts again with later versions. What I would really like to...
October 25, 2006 at 7:57 am
At the publisher (DOMAIN_A\NAME1) I have registered the subscriber using it's IP address. At the subscriber (DOMAIN_B\NAME2) I have registered it as it's IP address and registered the publisher as...
June 23, 2006 at 7:09 am
I have users set up as local admin and SQL system admin at both subscriber and publisher.
I'm not sure it's a permissions thing, as it can't even find the server...
June 22, 2006 at 11:06 am
I'm fairly new to replication but if I understand your question correctly.....
I got round this by creating a second publication with only the views selected. I can reinitialise this easily...
April 26, 2006 at 8:48 am
Thanks for your help everyone.
I have added the 'not for replication' to the triggers (at both publisher and subscriber) and as yet have been unable to deliberately create conflicts. Maybe this is...
February 15, 2006 at 5:16 am
Thankyou very much for your help. I have altered the triggers and will see how it goes.
Regards
Cayley
February 10, 2006 at 11:25 am
Its acutally a trigger causing the errors rather than just the FK relationship. Certainly there is nothing in the relationships tab for the table properties so I can't turn it...
February 10, 2006 at 8:02 am
The replication is needs to insert into both tables A and B. On the the other two replication databases the insert of parent into A appears to happen first as...
February 10, 2006 at 5:23 am
Thanks for your help. I agree - it's probably not the replication randomly ordering things wrong, but I've must have pressed something different somewhere which has caused the problem. Trouble is I...
February 9, 2006 at 1:15 pm
Viewing 9 posts - 1 through 9 (of 9 total)