Skip to main content

SQL - Calculate time difference in Minutes, Hours, Days, Weeks, Months, Years for Posts / Notification


In this post I will show you how you can easily calculate time difference between two dates in seconds, minutes, hours, days, and even weeks, months and years in SQL.

This functionality can be used in notifications, emails, blog post etc

The key of this calculation is in Modulo operator, %. It returns the remainder (NOT the result!) of one number divided by another!


CREATE FUNCTION [dbo].[FN_GetTimeDifference] (@FromDate DATETIME, @ToDate DATETIME)      
RETURNS NVARCHAR(50)  
AS       
BEGIN       

DECLARE @Result NVARCHAR(50)       

SELECT  @Result = CASE WHEN DATEDIFF(second, @FromDate, @ToDate) / 60 / 60 / 24 / 7 > 0 THEN CAST(DATEDIFF(second, @FromDate, @ToDate) / 60 / 60 / 24 / 7 AS NVARCHAR(50)) + ' weeks ago' 
   WHEN DATEDIFF(second, @FromDate, @ToDate) / 60 / 60 / 24 % 7 > 0 THEN CAST(DATEDIFF(second, @FromDate, @ToDate) / 60 / 60 / 24 % 7 AS NVARCHAR(50)) + ' days ago'
   WHEN DATEDIFF(second, @FromDate, @ToDate) / 60 / 60 % 24 > 0 THEN CAST(DATEDIFF(second, @FromDate, @ToDate) / 60 / 60 % 24  AS NVARCHAR(50)) + ' hrs ago'
   WHEN DATEDIFF(second, @FromDate, @ToDate) / 60 % 60 > 0 THEN CAST(DATEDIFF(second, @FromDate, @ToDate) / 60 % 60 AS NVARCHAR(50)) + ' min ago'
   WHEN DATEDIFF(second, @FromDate, @ToDate) % 60 > 0 THEN CAST(DATEDIFF(second, @FromDate, @ToDate) % 60 AS NVARCHAR(50)) + ' sec ago' 
   END 

 
  
RETURN  @Result     

END  



Following is the usage and the expected output of the above function. In most of the cases we need to use GETDATE() as @ToDate parameter.


-----------------------------------------------------------------------------
SELECT dbo.FN_GetTimeDifference('2017-05-01 11:58:00', '2017-05-01 11:58:08')  
8 sec ago 
-----------------------------------------------------------------------------
SELECT dbo.FN_GetTimeDifference('2017-05-01 11:30:00', '2017-05-01 11:58:08')  
28 min ago
-----------------------------------------------------------------------------
SELECT dbo.FN_GetTimeDifference('2017-05-01 02:58:00', '2017-05-01 11:58:08')  
9 hrs ago
-----------------------------------------------------------------------------
SELECT dbo.FN_GetTimeDifference('2017-04-30 11:58:00', '2017-05-01 11:58:08')  
1 days ago
-----------------------------------------------------------------------------
SELECT dbo.FN_GetTimeDifference('2017-04-15 11:58:00', '2017-05-01 11:58:08')  
2 weeks ago
-----------------------------------------------------------------------------




Comments

  1. There are plenty of other slots options if these don’t work out, but these are first rate and you get free chips every two 우리카지노 hours to keep playing in} if you want like|if you'd like}. However, players who want the complete on line casino experience are likely to|are inclined to} gamble with real money after a couple of of} free rounds. Also TuskCasino will offer Best choice of the Online Slot Machines in your entertainment. Slot games shall be on offer from the best on line casino games providers where possible within the Casino Market. This weblog aims to share some insights on on line casino games and varieties of|several sorts of|various kinds of} on-line on line casino games.

    ReplyDelete

Post a Comment

Popular posts from this blog

Call User-defined Function on Linked Server :SQL Server

If you try to invoke a user-defined function (UDF) through a linked server in SQL Server by using a "four-part naming" convention (server.database.dbo.Function), you may receive error message.  The reason is User-defined function calls inside a four-part linked server query are not supported in SQL Server. Thats why error message indicates that the syntax of a Transact-SQL statement is incorrect.  To work around this problem, use the Openquery function instead of the four-part naming convention. For example, instead of the following query Select * from Linked_Server.database.dbo.Function(10) run a query with the Openquery function: Select * from Openquery(Linked_Server,'select database.dbo.Function(10)') If the user-defined function takes variable or scalar parameters, you can use the sp_executesql stored procedure to avoid this behavior.  For example: exec Linked_Server.database.dbo.sp_executesql N'SELECT database.dbo.Function(@input)',N'@input...

Microsoft SQL Server 2005 Service Pack 3 for Windows 7 (64 bit)

You can download from here Microsoft SQL Server 2005 Service Pack 3 Overview Service Pack 3 for Microsoft SQL Server 2005 is now available. SQL Server 2005 service packs are cumulative, and this service pack upgrades all service levels of SQL Server 2005 to SP3. You can use these packages to upgrade any of the following SQL Server 2005 editions: Enterprise Enterprise Evaluation Developer Standard Workgroup Download Size: 326.0 MB http://www.microsoft.com/downloads/details.aspx?FamilyID=ae7387c3-348c-4faa-8ae5-949fdfbe59c4&displaylang=en Microsoft SQL Server Management Studio Express Service Pack 3 Overview Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical management tool for managing SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services. SSMSE can also manage instances of the SQL Server Database Engine created by any edition of SQL Server 2005. Note: SSMSE cannot manage SQL Server Analysis ...

Truncate a SQL Server log file (Reduce the size of an LDF file)

I have been doing database administration and have been asked several times to reduce the size of database files. The actual mdf file is small, 3MB, but the LDF file is 10GB !! I have read about the DBCC SHRINKFILE command and tried this, but the file has stayed at 10GB even though it said the command executed fine. I've also tried using the wizard in SQL Server to reduce the LDF to a specified file size (800MB), this also failed to change the size even though it gave me the impression it had worked and was successful via the wizard. The best thing I found is to change the recovery mode of database to RECOVERY SIMPLE before executing the SHRINKFILE command. After that change back the recovery mode to FULL . ALTER DATABASE ExampleDB SET RECOVERY SIMPLE DBCC SHRINKFILE('ExampleDB_log', 0, TRUNCATEONLY) ALTER DATABASE ExampleDB SET RECOVERY FULL Happy Coding :)