In general terms we use a join hint is to correct a failure of the optimizer to identify a better query plan. This can happen for many reasons which broadly boil down to optimization being a "good enough" approach constrained by a time budget for finding a plan.
"also called a semi-join hint". With a semi-join we are only ...
If you check out the documentation for the USE statement, you'll see that it is not supported for Azure Synapse Analytics (formerly Azure SQL DW).
To change database contexts, you'll have to open an explicit connection to the desired database.
If you're having issues with your IDE, try specifying the desired database in your connection string when you ...
After reaching out to Azure support, I have managed to solve the issue.
Part of the support engineer's answer included the following:
I've reviewed internal telemetry and can confirm that the statistic listed in the error does not exist. This is likely a compute-node-level statistic that wasn't cleaned up properly.
I was able to confirm and fix this issue ...