Have you looked at creating a credential and an ssis sql agent proxy then running the step under this proxy

I'll assume Azure SQLDB since you cite "logical server".

Important to remember with Azure SQLDB there is no concept of server logins and permissions, indeed, you shouldn't be (and shouldn't need...

start here as this has all the info

https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-landing-sql-server?view=sql-server-ver16

You don’t need to use a file for the delete records, you have a memory resident recordset which you can loop through, could then output this status to a log...

ok, but as suggested by others why dont you just connect directly to the source first, build your recordset and then connect to the target and perform whatever work needs...

This is the snippet from script. The serverInstance and Query both use servers that have the Dash(-) in their names.

stopwatch = [System.Diagnostics.Stopwatch]::StartNew()
# Define your SQL Server...

Azure SQLDB or Azure SQL Managed Instance?

Vdis can be started and disposed to meet dev requirements

Hi,

we check our databases every day with dbcc. If you got an...

Why use sql auth and not windows auth?

You also need to bear in mind that even after decrypting the database and dropping the encryption key and cert it is still possible part of the transaction log is...

Obvious question, why does this person have the ability to do this in prod in the first place, kill this and you resolve 99.9% of the issues

Put delete triggers on...

again VDI will be best

Virtual desktop infrastructure is a common usage for exactly this, it keeps the organisation’s data where it should be and still easily accessible to those who have dev and test...

Original DBCC CHECKDB output would be helpful, with no outputs available would be safe to say data loss is unknown

if you knew what table(s) or index(es) were affected could restore...