What is actually the question ?

Why are inserts failing ? ( trace it if it's not available in the application logs )

no

• Keep in mind that creating the backups is only a first step !

  You should also perform restores on a regular basis to see of your backups still meet your...

If SQLServer detects the new definition to be the same as the current definition, it will not act.

However, if there are data type storage alterations, it will have to rebuild...

Keep in mind, to retrieve data in a certain order, you need to add an order by clause to your select statement !

Check the connection objects used by your application

My worst nightmare has come true.  We upgraded to 2022 and stuff is crawling now.  We turned off Query Store and went back to the old cardinality estimator and...

prevent the accounts to connect to the database.

To differentiate these accounts for this action, create a database user role which you "deny connect"

for your maintenance, you add the accounts...

use powershell dbatools ( free ) copy_dbalogin to copy accounts (including sid) from one AG member to another and avoid these issues.

wat's the isolation level the sproc is called with from the application ?

regarding implicite transactions, it all depends when the application will require its first lock and how...

use "restore filelistonly from disk=youdbackupfile" to check if the file contains backup information for different databases !

or "restore headeronly from disk=youdbackupfile"

Are you sure your databases will only have 2...

• This reply was modified 1 year, 11 months ago by Johan Bijnens.

No.

But it all depends if a new version functionally implements a functionallity your application may need or benifits from.

Keep in mind some of the new stuff in databases have been...

If you're curious about transaction log activity for open transactions, Paul Randal has a script at Script: open transactions with text and plans.

did you actually install SMO for SQL2016 ?

that's because you  don't start from the same set of data due to the "not exists" credential. ( which checks for existance in the target table !! )