Do you see anything wrong with this query???

Shouldn't the where condition be more like : where ClientId = @Param3??

This is a huge network load for the query and a lot...

set the identity as (1,1) as usual. Then add a check constraint (Id >=1 and Id <=999)

This seems like a multiple lists form to me. EX :

Load the list of countries, once an item is selected,

Load the regions (states, qhatever)

Load the towns

Then load the clients.

This...

Can you show me a few of the long ones?

I meant in a new message .

This solution is the best in your case (ignore the extra field in the insert) :

INSERT...

Is it more loaded than the other servers (number of users/queries).

Do you see a lot of queries with sp_executesql that have a mile long of parameters?

This is really an admin question, here's the thread link :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=131&messageid=214051

Ya you might wanna repost in administration.. this is not an access problem.

You might want to start a new thread for that question.

Can you post the statement please?

HTH.

Do you know what queries make the proc hit 100% or how many employees it takes?

Here's an exemple of a running total :

declare @pointy table(

id int not null primary key clustered,

point int not null)

insert @pointy (id, point)

SELECT 1,...

EXEC ('DTSRun /~Z0x6979CADB8B8DE884B8BFC34648CBBA20A75783FEBA84F9FD6DB768368C543165C7F301465563DF2967E5070A3659F42283F7888036ED7C15AB190C36E0E82E363163564EACD843AE89ABDB85DD76475BF1E88403FF1164DA3DDFC4984E1D4269DFD058029428C0581C3447 ')

you can create a job from within the dts menus and copy that long id from there.

Why do you want to do exactly?