against i mean execute.

I want to execute a stored procedure that is not on the linked server. The stored procedure would update tables on the linked server

ServerB is my linked server.

So, if the stored procedure exists doesn't exist on ServerB i can still executed the procedure against ServerB?

Yes it is

The databases is encrypted on the primary so when you restore to the secondary it is also encrypted.
If you backup the service master key from your primary server and...

No it didnt from what i am aware of it.

Why, if the DMK was restored from the primary should this not happen?

Yes it was

Would i be best to just update the local login to another account?
Will the retries work? Is it just new connections that would be affected?

3 Servers.
Server 1 and 2 synchronous commit with automatic fail over.
Server 3, asynchronous with manual fail over.

I can run a job that checks which server is...

Yes, I know select @@version works but I need to determine for it for number of servers so i would prefer to have a script that checks the version and...

I mean Azure Data Warehouse

I won't be changing the data that will be moved.

It will be just a straight copy from SQL Server to a single source.

It will be just a copy of production

Yes backup log are in the shared folder.

The logs are being applied to the secondary.

No issues with copy/restore jobs.

Transaction log report showing correctly on the secondary.

On the primary, transaction log...

I ran the following on the secondary

execute sp_refresh_log_shipping_monitor

@agent_id = 'B7EE4B00-364A-49F4-AC4A-391722F0E66D',

@agent_type = 1,

@database = 'Database',

@mode = 1

Getting agent ID from the below query

select *

from msdb.dbo.log_shipping_secondary_databases as sd

join msdb.dbo.log_shipping_secondary as...