File... Open.

That's it. It's really straight forward.

No. You should be able to open a live file. I do it all the time.

Oh wait, I see what you said. If you want to aggregate, you do have...

There are three ways to access the data in Extended Events. You can use the Live Data window within SSMS. It works really well and has a lot of functionality...

Which tables are these from:

and DTMTRADEDATE='2020-07-28'
and STRSALETYPE in ('I','W')

If those columns are in any of the tables where you're doing a LEFT JOIN, you should move these...

I assume we're talking about a batch here with multiple statements?

In that case, put Extended Events to work. You can create a session using the sql_statement_completed event for batches, or...

Nah, interrupt sounds fine. Ha! I'll see what I can do to get that fixed.

BTW, 3rd edition is WAY better than the first two.

Changes to the connection strings? ANSI settings? Differences in compiled execution plans? As above, wait statistics?

These are just a few of the possibilities. Also, you running a batch versus your...

Tons of stuff is faster in 2017. You should see what happened with 2019. They improved all sorts of stuff even more. It's honestly insane just how much better the...

OK. So, with ColNumber as the primary means of accessing the data, probably, and you should test this, not just trust some yahoo on the internet, that's your clustered key...

Okay, maybe I misunderstood the OP, but I thought from their explanation of the problem that they were trying to use the TOP clause to only get part of...

A stored proc would just use the script you have. It'll work.

In addition to everything Grant said, and he literally wrote the book on execution plans:

https://www.red-gate.com/simple-talk/books/sql-server-execution-plans-third-edition-by-grant-fritchey/

I'd also point out that the ORDER BY dufp.FeatureName will cause a sort to...

The key here is the types of queries, not simply should I throw an index on. Columnstore indexes are meant for analytical, aggregation & large scan types of queries. That's...

I assume you've tried and the error explained that your column names are not there. You can't create a view based on ad hoc queries because the view definition needs...

All the cost is located here: [Excel_DK].[dbo].[Excel_DK].[pk_ID] [DUFP]

The predicate is: [Excel_DK].[dbo].[Excel_DK].[PartNumber] as [DUFP].[PartNumber]=[@partNumber]

Probably need an index on that with some INCLUDE for the other returned columns.

Also, you have three different...