Scorpion Thanks for all your info so far.

What is happening is lots of users connect to a SQL server and start a merge replication.

Unfortunately this is quite a big replication......

I have been looking for this notification tab but i could not find it !.

Where can i find it ?

I would say it is always nice to have a default behaviour for a stored proc.

If you dont give it any parameters it will perform the default behaviour.

But when...

Yep but i still don't know what Resource qeue means

and I still don't know if all this qeuing will cause additional overhead on the server ........

It is a mix of SNapshot and Merge replication, it is a PULL replication scenario.

But we have some more info on this...... It seams that the sproc sp_MSAgent_stethoscope is causing...

Sorry forgot the last.....

The Distributor and the publisher is the same machine.....

So there are no Agents running

Andy thanks a Lot for your comments,

I understand most of it But what do you mean with Log Jam ?

And I understood you correct when you say this shouldn't affect...

If the cursor is not that big you could always use a memory table....

Works just like a real table but is faster than a cursor...

Declare @Table Table

( id int,

...

Probably the MAINTPLAN wizzard will put the DB in single user mode and this cannot be done while other connections are in the DB.

The maintplan is executed by the sqlserveragent...

We foud it already was the Server setting.....NO COUNT...

What i am really looking for is a tool that can handle the following situation.

There is a Developement database ( let's say release 3.1.0)

There is a Test database (let's say...

So could we conclude to say.....

If you need to have Dynamic parameters in your sproc

keep the following in mind :

1. If there are a few parameters use seperate stored procedures...

In a reply on Simon Sabin.

I tested your solution but extended it a little.....

set nocount on

set statistics io on

set statistics time on

exec usp_SelectClientAccountManager 2324,null

exec usp_SelectClientAccountManager null,99

exec usp_SelectClientAccountManager2 2324,null

exec usp_SelectClientAccountManager2 null,99

exec...

Well this looks a lot like the discussion we had with optional parameters.

Then i Posted this solution.....

I have some experience with this too and i found out that when you...

If you can stay away from UDF... Build a SP instead. I have had some pretty bad experiences with UDF and you don't know what it is doing because they...