I should say one thing - before changing compat levels, I would test things out on a sandbox. There ARE valid use cases for using the old CE or older...

I agree that re-doing the backup strategy seems like overkill, especially when it is working. Mind you, as a long term solution and for future supportability, I would be moving...

• This reply was modified 2 years, 3 months ago by Mr. Brian Gale.

That sounds like it may be a bug in SSMS then... but oof... using the edit GUI in SSMS? I find that to be clunky and painful to work with....

• This reply was modified 2 years, 3 months ago by Mr. Brian Gale.

Pretty sure that it is saying that you are  using an old CE because you are running SQL Server 140 but have database compatibility in 120. So the CE is...

As another random thought - Are you seeing any pattern to when it blanks out? Like is it good at 8:02 but by 8:15 it is blank? If so, I...

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...