are you using parameters from the asp page?

the datatype of the parameter is probably the issue in this case;

can you show us how the parameter is being passed to your...

well this stands out to me:

that means some, or many of the columns might be null...for me,that alone would...

we'd have to see your code, but are you doing something like this? remember @@ROWCOUNT gets reset with EVERY command, including SET operations, so you have to be careful.

DECLARE @mycount...

couldn't help but think of an old cowboy movie with someone saying "Them Thar is Fightin' Words!"

lol...i use it myself whenever i feel like it...but can i justify using it at all; it was the fastest to grab tool in the toolbox...nah, can't justify myself at...

following up on what Ron said, my google search lead me to lots of pdf files, as well as some information about creating UB92 or it's "digital equivilent"

is this just...

on windows 7 machines, security is tighter...local users are not automatically added as SQL administrators unless you specifically add them;

easiest way,since you said SQL 2005, is to use the surface...

that stored proc is used inside other system procedures...if you were to drop it, i guarantee you will, at a minimum, break replication, the SQL Agent, scheduled jobs,let alone lots...

I'm afraid the answer is "it depends"...we'd need to really see the procedure to give you a peer review and tell you what we thing is good, bad, or could...

you need to replace vbCrLf with the html break tag <br /> & vbCrLf, whether in the data source at SQL, or in the textbox/panel you are loading the data...

ok one imporvement i see is some out of date statistics on the Table CorrespondenceLog;

the estimated plan expecting 4 rows, but the actual ended up using almost 12 million.

can you...

great greg...can you post an Actual execution plan? that's where a few more details will help as well

ok i see what you are saying...you have a slow query, and at least a portion of the slowness is probably attributable to the grabbing lots of rows with ...

SQL Server indexes are constrained to a maximum width of 900 bytes; so you could include *part* of that text column, potentially;

typically when you have to search a text/varchar(max) column,...

i wouldn't say bad practice; you'd have to review the logic to determine if the data REALLY needs to go into a temp table (like it's being further processed or...