Thank you Richard! I will go through them. I appreciate your input

I think I will just push to have our company get out of...

Thank you for you input! I really appreciate the tip.

Yes, I see...thanks for the tip..I will pass that on to the developer. I do not see how that has anything to do with my server coming to a halt...

Yes, I know the purpose of 'timestamp' I just do not see how adding timestamp is going to make this query run more efficent?

What is the purpose of the timestamp? I don't understand.

Here you go..I removed the server name and table name

exec sp_executesql N'UPDATE "<server>".."<table>" SET "PurposeRefinance"=@P1,"EstateHeldIn"=@P2,"SalesPrice"=@P3 WHERE "ClientID"=@P4 AND "subFinancing" IS NULL AND "Originator" IS NULL AND "ThirdPartyName" IS...

Same amount of users..and now that you mention it, I do see a lot of sp_executesql in the trace file..more than half of the queries are sp_executesql.

Would that cause issues?

Thanks, I did create a new thread in the administration  forum. I figured it could be Access as our other servers (11 of them) run fine with sp3a installed. Only this...

I have ran multiple traces and there are no specific queries or stored procs. I have dropped and re-created indexes.

I also want to add that approx 31% of the processes...