Corrupted table or bug or..?

SQL 7.0
In QA, if I execute the following:
SELECT name FROM maindata WHERE ddate = '20041011'
..the name 'vpipx' does NOT show up.
However, if I execute:
SELECT * FROM maindata WHERE name = 'vpipx' and ddate
= '20041011'
..the name 'vpipx' DOES show up.
This is on one server only. Two other servers don't
exhibit this. I'm trying to figure out if there is
something corrupted in this particular table or where the
problem is, or if it could happen to my other tables, or
if it's happening in my other tables right now, and i'm
not aware of it.
To see if 'vpipx' is showing up as a result: After I
execute the query, I then do Edit/Find for 'vpipx' and it
turns up "not found". I've also cut and pasted the
results into NotePad and searched for 'vpipx', and it
wasn't found.
I've checked the execution plans of the two queries and
see nothing unusual. There is only one index.
Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86) May 29
2003 15:21:25
Copyright (c) 1988-2002 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service
Pack 4)
(1 row(s) affected)
CREATE TABLE [dbo].[MAINDATA] (
[Name] [varchar] (32) NOT NULL ,
[DDate] [smalldatetime] NOT NULL ,
[DO] [decimal](18, 6) NOT NULL ,
[DH] [decimal](18, 6) NOT NULL ,
[DL] [decimal](18, 6) NOT NULL ,
[DC] [decimal](18, 6) NOT NULL ,
[DV] [int] NOT NULL ,
[DOI] [int] NOT NULL
) ON [PRIMARY]
GO
CREATE UNIQUE CLUSTERED INDEX [SDate] ON [dbo].
[MAINDATA]([Name], [DDate]) WITH FILLFACTOR = 90 ON
[PRIMARY]
GO
DBCC CHECKDB turns up no errors.
There are 98 million records.
Any help appreciated.
Thx,
DonHow many records are you getting back normally?
QA has a size limit on it, so all of the rows may not be showing up.
Try the query from another application and see what it does. I would pipe
in the query to osql and pipe the results out to a text file.
osql /E /iC:\input.sql /oC:\Output.txt
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Don D" <anonymous@.discussions.microsoft.com> wrote in message
news:05fe01c4b6c0$569d9340$a401280a@.phx.gbl...
> SQL 7.0
> In QA, if I execute the following:
> SELECT name FROM maindata WHERE ddate = '20041011'
> ..the name 'vpipx' does NOT show up.
> However, if I execute:
> SELECT * FROM maindata WHERE name = 'vpipx' and ddate
> = '20041011'
> ..the name 'vpipx' DOES show up.
> This is on one server only. Two other servers don't
> exhibit this. I'm trying to figure out if there is
> something corrupted in this particular table or where the
> problem is, or if it could happen to my other tables, or
> if it's happening in my other tables right now, and i'm
> not aware of it.
> To see if 'vpipx' is showing up as a result: After I
> execute the query, I then do Edit/Find for 'vpipx' and it
> turns up "not found". I've also cut and pasted the
> results into NotePad and searched for 'vpipx', and it
> wasn't found.
> I've checked the execution plans of the two queries and
> see nothing unusual. There is only one index.
>
> Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86) May 29
> 2003 15:21:25
> Copyright (c) 1988-2002 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service
> Pack 4)
> (1 row(s) affected)
> CREATE TABLE [dbo].[MAINDATA] (
> [Name] [varchar] (32) NOT NULL ,
> [DDate] [smalldatetime] NOT NULL ,
> [DO] [decimal](18, 6) NOT NULL ,
> [DH] [decimal](18, 6) NOT NULL ,
> [DL] [decimal](18, 6) NOT NULL ,
> [DC] [decimal](18, 6) NOT NULL ,
> [DV] [int] NOT NULL ,
> [DOI] [int] NOT NULL
> ) ON [PRIMARY]
> GO
> CREATE UNIQUE CLUSTERED INDEX [SDate] ON [dbo].
> [MAINDATA]([Name], [DDate]) WITH FILLFACTOR = 90 ON
> [PRIMARY]
> GO
>
> DBCC CHECKDB turns up no errors.
> There are 98 million records.
> Any help appreciated.
> Thx,
> Don
>|||Ok, the OSQL query method worked.
There were approx 75,000 rows returned by the query.
Does this OSQL test suggest that all is OK internally?
That the reason it's not showing up in the QA query is
because of the size limit?
thx,
Don
>--Original Message--
>How many records are you getting back normally?
>QA has a size limit on it, so all of the rows may not be
showing up.
>Try the query from another application and see what it
does. I would pipe
>in the query to osql and pipe the results out to a text
file.
>osql /E /iC:\input.sql /oC:\Output.txt
>
>HTH
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Don D" <anonymous@.discussions.microsoft.com> wrote in
message
>news:05fe01c4b6c0$569d9340$a401280a@.phx.gbl...
>> SQL 7.0
>> In QA, if I execute the following:
>> SELECT name FROM maindata WHERE ddate = '20041011'
>> ..the name 'vpipx' does NOT show up.
>> However, if I execute:
>> SELECT * FROM maindata WHERE name = 'vpipx' and ddate
>> = '20041011'
>> ..the name 'vpipx' DOES show up.
>> This is on one server only. Two other servers don't
>> exhibit this. I'm trying to figure out if there is
>> something corrupted in this particular table or where
the
>> problem is, or if it could happen to my other tables,
or
>> if it's happening in my other tables right now, and i'm
>> not aware of it.
>> To see if 'vpipx' is showing up as a result: After I
>> execute the query, I then do Edit/Find for 'vpipx' and
it
>> turns up "not found". I've also cut and pasted the
>> results into NotePad and searched for 'vpipx', and it
>> wasn't found.
>> I've checked the execution plans of the two queries and
>> see nothing unusual. There is only one index.
>>
>> Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86) May
29
>> 2003 15:21:25
>> Copyright (c) 1988-2002 Microsoft Corporation
>> Standard Edition on Windows NT 5.0 (Build 2195: Service
>> Pack 4)
>> (1 row(s) affected)
>> CREATE TABLE [dbo].[MAINDATA] (
>> [Name] [varchar] (32) NOT NULL ,
>> [DDate] [smalldatetime] NOT NULL ,
>> [DO] [decimal](18, 6) NOT NULL ,
>> [DH] [decimal](18, 6) NOT NULL ,
>> [DL] [decimal](18, 6) NOT NULL ,
>> [DC] [decimal](18, 6) NOT NULL ,
>> [DV] [int] NOT NULL ,
>> [DOI] [int] NOT NULL
>> ) ON [PRIMARY]
>> GO
>> CREATE UNIQUE CLUSTERED INDEX [SDate] ON [dbo].
>> [MAINDATA]([Name], [DDate]) WITH FILLFACTOR = 90 ON
>> [PRIMARY]
>> GO
>>
>> DBCC CHECKDB turns up no errors.
>> There are 98 million records.
>> Any help appreciated.
>> Thx,
>> Don
>
>.
>|||That would be my guess. In QA, check the Tools->Options tab. You can make
modifications to the amount of data that is returned.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Don D" <anonymous@.discussions.microsoft.com> wrote in message
news:1aa001c4b6e0$92ab5cd0$a501280a@.phx.gbl...
> Ok, the OSQL query method worked.
> There were approx 75,000 rows returned by the query.
> Does this OSQL test suggest that all is OK internally?
> That the reason it's not showing up in the QA query is
> because of the size limit?
> thx,
> Don
> >--Original Message--
> >How many records are you getting back normally?
> >
> >QA has a size limit on it, so all of the rows may not be
> showing up.
> >
> >Try the query from another application and see what it
> does. I would pipe
> >in the query to osql and pipe the results out to a text
> file.
> >
> >osql /E /iC:\input.sql /oC:\Output.txt
> >
> >
> >HTH
> >
> >Rick Sawtell
> >MCT, MCSD, MCDBA
> >
> >
> >
> >
> >"Don D" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:05fe01c4b6c0$569d9340$a401280a@.phx.gbl...
> >> SQL 7.0
> >> In QA, if I execute the following:
> >>
> >> SELECT name FROM maindata WHERE ddate = '20041011'
> >>
> >> ..the name 'vpipx' does NOT show up.
> >>
> >> However, if I execute:
> >>
> >> SELECT * FROM maindata WHERE name = 'vpipx' and ddate
> >> = '20041011'
> >>
> >> ..the name 'vpipx' DOES show up.
> >>
> >> This is on one server only. Two other servers don't
> >> exhibit this. I'm trying to figure out if there is
> >> something corrupted in this particular table or where
> the
> >> problem is, or if it could happen to my other tables,
> or
> >> if it's happening in my other tables right now, and i'm
> >> not aware of it.
> >>
> >> To see if 'vpipx' is showing up as a result: After I
> >> execute the query, I then do Edit/Find for 'vpipx' and
> it
> >> turns up "not found". I've also cut and pasted the
> >> results into NotePad and searched for 'vpipx', and it
> >> wasn't found.
> >>
> >> I've checked the execution plans of the two queries and
> >> see nothing unusual. There is only one index.
> >>
> >>
> >> Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86) May
> 29
> >> 2003 15:21:25
> >> Copyright (c) 1988-2002 Microsoft Corporation
> >> Standard Edition on Windows NT 5.0 (Build 2195: Service
> >> Pack 4)
> >>
> >> (1 row(s) affected)
> >>
> >> CREATE TABLE [dbo].[MAINDATA] (
> >> [Name] [varchar] (32) NOT NULL ,
> >> [DDate] [smalldatetime] NOT NULL ,
> >> [DO] [decimal](18, 6) NOT NULL ,
> >> [DH] [decimal](18, 6) NOT NULL ,
> >> [DL] [decimal](18, 6) NOT NULL ,
> >> [DC] [decimal](18, 6) NOT NULL ,
> >> [DV] [int] NOT NULL ,
> >> [DOI] [int] NOT NULL
> >> ) ON [PRIMARY]
> >> GO
> >>
> >> CREATE UNIQUE CLUSTERED INDEX [SDate] ON [dbo].
> >> [MAINDATA]([Name], [DDate]) WITH FILLFACTOR = 90 ON
> >> [PRIMARY]
> >> GO
> >>
> >>
> >> DBCC CHECKDB turns up no errors.
> >>
> >> There are 98 million records.
> >>
> >> Any help appreciated.
> >>
> >> Thx,
> >> Don
> >>
> >
> >
> >.
> >|||Thanks for your help...greatly appreciated :-)
Don
>--Original Message--
>That would be my guess. In QA, check the Tools->Options
tab. You can make
>modifications to the amount of data that is returned.
>HTH
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>"Don D" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1aa001c4b6e0$92ab5cd0$a501280a@.phx.gbl...
>> Ok, the OSQL query method worked.
>> There were approx 75,000 rows returned by the query.
>> Does this OSQL test suggest that all is OK internally?
>> That the reason it's not showing up in the QA query is
>> because of the size limit?
>> thx,
>> Don
>> >--Original Message--
>> >How many records are you getting back normally?
>> >
>> >QA has a size limit on it, so all of the rows may not
be
>> showing up.
>> >
>> >Try the query from another application and see what it
>> does. I would pipe
>> >in the query to osql and pipe the results out to a
text
>> file.
>> >
>> >osql /E /iC:\input.sql /oC:\Output.txt
>> >
>> >
>> >HTH
>> >
>> >Rick Sawtell
>> >MCT, MCSD, MCDBA
>> >
>> >
>> >
>> >
>> >"Don D" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:05fe01c4b6c0$569d9340$a401280a@.phx.gbl...
>> >> SQL 7.0
>> >> In QA, if I execute the following:
>> >>
>> >> SELECT name FROM maindata WHERE ddate = '20041011'
>> >>
>> >> ..the name 'vpipx' does NOT show up.
>> >>
>> >> However, if I execute:
>> >>
>> >> SELECT * FROM maindata WHERE name = 'vpipx' and
ddate
>> >> = '20041011'
>> >>
>> >> ..the name 'vpipx' DOES show up.
>> >>
>> >> This is on one server only. Two other servers don't
>> >> exhibit this. I'm trying to figure out if there is
>> >> something corrupted in this particular table or
where
>> the
>> >> problem is, or if it could happen to my other
tables,
>> or
>> >> if it's happening in my other tables right now, and
i'm
>> >> not aware of it.
>> >>
>> >> To see if 'vpipx' is showing up as a result: After I
>> >> execute the query, I then do Edit/Find for 'vpipx'
and
>> it
>> >> turns up "not found". I've also cut and pasted the
>> >> results into NotePad and searched for 'vpipx', and
it
>> >> wasn't found.
>> >>
>> >> I've checked the execution plans of the two queries
and
>> >> see nothing unusual. There is only one index.
>> >>
>> >>
>> >> Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86)
May
>> 29
>> >> 2003 15:21:25
>> >> Copyright (c) 1988-2002 Microsoft Corporation
>> >> Standard Edition on Windows NT 5.0 (Build 2195:
Service
>> >> Pack 4)
>> >>
>> >> (1 row(s) affected)
>> >>
>> >> CREATE TABLE [dbo].[MAINDATA] (
>> >> [Name] [varchar] (32) NOT NULL ,
>> >> [DDate] [smalldatetime] NOT NULL ,
>> >> [DO] [decimal](18, 6) NOT NULL ,
>> >> [DH] [decimal](18, 6) NOT NULL ,
>> >> [DL] [decimal](18, 6) NOT NULL ,
>> >> [DC] [decimal](18, 6) NOT NULL ,
>> >> [DV] [int] NOT NULL ,
>> >> [DOI] [int] NOT NULL
>> >> ) ON [PRIMARY]
>> >> GO
>> >>
>> >> CREATE UNIQUE CLUSTERED INDEX [SDate] ON [dbo].
>> >> [MAINDATA]([Name], [DDate]) WITH FILLFACTOR = 90 ON
>> >> [PRIMARY]
>> >> GO
>> >>
>> >>
>> >> DBCC CHECKDB turns up no errors.
>> >>
>> >> There are 98 million records.
>> >>
>> >> Any help appreciated.
>> >>
>> >> Thx,
>> >> Don
>> >>
>> >
>> >
>> >.
>> >
>
>.
>