definitely a learning experience After looking at the sql profiler trace again I see what's happening.

The conflict occurs because of the column constraint. It can't update EM_ID in...

i don't understand how or why they want to use it as a 'security view' and I didn't realize that you could compute the date and time into...

did not find an update statement.. lock aquired, lock released.. over and over again

i set up profiler to pick up everthing.. aside from all the selects.. i'm just seeing lots of these..

exec sp_cursorfetch 180151353, 2, 1, 1

Did I set up profiler...

Profiler....

declare @P1 int

set @P1=-1

declare @P2 int

set @P2=0

declare @P3 int

set @P3=1

declare @P4 int

set @P4=8196

declare @P5 int

set @P5=0

exec sp_cursorprepexec @P1 output, @P2 output, NULL, N'SELECT em_id,em_std FROM em ORDER BY em_id', @P3...

I think the application is trying to modify the em_id field which contains employee names. It does not look like the constraint was created with 'no check'...

successfully Dropped my article from the publication using sp_droparticle.

I truncated the table on my subcriber side and then did a snaphot and let everything sync back up.

I re-added the...

ok.. I understand that the procedure would be no different if the DIST agent is running or not.. but what WOULD be the procedure for droppin/re-adding an article?

which should I do first?

exec sp_dropsubscription @publication = N'TowerDB to KOCSQL03', @article = N'cbl', @subscriber = N'all', @destination_db = N'all'

exec sp_droparticle @publication = N'TowerDB to KOCSQL03', @article = N'cbl',...

Here we go again.. a DR Test but a short one this time.. only a couple of hours.

While my distribution job is disabled, what would the proper procedure...

can anyone help me with the proper steps to drop this article from the subscription and then re-add it?

I cannot find a snapshot folder on my publishing server.

what would be the correct steps to drop and recreate this article for relication?

any fix for this??? urgent today!!!!!!!!!!!

we end up repartiioning and reinstalling.. no big deal. server is all recovered (thanks)

NOW er are getting this:: Cannot generate SSPI context" when trying to connect to...

awesome. thank you