Important alert: (current site time 7/15/2013 8:06:04 PM EDT)
 

VB icon

Using Case Statements to Empower your Betweens

Email
Submitted on: 11/20/2001 7:07:06 AM
By: James Travis  
Level: Intermediate
User Rating: By 3 Users
Compatibility: SQL Server 7.0, SQL Server 6.5 and earlier
Views: 25191
author picture
(About the author)
 
     To demonstrate selection queries using Case statements to adjust bewtween clauses range based on situational needs.
 
code:
Can't Copy and Paste this?
Click here for a copy-and-paste friendly version of this code!
 
Terms of Agreement:   
By using this code, you agree to the following terms...   
  1. You may use this code in your own programs (and may compile it into a program and distribute it in compiled format for languages that allow it) freely and with no charge.
  2. You MAY NOT redistribute this code (for example to a web site) without written permission from the original author. Failure to do so is a violation of copyright laws.   
  3. You may link to this code from another website, but ONLY if it is not wrapped in a frame. 
  4. You will abide by any additional copyright restrictions which the author may have placed in the code or code's description.
				
--**************************************
-- Name: Using Case Statements to Empower your Betweens
-- Description:To demonstrate selection queries using Case statements to adjust bewtween clauses range based on situational needs.
-- By: James Travis
--
-- Assumes:The case statement is one of the greatest items in SQL as it will allow you to do conditional testing of variable objects and return the specific items a person needs with less user input. Many people use case statements in their stored procedures but many don't realize the potential they can gain from them inside queries to help manipulate the data. Here in this example I will use time reporting to control how specific data is reported on based on the current system time of the server. (Note: I add 2 milliseconds to the start time and subract 1 from the end time due to the fact SQL Server will pull the first second befor and after a given time anyway in a between statment. By adding 2 I ensure I start at .001 and subtracting 1 and end at .000 and get no overlap in my result set. But depending on the date you store this may not be needed in you situation.)
--
--This code is copyrighted and has-- limited warranties.Please see http://www.Planet-Source-Code.com/vb/scripts/ShowCode.asp?txtCodeId=365&lngWId=5--for details.--**************************************

SELECT * FROM tblNameGoesHere WHERE ([DateTimeFldGoesHere] BETWEEN 
DATEADD(ms,2,DATEADD(hh,-1,(CASE
	WHEN (DATEPART(mi, GETDATE()) BETWEEN 0 AND 14) THEN DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE())
	WHEN (DATEPART(mi, GETDATE()) BETWEEN 15 AND 29) THEN DATEADD(mi,15,DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE()))
	WHEN (DATEPART(mi, GETDATE()) BETWEEN 30 AND 44) THEN DATEADD(mi,30,DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE()))
	ELSE DATEADD(mi,45,DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE()))
END)))
AND
DATEADD(ms,-1,(CASE
	WHEN (DATEPART(mi, GETDATE()) BETWEEN 0 AND 14) THEN DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE())
	WHEN (DATEPART(mi, GETDATE()) BETWEEN 15 AND 29) THEN DATEADD(mi,15,DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE()))
	WHEN (DATEPART(mi, GETDATE()) BETWEEN 30 AND 44) THEN DATEADD(mi,30,DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE()))
	ELSE DATEADD(mi,45,DATEADD(mi,-DATEPART(mi,GETDATE()),GETDATE()))
END)))


Other 20 submission(s) by this author

 


Report Bad Submission
Use this form to tell us if this entry should be deleted (i.e contains no code, is a virus, etc.).
This submission should be removed because:

Your Vote

What do you think of this code (in the Intermediate category)?
(The code with your highest vote will win this month's coding contest!)
Excellent  Good  Average  Below Average  Poor (See voting log ...)
 

Other User Comments


 There are no comments on this submission.
 

Add Your Feedback
Your feedback will be posted below and an email sent to the author. Please remember that the author was kind enough to share this with you, so any criticisms must be stated politely, or they will be deleted. (For feedback not related to this particular code, please click here instead.)
 

To post feedback, first please login.