My guess... Trigger is causing excessive locking!

Details on the implementation are needed so that we can help you

You can put those conditions in a table and then perform a join to that table using something like:

select x.*

from x join y on x.[Region Name] Like y.pattern

Cheers !

>>....but still the space is not freed,<<<

Your transaction log may have grown but the space used is definitely marked as unsued, just not released to the OS. Files won't shrink...

1. Sorry that may not be possible

2. If you removed the login that was the owner of that DB you are causing this issue.

That is why is usually a good...

Totally agree

This->That->This->That ... repeat as much as you please

You need to change your mind set to perform that process by SET *not* by ROW just import the XML File ENTIRELY in a temp table then update/delete/insert into ...

Just comment out the delete stored procedure code on the subscriber!

DECLARE @C TABLE (CUSTOMER_ID int, FIELD_NUMBER int, FIELD_VALUE varchar(200) )

INSERT INTO @C (CUSTOMER_ID, FIELD_NUMBER, FIELD_VALUE) VALUES(1,1,'BLUE')

INSERT INTO @C (CUSTOMER_ID, FIELD_NUMBER, FIELD_VALUE) VALUES(1,2,'RED')

INSERT INTO @C...

Good guess? That was pure magic guess!!!! ...

you need to mark all user triggers as "not for replication" just in case you did copy triggers (or someone put one) on the subscriber !

That alert Message Apears as NOT logged on 2000 also.

If you are currently ussing it in 2000 someone/something marked it as logged. You could marked it as logged using...

>>> Our bosses make us accountable. Why don't theirs? <<<

theirs might but is a tough business decision to "fix" bugs beacuse the time spent on that is very unproductive

Happy to help

3604 is to log everytime that deadlock monitor start running DONOT use that 3605 is the guy!

If what you want is to "EXPAND the SERVER NODE" you do need SA.

If what you want is to "query" the remote server then that should be enough!