Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread SQL problem
Wed, Jan 25 2006 9:10 AMPermanent Link

Hi;
Stats D7
v4.22b7
[LastMod ]field is a TimeStamp type
Below is the plan.
Problem : I should not get any data because the value of LastMod is the same
as the condition to the right of the "Where". I'm getting the complete
dataset retuened
Any insights
TIA
Allan


SELECT * from MeditechData WHERE [LastMod] > '2006-01-25 9:44:27 AM'

Tables Involved
---------------

MeditechData (MeditechData) table opened shared, has 6148 rows

Result Set Generation
---------------------

Result set will be live

Result set will consist of one or more rows

Result set will be ordered by the primary index for the table MeditechData

WHERE Clause Execution
----------------------

The expression:

[LastMod] > '2006-01-25 9:44:27 AM'

is UN-OPTIMIZED, covers 6148 rows or index keys, costs 5213504 bytes, and
will
be applied to the MeditechData table (MeditechData) before any joins

============================================================================
====
>>>>> 6148 rows affected in 0.02 seconds
============================================================================
====

Wed, Jan 25 2006 10:30 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

brock


I suppose it could be down to milliseconds. Try

SELECT * from MeditechData WHERE [LastMod] > '2006-01-25 9:44:27.999 AM'

and see what happens.

Roy Lambert
Wed, Jan 25 2006 10:38 AMPermanent Link

Roy;

That's the ticket!!

Thanks buddy!

Allan
"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:E394E8FE-9873-4C84-AAF2-4F5EA1F89EE1@news.elevatesoft.com...
> brock
>
>
> I suppose it could be down to milliseconds. Try
>
> SELECT * from MeditechData WHERE [LastMod] > '2006-01-25 9:44:27.999 AM'
>
> and see what happens.
>
> Roy Lambert
>

Image