Using date ranges on a composite key degrades performance

2004-06-22 Thread David Perron
Im finding that when I execute a query joining to a large fact table (~450 million rows) using a composite key of INT(11) DATE for a single Date i.e. AND dimension.id = factable.id AND factable.Date = '2004-06-22' the query returns exceptionally fast. However, when I change this to a range,

Re: Using date ranges on a composite key degrades performance

2004-06-22 Thread SGreen
: Fax to: 06/22/2004 02:46 Subject: Using date ranges on a composite key degrades performance PM

RE: Using date ranges on a composite key degrades performance

2004-06-22 Thread David Perron
' -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 3:16 PM To: David Perron Cc: [EMAIL PROTECTED] Subject: Re: Using date ranges on a composite key degrades performance Are you using the JOIN ... ON... syntax or the comma syntax of joining

RE: Using date ranges on a composite key degrades performance

2004-06-22 Thread SGreen
to: 06/22/2004 03:38 Subject: RE: Using date ranges on a composite key degrades performance PM