Thanks Andrew, I think I'm goint to pull the little hair I have left -- out.
The thing that so interesting is that when I run the stored procedure from
QA(from the hosting server or my workstation) it run within 1 sec but when
it's executed from ASP it times-out?
This is a good one ...
"Andrew J. Kelly" <sqlmvpnooospamshadhawk.com> wrote in message
news:e7f5chKRDHA.2096TK2MSFTNGP12.phx.gbl...use> I suspect this is due to the fact the WHERE clause is highly unlikely toNULL> an index and will most likely scan the table. If that is the case a table
> or page level lock is more efficient. IS NULL is not always usable in an
> index seek especially where there are usually many rows that are null.
> Andrew J. Kelly
> SQL Server MVP
> "TJ" <nospamnowhere.com> wrote in message
> news:e7jNLwJRDHA.2224TK2MSFTNGP12.phx.gbl...> > Hey guys, I've been having performance problems and I'm going to through
> > Microsoft's Kb articles but I was wondering if what I'm seeing is a
> > "Tell-tell" sign of something obvious.
> > I've noticing that many of the queries that "time-out" seem to run to
> > completion when I add the rowlock hint to the select like ...
> > SELECT DISTINCT CDR.EXTENSION FROM CDR WITH (ROWLOCK)
> > WHERE LastEditTimeStamp IS NULL and PostTimeStamp is NULL AND PID IS>> >
> > Does this point to anything obvious to anyone?
> > --
> > Any and all contributions are greatly appreciated ...
> > Regards TJ