do not allow for dynamic sql to be used.

Provide the needed stored procedures that accept all input parameters and only grant the application account execute authority for the sprocs.

If these tables make the majority of data of that database, just restore the full database to a new database name and remove the ones you do not want to...

have you been able to intercept the long-running-blocking transaction ?

What is so "special" about it ?

have you checked ( and validated ) the "know issues" for CU16 ?

Validate the...

The biggest optimization I've done is to have its name meet our naming conventions ∇

I'm having an issue on 2016 and 2017... If you have 2019 or any version prior to 2016, would you run the following code, please, and let me know...

Why upgrade to SQL2012? If possible, go for a supported version. Performance and management features have been enhanced very much!

Also double check the current db levels for all databases!

e.g. SQL2012...

in this example, I've oriented everything towards its end of month date.

When working with date/datetime, stay in that data type as long as possible because of validation and appropriate builtin...

during the setup process, the used accounts are being granted connect to the endpoint, so that is covered.

what have you tested for this homework assignment??

Is that 1,5TB compressed backup size?

Will you be using backup to url= blobstorage(v2?)

or backup to azure file storage?

network speed 100mbps: is that your internet connection speed?

Are you the only user...

Best you can do is to script out the endpoint you've created using SSMS and SQL authentication and see what it used.

We always user the sql  server service accounts (...

It's almost humorous as to the amount of irony...

ah, the joys of would be JSON

SUBSTRING to the rescue

declare @wouldbejson NVARCHAR(200) = N'{BATHROOM CLEANING}{2.5%}'
 Select charindex(N'{',@wouldbejson, 1) as firstoffset 
, charindex(N'}',@wouldbejson,1) as firstEndOffset
, charindex(N'}{',@wouldbejson, 1)...

Why did it take...

Current for SQL2019 is CU17 ! Make sure you're keeping up with these cumulative updates ! They fix a lot, but you'll have to test !

Also: check "Manage...