Prev: DST time change and SQL agent jobs
Next: SQL Server maxes out at 100% CPU!
From: dg on 15 Mar 2010 15:02
Yes,, we tried this, but to no avail...

"Dan Guzman" wrote:

> > In addition to
> > the query above, we have tried locating rows with invalid columns in them
> > with a where clause referencing other (valid) fields (and values) in the
> > row.
> > No luck.
>
> Are you able to return a problem row using *only* valid columns and values
> in the query?
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
> http://weblogs.sqlteam.com/dang/
>
>
>
From: Dan Guzman on 15 Mar 2010 20:49
> Yes,, we tried this, but to no avail...

So the SELECT statement includes no references to the problem data (only
good data in the SELECT and WHERE clause)? Does the query plan use an index
with a key on the problem columns? I would expect that the select would
return rows as long as invalid values are entirely avoided.

--
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"dg" <dg(a)discussions.microsoft.com> wrote in message
news:534AE905-339A-4A82-A470-EF7BCAD8D02F(a)microsoft.com...
> Yes,, we tried this, but to no avail...
>
> "Dan Guzman" wrote:
>
>> > In addition to
>> > the query above, we have tried locating rows with invalid columns in
>> > them
>> > with a where clause referencing other (valid) fields (and values) in
>> > the
>> > row.
>> > No luck.
>>
>> Are you able to return a problem row using *only* valid columns and
>> values
>> in the query?
>>
>> --
>> Hope this helps.
>>
>> Dan Guzman
>> SQL Server MVP
>> http://weblogs.sqlteam.com/dang/
>>
>>
>>
 | 
Pages: 1
Prev: DST time change and SQL agent jobs
Next: SQL Server maxes out at 100% CPU!