I haven't encountered issues yet.

In any case, best is to start your preparation using   SQL Server Data Migration Assistant

Regarding your error: Check the choose function in Books online ! It expects an INT for index value !

check out date functions in books online !

With regards to using the "not exists " variant vs the "left join where key is null" : it all about the volume you expect to delete vs the set...

FWIW

Have you tried replacing the "not IN"-lists with temp tables or tablevars ?

Basically you have SQLServer using its query engine in a better way using table objects in stead of...

Using Standard Edition I assume.

AFAIK Std Edtn only supports Basic Availability Groups and has limitations !

Get well soon, Ken

have a look at Scope: The drastic caveat with Logon Triggers

We have automated weekly restores ( including checkdb ) .

This target server has a C-drive and one big raid-0 volume as that is its only purpose.

It holds max 2 user...

That's wonderful news, Kendra and Jeremiah.

Keep in mind, your dogs immigration will need some time too, maybe even a quarantine time.

All the best in the UK

and, depending on your view definition, the result must also meet the view specifications !

( With check option )

ref: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-view-transact-sql?view=sql-server-ver15

Please upgrade to the latest CU ! You are missing essentials and RTM already had a mandatory hotfix at launch time !

https://support.microsoft.com/en-us/help/4536075/cumulative-update-2-for-sql-server-2019

Please let me know if that helped !

Good points !

what edition are you using ? Std edtn  vs Ent edtn ?

( No backups on secondary replica with basic AGs ( = std edtn ))

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

What did you test ?

logically step-1 determine the max CreatedDate per orderid

logically step-2 update all rows for the given orders that do not have CreatedDate equal to the max_CreatedDate for...