Just thought of a small scenario that MAY not impact you, but thought I'd toss this in here too - do you have any heaps? The reason I ask is,...

Makes more sense to me now, but I know I still prefer having a bunch of "useless" backups rather than an inconsistent backup strategy. But that's just my opinion. Doesn't...

I could be mistaken, but what you set up is an isolated network so SQL can talk to AWS for authentication using AD authentication BUT you have no computers joined...

As a guess (no access to or history of your system) - I would say that in some old old version of SQL Server, single user mode on system databases...

Possibly a silly question, but is there a reason for this obscure backup strategy? I am just trying to figure out why you would want to have backups taken sporadically...

One thing I would be careful of is that using AKV means your SQL instance relies on a cloud service to decrypt its data. This is important for 2 big...

Looking at the docs, it sounds like there should be no reason that this shouldn't work as long as AKV supports one of the methods that SQL Server supports.

That being...

My advice would be to do more staged upgrade and migrate it over to an SSIS catalog. Like upgrade from 2005 to 2008 R2 to 2012 to 2014 to 2017...

I personally can't read the screenshot, but kudo's to you frederico_fonseca for reading that!

Just as a second opinion on this, I think that is normal behavior as well. If I...

Yeah, that looks like it'll not work how you expect because your line:

set @upd_tab = (SELECT name FROM sys.objects where name like '%job queue entry$%' and type_desc...

Reading the notes on the link you provided, it sounds like things changed with custom authentication in 2017 in that it no longer relies on the ASP.NET stuff and now...

There is no "straight answer" to it as it highly depends on your usage. If the system is currently running, look at the max memory value and look how often...

Another thing to add is that each SQL instance needs SOME RAM. If you have your max memory for those set too low, you can run into issues.

I do agree...

For uploading the data set , that depends on how you set things up. For uploading the data source, yeah that is required otherwise the report has no idea what...

If I remember right, jobs do not migrate over when you do that. BUT since the old system is still available, just script out the jobs and run that script...