Actually, if you restore the backup to an instance as a new database, there is no need for a tail-log backup at all !

( this is a flaw in the...

You've messed up the xml to much !

It doesn't produce a garph anymore !

Use dummy names ( T123 / t124 / ... ) instead of "<table name>" as < and...

can you share the xml?

A tail-log backups only purpose is that you can restore the original database as is was on the target server right before you performed the intended restore.

What's the difference with...

I requested it to write the TSQL DDL to created the needed tables based on your input.

It came up with this. ( not perfect, but it gets you started )

fwiw - post this question as input for copilot . microsoft . com and add "Write the tsql stored procedure to process my expenses report per batch"

See what it comes...

Keep in mind, everybody that can use the linked server, will have the authority of the given "rmtuser" !

That's the reason I only allow read-only accounts to be used in...

How did you define the security to be followed when using this linked server ?

even on SQLMI there are restrictions for CLR stuff:

is your user profile stored with remote as primary ?

( = wrong implementation of a great concept )

indeed. Thank you for pointing the subtle difference.

Tried it.

Didn't provide the data I aimed for.

It did generate the same error as the debug channel at create time.

However, now I see it accepts the create of the event session.

Time to investigate ( for a short...

doesn't work !!! ( see OP )

did you check for "Cross database ownership chaining" ?

Ref 2: "Understanding Cross Database Ownership Chaining in SQL Server"

I want to restore the DBs to another MI in regular intervals as use to do in traditional SQL. Please suggest how to make it possible to schedule automated...