In Powershell - you can create a function at the top of the script, then call it later - or you can put a function in a separate file and...

If you create the new database in SQL Server - setup the secondary replicas, then start loading data from your other system, that would work.  But it is going to...

You stated that 'for some reason' SSIS no longer works?  What is that reason?

Using a linked server (assuming this is cross server access) can cause issues - with the transaction...

I would not utilize read-intent for this scenario - that really should only be used for offloading application reads and is not intended to offload reporting users access.

Instead - upgrade...

The failover mode doesn't matter - what matters is the mode.  If the mode is asynchronous - you must switch to synchronous before failing over, or you force the failover...

In an AG - you need to replicate logins and agent jobs to each secondary that can be used for failover.  The logins must be created on the secondary with...

I am not sure what you expect - I have provided more than enough examples to get you what you need.

From my previous post:

Here are some hints:

# Encoding check...

What OS is being used - is it x86 or x64 OS?  Since this is SQL Server 2005 - I suspect you might have an older x86 OS.  If so...

I provided examples of how to work with the BOM and use that - I recommend (strongly) that you do so - instead of the earlier hack I provided to...

As I pointed out in my other posts - that check for 'unicode' is not the best option.  The best option is to check for the specific BOM characters for...

Here are some hints:

# Encoding check arrays
[byte[]]$utf7 = 43,45;
[byte[]]$unicode = 255,254;
[byte[]]$utf8 = 239,187,191;

    if (-not (Compare-Object $bytes[0..1] $unicode)) {
  ...

If the file was created with a BOM (byte order mark) - you can use that to determine the encoding.  Unicode\Unicode (Big-Endian)\Unicode (UTF-32)\Unicode (UTF-32 Big-Endian)\UTF-8 all have a definition for...

A picture is worse than an Excel spreadsheet - we can't take that information and create a test.  You also didn't provide sample data...

BTW - this forum deals with Microsoft...

These are not really issues with SQL...

Not sure what else to say - you seem to have files with different encodings, and worse - some files in UTF-7 which has been deprecated for quite a while.

Since...