I realise this is an older post, but I was wondering if anyone has experienced any downsides with automatic tuning being on. It seems it is all positive from the...

Once  transactions are moved over to the replica log get cleared. Problems arise if there is ever a connection issue.

Just to add my bit:

In the Query Store you my want to look at regressed quries. In fact look at your Query Store overall from many views,... I/O, cpu, running...

Set the size manually after restorng and see if it does not get shrunk after wards.

Are you connecting to the correct database and not a test server ?

You can try to check the Query Store for "regressed queries". These are ones that have chosen less optimal plans. There could be a few procedures this is afflicting but...

Sounds like your transaction log being full is putting a stop to replication. There is no need to "shrink" the log file if it is just going to grow again....

Secondary replicas as I understand have read intent off by default. Did you make this change in the application or the database ?

Seems to me you may want to get familiarized with the LAG() function. I am sure you can incorporate it into your solution,

https://docs.microsoft.com/en-us/sql/t-sql/functions/lag-transact-sql?view=sql-server-2017

The previous months ending balance is...

I imagine if your statistics are up to date you will not have to consider the join order as the optimiser will define that. There may be times where it...

From Mircrosoft Docs : "

When SET XACT_ABORT is ON, if a Transact-SQL statement raises a run-time error, the entire transaction is terminated and rolled back.

When SET XACT_ABORT is OFF, in...

My one thought here is that a call to a stored procedure may not roll back within a transaction, whereas if you do ,say,  just inserts to multiple tables within...

And what was the result? What exact message do you get?

How do you absolutely know the users do not already have permission?

OR , Is there another permission setting denying this...

Please add sample data along with DDL/DML statements to set up the tables we need to be able to see what you are seeing on your side.

Without knowing more you...

AS Jeff emphasied in his post, look at your indexes on both of your tables (even the temp table). It is worth re-emphasising.

I would also look into how the table...