i noticed in the example you pasted, and also in the web page example, it is using extended ascii characters for the quotes (left dbl quote and right dbl quote)...

you might want to paste your procedure here; some of us can point out any spots where the procedure might be able to be optimized. I think you glazed over...

sql_er no it does not address the issue where a tablename might span across  the 4000 char mark in syscomments;

in my case, i check sysdepends and this, and it's "good...

try SELECT name, age FROM users WHERE ISNULL(age,0) = ISNULL(@age, 0)

if it's taking 1.5 hours to complete, i bet it's got a row by row cursor on a big table, and whatever it is doing might be optimized into one...

Stephen's right...you could use a case statement to avoid the < 20 pitfall:

CASE WHEN len(Incident_Details.Description) < 20 then '' ELSE

substring(Incident_Details.Description, 20, len(Incident_Details.Description) -19) END AS...

peter I'm having a similar issue when i try to do it as well in my 2005 test server.

I never created my info views based on other views, so in...

it's the alias for the count....we still need the schema and datasample to give a meaningful answer.

SELECT USER,

CASE WHEN ISNULL(APPLICATION1,0)=0 THEN 0 ELSE 1 END  +

CASE WHEN ISNULL(APPLICATION2,0)=0 THEN...

thanks for the correction Vladan; i missed that one since i just winged it and didn't test it in QA. Maybe he can redesign the schema and fix the issue.

really difficult without the schema of the tables...can we assume that the table CitrixApps, with only a single column, is source for the values in the Working table's Application1/2/3... columns?

if...

that's not true; I've created lots of information_schema views in sql 2000;

like Peter outlined, you simply create a view in master and change the owner to INFORMATION_SCHEMA; I've done...

as I understand it, SQL Lite speed uses the updated SQL Server API's to create a standard SQL Server backup, abiet much faster, because the TSQL/Enterprise Manager backup commands use...

what is the defined size of the tempdb? tempdb gets recreated every time you stop and start the server, so if you stoip and start, and it is still 5...

there's no event you can use, but you can check to see if soemthing has been backedup since a certain date, and do your special process from there (i assume...

you didn't explain what you meant by "slowness"... I still suspect the autoclose issue;

you can run this statement to see if anything is set to autoclose=true or not:

SELECT + [name]...