Re: on stored procedure
- From: "Mike" <lmpope@xxxxxxxxx>
- Date: Tue, 11 Oct 2005 00:18:36 +0200
CLAIM_ID is a giving number (CLAIM #) and the dates are stored in a strange
format: yyyymmdd.
"Adam Machanic" <amachanic@xxxxxxxxxxxxxxxxxxxxxxxxxxx> escribió en el
mensaje news:uajuINczFHA.720@xxxxxxxxxxxxxxxxxxxxxxx
> "Ana" <nospam@xxxxxxxxx> wrote in message
> news:%2373L2HczFHA.460@xxxxxxxxxxxxxxxxxxxxxxx
>>
>> ORDER BY dbo.CLAIMS.CLAIM_ID
>
> You're ordering by the CLAIM_ID; why would you expect this to influence
> the ordering of DATE_OF_CLAIM?
>
> Try:
>
> ORDRY BY dbo.CLAIMS.DATE_OF_CLAIM
>
> By the way, why are you casting the date? Doing so will ruin index
> utilization.
>
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
>
>
>
.
- References:
- Q: on stored procedure
- From: Ana
- Re: on stored procedure
- From: Adam Machanic
- Re: on stored procedure
- From: Ana
- Re: on stored procedure
- From: Adam Machanic
- Re: on stored procedure
- From: Ana
- Re: on stored procedure
- From: Adam Machanic
- Q: on stored procedure
- Prev by Date: DMX INSERT INTO and OleDB Question
- Next by Date: Re: DMX INSERT INTO and OleDB Question
- Previous by thread: Re: on stored procedure
- Next by thread: DMX INSERT INTO and OleDB Question
- Index(es):
Relevant Pages
|