InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 10:27:35 GMT20http://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspx[quote][b]anthony.green (1/17/2013)[/b][hr][quote][b]Ed Wagner (1/17/2013)[/b][hr]If your field is a datetime data type, then you're comparing the datetime result of GetDate() against the datetime value of the field. So, nothing's going to match. I like the BETWEEN or <= and >= approach as well. That was you can avoid putting date parsing functions on the field (i.e.: to the left of the = sign) which would be a disaster for performance.Effectively, you want use date functions that evaluate to something like this:[code="sql"]WHERE Invoice_Date BETWEEN '01/01/2013 00:00:00.000' AND '01/01/2013 23:59:59.999'[/code][/quote]That will equate to BETWEEN 01/01/2013 and 02/01/2013 due to the rounding of datetime.You would want 01/01/2013 00:00:00.000 AND 01/01/2013 23:59:59.997 instead, unless your using datetime2But always try to remember to qualify your dates as ISO formats so that SQL doesnt get confused or set the dateformat to the correct formatYYYY-MM-DDTHH:MM:SS.msTake 02/01/2013 is it 2nd Jan 2013 or 1st Feb 2013, depending who you ask you will get a different answer, where as if it follows an ISO standard there cannot be any confusion[url]http://en.wikipedia.org/wiki/ISO_8601[/url][/quote]It would be even better to specify start and end dates using the "half-open interval" model, like this: WHERE DatetimeColumn >= '2013-01-01 00:00:00.000' AND DatetimeColumn < '2013-01-02 00:00:00.000'This will return all values with a date component of 2013-01-01 with none of the ambiguity that can result from rounding the time component when evaluating the BETWEEN condition.It's called a "half-open interval" because the "start" datetime is included in the range but the "end" datetime is not.Fri, 18 Jan 2013 09:29:51 GMTwolfkilljhttp://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspx[quote][b]ziako (1/17/2013)[/b][hr]Thanks Anthony Green. That worked fine.[/quote]No problem, glad I could assist.May I suggest some further reading [url]http://www.sqlservercentral.com/blogs/lynnpettis/2009/03/25/some-common-date-routines/[/url]They may help you out with other date related issues you may run into.Thu, 17 Jan 2013 07:15:46 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspxThanks Anthony Green. That worked fine.Thu, 17 Jan 2013 07:13:56 GMTdbmanhttp://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspx[quote][b]Ed Wagner (1/17/2013)[/b][hr]If your field is a datetime data type, then you're comparing the datetime result of GetDate() against the datetime value of the field. So, nothing's going to match. I like the BETWEEN or <= and >= approach as well. That was you can avoid putting date parsing functions on the field (i.e.: to the left of the = sign) which would be a disaster for performance.Effectively, you want use date functions that evaluate to something like this:[code="sql"]WHERE Invoice_Date BETWEEN '01/01/2013 00:00:00.000' AND '01/01/2013 23:59:59.999'[/code][/quote]That will equate to BETWEEN 01/01/2013 and 02/01/2013 due to the rounding of datetime.You would want 01/01/2013 00:00:00.000 AND 01/01/2013 23:59:59.997 instead, unless your using datetime2But always try to remember to qualify your dates as ISO formats so that SQL doesnt get confused or set the dateformat to the correct formatYYYY-MM-DDTHH:MM:SS.msTake 02/01/2013 is it 2nd Jan 2013 or 1st Feb 2013, depending who you ask you will get a different answer, where as if it follows an ISO standard there cannot be any confusion[url]http://en.wikipedia.org/wiki/ISO_8601[/url]Thu, 17 Jan 2013 07:08:34 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspxIf your field is a datetime data type, then you're comparing the datetime result of GetDate() against the datetime value of the field. So, nothing's going to match. I like the BETWEEN or <= and >= approach as well. That was you can avoid putting date parsing functions on the field (i.e.: to the left of the = sign) which would be a disaster for performance.Effectively, you want use date functions that evaluate to something like this:[code="sql"]WHERE Invoice_Date BETWEEN '01/01/2013 00:00:00.000' AND '01/01/2013 23:59:59.999'[/code]Thu, 17 Jan 2013 07:03:03 GMTEd Wagnerhttp://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspxThats becuase you probably wont have anything that is equal to the date being used in the where clauseYou really need to do an >= < where clauseSELECT [Invoice_Date],[UserId],[Customer],[InvoiceNo],[Description],[Pack],[PIP_Code],[Class],[Major_Grp],[Invoice_Val],[Cost_Pr],[Quantity]FROM [Telesales].[dbo].[Sales]Where Invoice_Date >= dateadd(dd, datediff(dd, 0, GETDATE()) - 1, 0)AND Invoice_Date < dateadd(dd, datediff(dd, 0, GETDATE()), 0)Remember that dates are forever moving valuesNo two runs of the query are the same when using = and getdate() as the time stamp will change on each run.Thu, 17 Jan 2013 04:47:18 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspxit's not work properly............Thu, 17 Jan 2013 04:42:01 GMTalpeshchauhanhttp://www.sqlservercentral.com/Forums/Topic1408326-391-1.aspxHello,I am trying to create a query to get the results for yesterdays data only. So basically i need all the sales for yesterdays invoices date. I am running the query and getting zero results. The SQL i am using is below. Does anyone know if i am doing this wrong?SELECT [Invoice_Date] ,[UserId] ,[Customer] ,[InvoiceNo] ,[Description] ,[Pack] ,[PIP_Code] ,[Class] ,[Major_Grp] ,[Invoice_Val] ,[Cost_Pr] ,[Quantity] FROM [Telesales].[dbo].[Sales] Where DATEADD(d,-1,GETDATE()) = Invoice_Date Also tried:SELECT [Invoice_Date] ,[UserId] ,[Customer] ,[InvoiceNo] ,[Description] ,[Pack] ,[PIP_Code] ,[Class] ,[Major_Grp] ,[Invoice_Val] ,[Cost_Pr] ,[Quantity] FROM [Telesales].[dbo].[Sales] Where Invoice_Date = (GETDATE() - 1)Thu, 17 Jan 2013 04:40:21 GMTdbman