Found the issue... the user who found the issue provided me with the code... which I just modified here to reproduce it "as-is"... when I  copied the same code into...

Sure...

USE [TempDB]
GO

DROP TABLE IF EXISTS #Results
SELECT 'A' [Column1], 'B' [Column2] INTO #Results

SELECT * FROM #Results

SELECT * FROM #Results
WHERE 1=1 AND [Column1] in ('A') AND [Column2] = 'B'
...

My understanding of how the engine interprets "equals" versus "IN()" is pretty much the same.  The IN operator is used to compare a column value against a set of values...

I did come across this... which does explain it... but geeez, never in 24 years have I been bitten by this in a VIEW

https://learn.microsoft.com/en-us/sql/t-sql/data-types/precision-scale-and-length-transact-sql?view=sql-server-ver16&redirectedfrom=MSDN

"Operators can always change precision scale..."

<table>

<thead>

<tr>

<th>Operation</th>

<th>Result precision</th>

<th>Result...

Thanks for the response - it's great to see the old names replying all the time 🙂

I have considered this and we've actually used it and an alternate (SQLSafe Virtual...

Great stuff!  Thanks for the advice thus far....I'll play with this a bit and see if it works for this scenario

Can you please post/attach your entire script?

Thanks for everyone's comments thus far, that's the current plan - restore to a different server, different storage, sans Vormetric and see if the corruption is still present.  Just so...

I wanted to also note that Vormetric encrypts the data at the OS/folder level

Wow this is a blast from the past!  If it's sending a blank email it's because one of the values being assigned to a parameter is NULL.  I would check...

Rewriting it using the temp table is an option I did consider but was hoping for one of those “a ha” moments ??

The execution plan is not that bad and...

I realize this is a very, very old post but did you ever get this resolved?  If so, what steps did you take?

My team just got plagued with the same...

Thanks Steve, was just seeking confirmation. I realize this isn't a "standard" or best practice per say, but always have added it in to facilitate server builds across large distributed...

Is there any negative impact to adding trace flags to a server startup proc?  More of as a failsafe that anything...

Resolving this issue for me was simply a matter or placing the DB in EMERGENCY mode and bringing it back online:
ALTER DATABASE PROBLEM_CHILD SET EMERGENCY
GO
Once...