Hmmm...

I'm not sure. Check your SSMS. Make sure you're on the latest version. Then, it may be simply that the load on your system is such that querying Query Store...

Then you may need to create a temporary storage between the two. Load a table somewhere, then call the other query.

Also test whether doing an outer join to the approved table and looking for nulls might be faster than the NOT IN.

To tell you where the row estimates are coming from, I need to see the execution plan, query and statistics. However, in general, the row counts come from the statistics....

Piling on just a little. It could break things. It completely depends on how you do deployments of changes to the structures in your database. A schema bound view means...

There are a number of things that can cause different execution plans. First up, and usually the most common, is parameter sniffing. A value is passed to a stored procedure....

I'm a little confused as to why this is a problem. If you have a way to tell SQL Server, hold all the data on this query, then, you have...

Try running a query or three to see what happens. The system tables are pretty straight forward to use. Let's figure out if it's Query Store itself that's a problem...

Cheers!

The reports are pretty chatty. Have you tried just running a query directly?

What about using TOP 1 and order by the 'Last touch date'?

I read The Fort. I've also read Cornwall's books about the battle of Agincourt. And the Last Kingdom. He's got some great stuff.

BTW, you'll get a lot more attention by posting your stuff to a new question. The only people likely to respond to this are those of us who are following...

You may have kind of outlined the issue. You truncated the data, which will empty the statistics automatically. The SELECT query runs after the truncate, but before the data load...

You're past the edge of what Express is used for. I'd strongly advise you to upgrade to a paid version of SQL Server. You can take advantage of more and...