Found the problem - apparently this is a bug in SQL 2019.

2021-06-06 10:30:21.16 The restore operation was successful. Secondary Database: 'FakeName', Number of log backup files restored: 1

2021-06-06 10:30:21.16 ***...

Just to follow up, that setting is a life saver.

The process I was having issues with is now running at around 40 seconds consistently, it used to be around a...

Appreciate the responses 🙂

I had discounted parameter sniffing (perhaps unwisely) because the same job has been running for over ten years on five different GP databases without this issue.  One...

Ben -

I appreciate the reply.  However, in this case the same service account is being used on both servers, and I made sure that the service account had full access...

Figured it out...  sort of.

I had a similar issue a few months ago with replication.  We'd recently applied a new Group Policy and it had wiped the stored credentials of...

You can do something like this...  bear in mind it may take several minutes depending on how many databases you have, and how many procedures, etc.

declare @find...

To see if it's in a stored procedure somewhere:

SELECT DISTINCT
o.name AS Object_Name,
o.type_desc
FROM 
sys.sql_modules m
INNER JOIN sys.objects o ON m.object_id = o.object_id
WHERE 
m.definition Like '%cmdshell%';

Michael - appreciate the reply; the service account already is a sysadmin, as well as local server admin and network admin.

We found that the "Replace a Process Level Token" permission...

We are using Oracle 12.2

However, I am not using SSIS for anything related to this Oracle connection, specifically because I couldn't get SSIS to connect.  Not sure if that is...

I was thinking along the same lines...  and agree, it's not a serious issue - more of an annoyance.  Was just curious to see if anyone had seen it before...

Thanks for the reply...

I have been digging around for other AD groups but it really does seem to be specific to this one.  If I remove a user from the...

Hehe...  the worst part is the same thing happened like a year ago, but it's been fine since we did the firewall changes...  they just forgot to apply them when...

Found the problem....  *sigh*

Our infrastructure team spun up a copy of our production environment, but forgot to update the firewall to prevent it from communicating outside itself.  So it updated...

We aren't using SSIS - we have a stored procedure that we call where we're doing basically this for each of about a dozen tables:

truncate table xfer_fact_booking
insert...

Steve -

Thanks!  All good points that I unfortunately forgot 😀