Getting datepart to work for query

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » T-SQL (SS2K5) » Getting datepart to work for query

Getting datepart to work for query

Rate Topic

Display Mode

Topic Options

Author

Message

shree dhavale

Posted Saturday, June 27, 2009 1:50 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Saturday, February 02, 2013 7:00 PM
Points: 147, Visits: 37

Hi,
I have a report where I need to see all current activity in a mfg shop from 4:30 am of yesterday to 4:29 am of today. I cant seem get the datepart to work for my time part of the date. Could someone please help me with the syntax for -
Where startdate >= yesterday 4:30 am and startdate <=today 4:29 am
There is also a report I need to generate for Monday 4:30a.m to Saturday 4:30 am every week.
Thanks for all the help in advance!
Shree

Post #743164

bitbucket-25253

Posted Saturday, June 27, 2009 3:14 PM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 6:41 AM
Points: 5,103, Visits: 20,210

shree dhavale

It would help those who will be attempting to help you if you provided the table structure, sample data and the T-SQL statement that you have attempted to utilize. All this per the article whose link is in my signature block.

If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read
Before posting a performance problem please read

Post #743176

Jeffrey Williams 3188

Posted Saturday, June 27, 2009 7:45 PM

SSCarpal Tunnel

Group: General Forum Members
Last Login: Friday, May 17, 2013 11:21 AM
Points: 4,317, Visits: 9,216

Here are a few things for you to look at:

Select dateadd(minute, 990, dateadd(day, datediff(day, 0, getdate()), 0))
,dateadd(minute, 990, dateadd(day, datediff(day, 0, getdate()) - 1, 0))

Now, with the above you could do something like:

Select {columns}
From YourTable
Where YourDate >= dateadd(minute, 990, dateadd(day, datediff(day, 0, getdate()), 0))
And YourDate < dateadd(minute, 990, dateadd(day, datediff(day, 0, getdate()) - 1, 0))

Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

Post #743197

Michael Valentine Jones

Posted Saturday, June 27, 2009 10:53 PM

SSCrazy

Group: General Forum Members
Last Login: Yesterday @ 6:26 PM
Points: 2,945, Visits: 10,514

select
        *
from
        MyTable
where
        -- Greater than or equal to yesterday at 04:30
        MyDate >= dateadd(day,datediff(day,0,getdate())-1,'04:30')	and
        -- Less than today at 04:30
        MyDate <  dateadd(day,datediff(day,0,getdate())  ,'04:30')

Post #743215

shree dhavale

Posted Sunday, June 28, 2009 10:45 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Saturday, February 02, 2013 7:00 PM
Points: 147, Visits: 37

Thanks so much for helping out. I will use the syntax posted in the solution.
Here is the part that I had needed help with in my where clause...
(where (timesheet.wcstart between @start_date and @end_date and timesheet.wcfinish is null))

INSERT INTO #timesheet

SELECT emp.firstname + ' ' + emp.surname, mo.monumber, inv.customer_part_num, inv.description, t.opno, routing.description,workcenter.name,
Case When timesheet.wcstart < @start_date then @start_date
Else timesheet.wcstart
End,
timesheet.wcfinish,
ISNULL(workcenter.machine,'X'),
'',
TSNo
FROM mfg_timesheet t
Left outer join cubs..mfg_mo_routing routing On
routing.companyid = timesheet.companyid and
routing.mo_key = timesheet.mo_key and
routing.opno = timesheet.opno
Left outer join cubs..mfg_workcenter workcenter On
workcenter.wcno = timesheet.wcno and
workcenter.companyid = timesheet.companyid,
mfg_mo mo, inv_item inv,mfg_employee emp,slsord sls

where (timesheet.wcstart between @start_date and @end_date and timesheet.wcfinish is null) and
mo.mo_key = timesheet.mo_key and
emp.employeeid = timesheet.employeeid and
mo.companyid = inv.company_id and
mo.stocknumber = inv.stock_number and
timesheet.companyid = 1 and
workcenter.machine IN ('W') And
TSNo NOT IN (SELECT TsNo FROM mfg_timesheetAdj) and
sls.company_id = mo.companyid and
sls.slsord_number = mo.slsord_number

Post #743348

Mark Eytcheson

Posted Monday, June 29, 2009 1:22 PM

Old Hand

Group: General Forum Members
Last Login: Thursday, January 19, 2012 3:33 PM
Points: 377, Visits: 8,621

I usually create two datasets:
1. StartDate
SELECT CAST((CONVERT(varchar(10), GETDATE()-9, 101)) AS DATETIME) AS StartDate

2. EndDate
SELECT CAST((CONVERT(varchar(10), GETDATE()-2, 101) + ' 23:59:59') AS DATETIME) AS EndDate

Then set the parameters @StartDate and @EndDate equal to the values of these two datasets.

Post #743908

Lynn Pettis

Posted Monday, June 29, 2009 1:26 PM

SSC-Insane

Group: General Forum Members
Last Login: Today @ 7:20 AM
Points: 21,625, Visits: 27,469

Mark Eytcheson (6/29/2009)

SELECT CAST((CONVERT(varchar(10), GETDATE()-2, 101) + ' 23:59:59') AS DATETIME) AS EndDate --> This will miss any records with a datetime value > [Date] 23:59:59.000 and [Date + 1] 00:00:00.000.

Cool

Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)

Post #743910

Michael Valentine Jones

Posted Monday, June 29, 2009 9:23 PM

SSCrazy

Group: General Forum Members
Last Login: Yesterday @ 6:26 PM
Points: 2,945, Visits: 10,514

Queries for a date range should normally be in this form:

where MyDatetimeColumn >= @StartDatetime  and MyDatetimeColumn < @EndDatetime

In other words greater than or equal to the first point in time that we know that we want, and less than the first point in time that we don't want.

There is never any guarantee that the precision of time intervals will stay the same in future releases, so it is unrealistic to code end time as "2009-06-29 23:59:59.997", even if this is the last possible moment that we want to select with the current version of SQL Server. Just code it as less than '2009-06-30'.

Post #744135

« Prev Topic | Next Topic »

Permissions