That is the answer. I was not aware of this procedure, thank you. If would like to make this the answer, then I will accept it.

Wait, I think I understand. If another job is created to run the AddEvent at the desired interval and simply not call the API altogether, that might be a solution for the not supported subscription schedules. WOW thanks.

Solutions here are great, however, we would require a new custom thread pool service to run all reports and tend to the schedules:). Think it may be easier just to turn "End of Month" into "Start of Month" since it is not mission critical a few seconds won't matter, just the timestamp on teh report will be off and wonky..

To enable a subscription schedule for "Last Day of Month" and for every X months.

Would a one-way Forest trust be a possible solution here?

Thanks for the tidbit.

@J.Mini - Not much unless you use it to access an RDS Sql Server instance.

I bet you can find some pretty good PowerShell scripts that can connect to both systems. Once connected to both endpoints something similar to what is described in this article can be used to move data back and forth. dba.stackexchange.com/questions/191679/…