you can code it in a c# script within ssis - most likely there are already functions to do that including .net native ones.

event viewer - see this link for some info https://docs.microsoft.com/en-us/sql/integration-services/performance/events-logged-by-an-integration-services-package?view=sql-server-ver15

better to run packages on filesystem or catalog - easier to check errors and easier to change...

event viewer - see this link for some info https://docs.microsoft.com/en-us/sql/integration-services/performance/events-logged-by-an-integration-services-package?view=sql-server-ver15

better to run packages on filesystem or catalog - easier to check errors and easier to change logging level

as far as I know yes

Command line setup is quite used for automation but this is one of the cases where doing on command line is likely to b e...

argh. clicked the report button by mistake - can some admin undo it please.

changing server collation is fully documented and supported by Microsoft - although the link I gave above...

you may be able to change it while still on the AG - but if it does not then remove the AG and do the same steps.

see https://www.mssqltips.com/sqlservertip/3519/changing-sql-server-collation-after-installation/

option Option #...

I'm at loss here - just tried it on my own server, resetting session completely even and bcp not trapped - bulk insert is logged fine (once I add the...

better give us the extended events script - it's likely it needs slightly different capture settings and a few of us here can help with that.

all information is on the manuals at https://docs.microsoft.com/en-us/sql/relational-databases/replication/sql-server-replication?view=sql-server-ver15

more specifically you wish to look at the supplied stored procs which will allow you to do all work. full list here https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/replication-stored-procedures-transact-sql?view=sql-server-ver15

with...

for a standard normal DBA no - for you and based on your interaction here over last few years I would say it will add a lot of work

and if all this is within a transaction scope why not use a temp table - if created and used within the same transaction it will be available to all...

datetime DOES have a format on convert - and that is what is causing it to fail.

format 1 is US - so date string should be...

datetime DOES have a format on convert - and that is what is causing it to fail.

format 1 is US - so date string should be on format "mm/dd/yyyy"

for YYYY-MM-DD...

the truncate sp needs execute as owner.

the sp that calls it does not need to have "execute as owner" - only change you need to do on that one is...

either ALTER table or execute permissions on a proc that does the truncate like the following

create procedure TruncateMySchemaTable
with execute as owner
as truncate table schemaname.MyTable;