"Pete Gajria" <pete.gajria@clarksecurity.com> wrote in message
news:oprv4np1fxajys4f@news.microsoft.com...
> Hi,
> looks like sql server 2000 (no sp) can't distinguish between
> 2 rows with timestamps less than 3ms apart
> in other words if you query a bunch of rows with a date > expression in
the
> where
> clause in a select statement it will actually drop rows
>
> heres an example
>
>
> select top 5 id, modified_date
> from test
> where modified_date is not null
> order by modified_date ASC
>
> 250136 2003-04-08 11:50:40.390
> 572016 2003-04-08 11:51:05.357
> 801365 2003-04-08 11:51:07.467
> 800755 2003-04-08 11:51:15.763
> 801159 2003-04-08 11:51:16.437
>
> now with the where clause
>
> select top 5 id, modified_date
> from test
> where modified_date > '2003-04-08 11:51:05.355' <-- 2 ms less than .357
> order by modified_date ASC
>
> 801365 2003-04-08 11:51:07.467
> 800755 2003-04-08 11:51:15.763
> 801159 2003-04-08 11:51:16.437
> 131901 2003-04-08 11:51:17.153
>
> & it dropped the first row with 357ms which should have been included.
>
> is there any workaround for this ?
>
> ive never seen a database do this & im amazed it could slip pass qc.
>
> regards,
> pete
>
>

> looks like sql server 2000 (no sp) can't distinguish between
> 2 rows with timestamps less than 3ms apart
>

wrote:

> Pete,
> Fully documented and has ALWAYS been the case with SQL Server.
>
>> looks like sql server 2000 (no sp) can't distinguish between
>> 2 rows with timestamps less than 3ms apart
>>
>
> Neil Pike MVP/MCSE. Protech Computing Ltd
> Reply here - no email
> SQL FAQ (484 entries) see
> http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
> (faqxxx.zip in lib 7)
> or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> or www.sqlserverfaq.com
> or www.mssqlserver.com/faq
>
>

"Pete Gajria" <pete.gajria@clarksecurity.com> wrote in message
news:oprwbq9ix5ajys4f@news.microsoft.com...
> Hi Neil,
> Thanks for the followup
> Now is there any workaround to this issue ?
>
> Regards,
> Pete
>
>
> On Sun, 28 Sep 2003 18:25:22 +0100, Neil Pike <neilpike@compuserve.com>
> wrote:
>
> > Pete,
> > Fully documented and has ALWAYS been the case with SQL Server.
> >
> >> looks like sql server 2000 (no sp) can't distinguish between
> >> 2 rows with timestamps less than 3ms apart
> >>
> >
> > Neil Pike MVP/MCSE. Protech Computing Ltd
> > Reply here - no email
> > SQL FAQ (484 entries) see
> > http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
> > (faqxxx.zip in lib 7)
> > or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> > or www.sqlserverfaq.com
> > or www.mssqlserver.com/faq
> >
> >
>
>
>
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

"Pete Gajria" <pete.gajria@clarksecurity.com> wrote in message
news:oprwbq9ix5ajys4f@news.microsoft.com...
> Hi Neil,
> Thanks for the followup
> Now is there any workaround to this issue ?
>
> Regards,
> Pete
>
>
> On Sun, 28 Sep 2003 18:25:22 +0100, Neil Pike <neilpike@compuserve.com>
> wrote:
>
> > Pete,
> > Fully documented and has ALWAYS been the case with SQL Server.
> >
> >> looks like sql server 2000 (no sp) can't distinguish between
> >> 2 rows with timestamps less than 3ms apart
> >>
> >
> > Neil Pike MVP/MCSE. Protech Computing Ltd
> > Reply here - no email
> > SQL FAQ (484 entries) see
> > http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
> > (faqxxx.zip in lib 7)
> > or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> > or www.sqlserverfaq.com
> > or www.mssqlserver.com/faq
> >
> >
>
>
>
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

> Now is there any workaround to this issue ?