The problem here is how SQL Server generates the execution plan for the query using the view.

If SQL determines that filtering earlier in the plan is the better option then...

Just curious - but how and why would you archive 'Quality History' if there is no Quality_Date associated with that row?  I would assume that not having a quality date...

You can, and definitely should, get rid of the other ISNULLs in your WHERE:

AND ISNULL(d.value_2,'') NOT IN ('Clay','Volusia') --replace with -->  AND d.value_2 NOT IN ('Clay','Volusia')

AND ISNULL(rc.referral_category_ud,'') <> 'FFS_NO_TAKE_BAC'...

• This reply was modified 2 years, 9 months ago by Jeffrey Williams.

He also was only testing...

Using .AddWithValue will end up costing you a lot more than...

Instead of enabling both successful and failed logins - you can configure an audit instead.  The audit can also send the data to the application event log -...

Instead of enabling both successful and failed logins - you can configure an audit instead.  The audit can also send the data to the application event log - but that...

It seems this thread has gotten off-track.  The original question was why does NOT IN behave the way it does - and that is easily explained when you consider the...

Maybe I am off-base here, but this really isn't about how Microsoft handles NULLs, rather it is more simply a logic problem.

When using IN - match on ANY item in...

Add a new volume - either as a mount point or a separate drive.  Add a new file to the PRIMARY filegroup at the same size as the exiting file(s)...

@AntGreen - the process you outline isn't supported.  That process allows for one version up on the OS and/or SQL Server only - which won't allow for upgrading to SQL...

In the left pane - select Expressions.  Find the one for Files - and setup the expression.

Thanks, I do believe we are.

• This reply was modified 2 years, 10 months ago by Jeffrey Williams. Reason: Stupid phone

Correct, you convert the local time to UTC then perform the conversion to Unix timestamp.

In fact, the numeric timestamp is only UTC by convention.  There is nothing inherent in that...

I understand that, but converting to or from a Unix timestamp doesn't need to know anything about UTC.  The conversion is strictly based on the number of seconds or milliseconds...