In your first query ( "then" part )  you only select columns of the "DROPS " table.

of course, your "ELSE" part will only get executed when it does not find...

if your storage is a SAN, you could implement Storage Replication with failover capabilities. ( Storage arranges sync )

On the newer SQLServer side ( first on SQL2012 ), you could...

• This reply was modified 4 years, 7 months ago by Johan Bijnens.

Just my 2ct:

Azure AD <> on-prem AD ! 

Granting an Azure AD user or group requires :

1 ) An Azure AD account ( user or group ) to be granted Azure...

Just wondering how the current solution performs with date/datetime data types on a larger set of logging data.

Regarding your I/O errors: You MUST investigate these as SQL Server is only raising this alert if a single I/O takes more that 15 SECONDS !

This may indeed have a...

Do you document "preferred node" in SQLServer ?

If yes, you could have a startup stored procedure checking that value to the current value and raise an alert or send an...

Have a look at powershell module dbatools ! it has very nice features to support your migration.

DBATools sql server migration enhancements

FWIW the execution plan will show the indexes it plans use ( and estimates or actual usage values )

Also keep this note in mind: "...optional for computers that do not host Microsoft SQL Server Reporting Services."

You only need to provide the latest CU.

It includes all others  !

-- added --

At install time ( of a sqlserver instance ) , you can indeed point to a path...

• This reply was modified 4 years, 7 months ago by Johan Bijnens.

I think you just have to start from the actual CU you are trying to install:

Set-Location 'E:\SQL_2019\patches'
SQLServer2019-KB4577194-x64.exe /ACTION=Patch /ALLINSTANCES /QUIETSIMPLE /IACCEPTPYTHONLICENSETERMS /IACCEPTROPENLICENSETERMS /IACCEPTSQLSERVERLICENSETERMS

Just my 2ct: Check this value.

Maybe activating this setting can take some pressure of your plan cache because it only has to calculate the stub and not actually put it...

Of course, a monitoring product is nice and fine and $$

But, if you are on a 0 budget, you could start the KISS way:

( we always install as DBA DBMail...

for what it's worth ...

- it took me 5 years to get our apps to a state that sysadmin was no more needed and no non-dba had sysadmin at OS...

have a look at SQLServer Joins