Solved

What's the difference between these two "qualifiers?"

Posted on 2016-11-11
3
44 Views
Last Modified: 2016-12-01
What's the difference between these two qualifiers:

datediff(d, max(t.created), getDate()) <= 45

and...

max(txn.created) > DATEADD(DAY, -45, GETDATE())

I'm thinking with the first one you have all of the rows where the t.created value falls within a range defined by the difference of today's date and whatever t.created values equals to 45 days or less.

The second clause is all of the rows that have a date that's greater than today's date minus 45 days.

Even when I attempt to explain that, I'm thinking they are fundamentally the same, but am I missing something?
0
Comment
Question by:brucegust
3 Comments
 
LVL 69

Accepted Solution

by:
Scott Pletcher earned 250 total points
ID: 41884260
datediff(d, max(t.created), getDate()) <= 45

= The number of calendar days (not necessarily 24-hour days) between t.created and the current date must be <= 45.


max(txn.created) > DATEADD(DAY, -45, GETDATE())

= The date and time in txn.created must be greater than the date and time 45 days before today.


The time factor is probably the most significant difference between them.
0
 
LVL 25

Assisted Solution

by:Pawan Kumar
Pawan Kumar earned 125 total points
ID: 41884421
Both are same if you consider the logic.

This <<datediff(d, max(t.created), getDate()) <= 45>> is really bad for performance as it will execute this expression for each row in the table and will lead to scanning the entire table even if you have index on the column.

This <<max(txn.created) > DATEADD(DAY, -45, GETDATE()) >> is good, since we are doing maths with the constant value and SQL will calculate the constant separately since it is not dependent on the any table.

Hope it helps !!
0
 
LVL 77

Assisted Solution

by:arnold
arnold earned 125 total points
ID: 41884665
the material difference is the logical comparison, one deals with integer comparison, the other performs datetime comparison.
The datetime comparison, can be simplified by assigning the date 45 days ago into a variable to avoid running dateadd for every row
Declare @date as datetime
Set @date=dateadd(d,-45,getdate())

Max(txt.created)>@date

Question is the cost of running datediff on every row of a result set less or more than datetime comparison, if not mistaken, the comparison on datetime also scans the entire result set datetime fields are not indexed........
0

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Slowly Changing Dimension Transformation component in data task flow is very useful for us to manage and control how data changes in SSIS.
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

861 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

25 Experts available now in Live!

Get 1:1 Help Now