Oh, don't do NOLOCK. Yeah, it will enhance performance because it changes how locking and blocking occurs within SQL Server. However, especially if you're getting lots of large scans, as...

Moving the target of your build process to Windows could help solve issues. You could then install whatever tools you needed to that Windows instance. Control could still be through...

There is a way to do this using T-SQL. However, I much prefer using SQL Compare from Redgate (even though I do work for them now, I used the...

Let's start with the importance of SQL Injection attacks, because you are absolutely open to them with this code. Especially the IN statements. That alone, you should rearchitect this.

Next,...

Yikes.

Nope. I'm not going to be much help here with DynamicsAX.

There's nothing magical about snapshot isolation. It helps with reads and blocking. It doesn't help with writes and blocking. If more than one person is attempting to update a given...

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!