Viewing 15 posts - 46 through 60 (of 90 total)
Hi,
Logging everyone who accessed an object is easy, just add the logging code to the proc. (SELECT SYSTEM_USER)
However I'm pretty sure there's no native way to determine if someone...
September 29, 2008 at 11:01 am
Hi,
I've had them too and I've tried everything to get rid of them. Sometimes disabling replication on the publisher and removing the distribution database works, but most of the time...
September 29, 2008 at 10:49 am
You're getting that just when calling the stored proc or when you run the alter?
If the former, can you send your command you're using to call it?
Have you checked to...
September 29, 2008 at 10:46 am
I do not have any merge replication instances to try this on so this is just a suggestion requiring more research.
According to BOL, SQL Server 2005 creates a table called...
September 29, 2008 at 9:59 am
What version of SQL Server are you using? What type of replication are you using? I'm guessing transactional.
This message means that the record that replication is trying to update in...
September 29, 2008 at 9:31 am
Santhosh,
Your question is too large to write a full step by step answer. I will tell you at a high level how to do it.
First, it is possible to import...
September 29, 2008 at 9:17 am
Probably not if you are going with the instead_of trigger, although you might want to start out with a separate db to test it.
Any idea why you end up with...
September 26, 2008 at 9:13 am
Is the subscriber/merged db separate from the above dbs?
September 25, 2008 at 1:42 pm
MH,
I tried to do this on one of my virtual servers just to see if I could make it work. It can't be done because (for starters) you can't create...
September 25, 2008 at 1:40 pm
When it retries the individual commands does it succeed in replicating them or does that also fail?
If so, does the distribution agent list the record it failed on?
Chris.
September 25, 2008 at 1:17 pm
Well... I think you COULD put an instead_of trigger on the table for the insert event, and then throw out the duplicate record or better yet, log it somewhere so...
September 25, 2008 at 1:14 pm
Steve,
I thought so too, and I've never tried without restoring a backup or applying a snapshot but Peter mentioned the NOSYNC option which I looked up in BOL.
Constant Value...
September 23, 2008 at 9:00 am
We tried that too. Unfortunately, for us we had to get rid of the subscription db, since you can't, probably because it would affect your reporting. Can you try setting...
September 23, 2008 at 8:40 am
Hi Peter,
Sorry, its really difficult to troubleshoot more complex/detailed problems on here.
When you recreated the subscription, did you start with a new subscriber db?
I have not dealt with this...
September 23, 2008 at 6:14 am
How did you get the data to the subscriber when you set up replication the first time around?
September 22, 2008 at 12:04 pm
Viewing 15 posts - 46 through 60 (of 90 total)