sounds like you have highlighted the contents of the procedure for parsing. You can't use return if the Create procedure OR alter procedure statements are not present.

HTH

As soon as the distribution agent starts delivering all transactions the log will be clearing but the size won't be reduced.

Dam! and I thought the dream was becoming reality

Got me

Personally, I would persue Ken's Idea and combine both (select + update) into one statement that way you could get rid of the locking problem:

ex:

UPDATE unprocessed_message 

SET state = @StateNext,

    @id = id,

   ...

To be honest that is a BAD choise.

When you have to hardCode that means that maintainability and Complexity will exponentially grow. I SQL is a better approach to create a...

>>I noticed that the job named:  "Distribution clean up: distribution" job is disabled, by default. 

I looked at BOL "Miscellaneous Agents" and it appears that job only runs for snapshot and...

can you  post the content on the insert trigger in the subscriber table?

And if you keep reading more carefully under the FAST_FORWARD it says:

Specifies a FORWARD_ONLY, READ_ONLY cursor with performance optimizations enabled

>> We had just recently done a similar test, different database, same situation, same cursor type, approx'ly 80k records processed in < 3 minutes.

I would bet a set based can do...

By Looking at the declaration of your cursor you have created a DYNAMIC type and needless to say that is far from optimal (From BOL:The data values, order, and membership...

-Can you post the @@fetch_status ? or it doesn't even gets there?

-Order by should never be used in views. Those are just tricks that harm performance you can always use...

Besides,

You can disable a constraint but you can't disable an index (not yet you can in 2005 )

You can rebuild/Defrag/drop indexes but you drop/create...

Jeswanth,

The inserted and deleted virtual tables are nothing but special tables generated from the transaction log. Deep down an update is nothing but a delete followed by an insert. Therefore...

Have you tried setting up the granularity to the row?

ex: "select * from myTable with (rowlock) where myVarBinaryColumn = @Value1

This statement is invalid:

insert into myTable set myVarBindaryColumn = @Value1

If you...

if you use the same trigger to handle the three possible events you can do this to determine what happened an act accordingly

declare @ins_cnt int, @del_cnt int

select @ins_cnt = count(*)...