Focus on the fact that what you're looking at are databases. Ignore the concept of a server. Yeah, it's still there, but it's radically easier to make the shift if...

Starting with the execution plan, you have a lot of issues. This is in no way a simple query. And views that join other views calling other views and functions,...

Partitioning is a data management process, not a performance enhancement process. In fact, unless you can with 100% accuracy, guarantee that ALL queries against a partitioned table will be using...

I am not sure profiler would be of much use to you even if it did support it, Synapse doesn't work the same way as a traditional SQL server...

I'd need to see the execution plan to see how the queries are being resolved in order to make suggestions for improvement.

Always? Every time? Hell no.

Frequently? Yeah, probably. If you're doing new or different functionality, then it's probably a good idea to have different structures to appropriately support that functionality. That's...

I know you said the environments are essentially the same, but then you list a number of differences. It's likely that the reason you're seeing it one environment and not...

What about simplifying this a bit and just use the TOP command. All you need is the ORDER BY. You don't have to go into all that row number...

It should look something like this: hamshackserver.database.windows.net

You just have to edit 'hamshackserver' to be whatever you named your server instance where the database lives.

You'll also have to allow your IP...

In addition to what Johan has pointed out, you can also use Extended Events to capture log behaviors, including the query that sparked them. Here's another article by Paul...

In addition to all the other good advice, look at the logic of the query. Filter data on retrieval instead of loading everything into temporary tables for processing.

I'm with Jeff.

Let's just clarify a bit though. Dimensional modeling is a good thing, for certain kinds of queries. It's not a good thing for other kinds of queries. So,...

The default value was set in 1998 on SQL Server 7. It's utterly and completely out of date. It bears no relation to the modern world. It should be a...

The default value was set in 1998 on SQL Server 7. It's utterly and completely out of date. It bears no relation to the modern world. It should be a...

It's another day when I think SQL Server Central must have been spying on us, producing such on-topic editorials, as here I am, old enough to claim my UK...