Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Query help Expand / Collapse
Author
Message
Posted Wednesday, April 3, 2013 8:15 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, August 17, 2014 3:50 AM
Points: 329, Visits: 858
I have a table as below. It has list of tasks with its start date and end date. When a user try to enter a new task with start date and end date, it has to check with existing task's start date and end date and report which start date or end date will the new task's start date and end date will conflict. A new task entry can’t start before or after or in between those dates. Basically query should pull all the row(s) that conflict with the given start and end date….If none, output will be empty.

Create Table MyTaskList
TaskName VARCHAR(50),
StartDate DATETIME,
EndDate DATETIME
);

INSERT INTO MyTaskList (TaskName, StartDate,EndDate)
VALUES('Task A','03/05/2012','03/08/2012');

INSERT INTO MyTaskList (TaskName, StartDate,EndDate)
VALUES('Task B','03/09/2012','03/12/2012');


INSERT INTO MyTaskList (TaskName, StartDate,EndDate)
VALUES('Task C','03/13/2012','03/15/2012');


Post #1438634
Posted Thursday, April 4, 2013 3:18 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 8:49 AM
Points: 2,434, Visits: 7,506
Difficult to know what you want to do because you haven't included expected output for any data.

What is you expected output with the following: -
DECLARE @NewTask VARCHAR(50), @StartDate DATETIME, @EndDate DATETIME;
SET @NewTask = 'TASK D';
SET @StartDate = '2012-03-04';
SET @EndDate = '2012-03-05';

DECLARE @NewTask VARCHAR(50), @StartDate DATETIME, @EndDate DATETIME;
SET @NewTask = 'TASK D';
SET @StartDate = '2012-03-14';
SET @EndDate = '2012-03-17';

Here's a shot in the dark: -
DECLARE @NewTask VARCHAR(50), @StartDate DATETIME, @EndDate DATETIME;
SET @NewTask = 'TASK D';
SET @StartDate = '2012-03-14';
SET @EndDate = '2012-03-17';

IF EXISTS (SELECT 1 FROM MyTaskList WHERE @StartDate >= StartDate AND @StartDate <= EndDate)
BEGIN
PRINT 'StartDate No Good';
END
ELSE IF EXISTS (SELECT 1 FROM MyTaskList WHERE @EndDate >= StartDate AND @EndDate <= EndDate)
BEGIN
PRINT 'EndDate No Good';
END
ELSE BEGIN
INSERT INTO MyTaskList (TaskName, StartDate,EndDate)
SELECT @NewTask, @StartDate, @EndDate;
END




Not a DBA, just trying to learn

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better, quicker answers on SQL Server performance related questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/



If you litter your database queries with nolock query hints, are you aware of the side effects?
Try reading a few of these links...

(*) Missing rows with nolock
(*) Allocation order scans with nolock
(*) Consistency issues with nolock
(*) Transient Corruption Errors in SQL Server error log caused by nolock
(*) Dirty reads, read errors, reading rows twice and missing rows with nolock


LinkedIn | Blog coming soon (for sufficiently large values of "soon" )!
Post #1438695
Posted Thursday, April 4, 2013 4:31 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, August 17, 2014 3:50 AM
Points: 329, Visits: 858
Sorry, output should be something like select from mytasklist where conflict dates exist. If no conflict dates exist, should be nothing.
Post #1438710
Posted Thursday, April 4, 2013 5:08 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 8:20 AM
Points: 23,270, Visits: 31,987
SQL_Surfer (4/4/2013)
Sorry, output should be something like select from mytasklist where conflict dates exist. If no conflict dates exist, should be nothing.


This doesn't help me. Using the limited sample data provided show us examples of both.



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 #1438717
Posted Thursday, April 4, 2013 6:09 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, August 17, 2014 3:50 AM
Points: 329, Visits: 858
Let me see if this helps. Select list of conflicted dates from the table with the new startdate or enddate or both. I am thinking of putting each condition in union but I could be thinking wrong.
Post #1438741
Posted Thursday, April 4, 2013 6:12 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, August 17, 2014 3:50 AM
Points: 329, Visits: 858
In other words, user needs to see list of conflicted dates so that he knows which new dates to put in.
Post #1438744
Posted Thursday, April 4, 2013 6:46 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 8:49 AM
Points: 2,434, Visits: 7,506
I note that you still haven't scripted out your expected outcome based on sample data. Unfortunately, this means I'm unable to provide any more assistance.

Good luck getting everything working.



Not a DBA, just trying to learn

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better, quicker answers on SQL Server performance related questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/



If you litter your database queries with nolock query hints, are you aware of the side effects?
Try reading a few of these links...

(*) Missing rows with nolock
(*) Allocation order scans with nolock
(*) Consistency issues with nolock
(*) Transient Corruption Errors in SQL Server error log caused by nolock
(*) Dirty reads, read errors, reading rows twice and missing rows with nolock


LinkedIn | Blog coming soon (for sufficiently large values of "soon" )!
Post #1438757
Posted Thursday, April 4, 2013 6:51 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 8:20 AM
Points: 23,270, Visits: 31,987
SQL_Surfer (4/4/2013)
In other words, user needs to see list of conflicted dates so that he knows which new dates to put in.



Words, all I see are words. We need to see True examples, using the bare sample data provided if (some data) is passed into (some code, not expecting this part) the expected result based on the input and the sample data provide is (what).




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 #1438759
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse