I did some more testing and investigations.  turns out the queries running against target table is using "with(nolock)" table hints.  This, in my understanding, from the testing  is what's causing...

• This reply was modified 3 years, 8 months ago by  AnzioBake.

Thanks Grant

I have created new thread with some more info:

https://www.sqlservercentral.com/forums/topic/empty-index-statistics-object

I realize this thread is two years old....

I too am on Sql 2016 in Compatibility mode 2012.  In the past four months we have had three occurrences of this problem.

We...

Thanks Chris for the response.  
As we  moved 400GB of data from the source files, and it is very unlikely to be require in the near future, the shrink...

We came to the similar conclusion, i.e. the shrink affected the table.  That is when we started looking at the table and index (statistics) statuses. Rebuild indices and the table...

thanks, but we already have a solution.  we are just interested in an actual explainantion for future reference i.e why index maintenance resulted in this sudden change in behaviour

We have confirmed that updating statistics with fullscan did not improve query performance

From what I have read the Cisco UCS sytem as example does exactly that:

Start with one, add a new blade, configure and you have the extra processing power on the...

okay, so maybe my understanding is incorrect

as examples:

Fixed server: 4 sockets, 8 memory slots, dual NIC, dual IO connectors

Blade: Four server slots, each with above

When server become hardware bound, for...

Fixed servers have limitation too. The blades, from what i understand, can be "grown" to a greater extent as the SQL server demands increase and it is therefore possibly...

Cross Apply's usage is for joining Table1 to the results set of a Table Valued user defined function that uses one or many values from the rows in Table1...

Looking at the attached SP this is a Oracle Db

ref SYSDATE and RAISE_APPLICATION_ERROR

are not SQL functions

without knowing your exact requirements this may be inappropriate

Instead of this massive loop why not simple use something like below, note:- Below is not a complete solution

Select

PossibleDate

From

(

----AllPossibleDays

Select top( Select...

CONVERT( datetime, [Date], 103 )

you could do a group by on

bnoun, upp,

And

Min( [1] ) AS side1,

Min( [2] )...