There are many business reasons why you might do this.

We have edge nodes where web servers sit in places closest to our customer base and to reduce latency we have...

Well you “could” do 30,000 columns in a table IF you marked them all as “SPARSE” columns.

Now the question is “should” you mark them as sparse.

What does this excel file...

Is the report server DB on a Standard Edition instance?

There was something if i remember correctly that it will pull the edition of the SQL instance as what you want...

Change the respective IP's based on what is changing.

If the "B" side is changing first, move the "B" nodes to the new subnet, change the node IP's, change the WSFC...

Are any of those two IPs the “new locations” IPs?

If not then yes you will need to change the IPs on the listener and WSFC after they have been relocated.

https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-replication-for-always-on-availability-groups-sql-server?view=sql-server-ver16#step7

Did you add the original publisher to the monitor from each replica in the AG as per the documentation?

Your expected result is off.

The value shouldn't be 6.07 it should be 5.666666666 recurring

100*5 = 500

50*7 = 350

850/150 = 5.6666666666666666666666666

select idproduct, product, sum(quantity*price)/sum(quantity)
from Table_1
group by idProduct, Product

There is AOAG's in standard edition, but they have limitations, check out Basic Availability Groups.

But yeah this is the way you want to be doing it now, in an AOAG...

Think the best thing first would be to also plan in a 2022 upgrade also.

2014 is end of life, and end of extended support in approx 8 months, after which...

This is an easy one to test, make a dummy proc which is just a WAITFOR DELAY and call that using the template you have above and note the behaviour...

Given the whole technology stack is 15 years + out of date, and if it works with SQL 2008, just run it on 2008.

Trade 1 unsupported platform for another.

No point...

Sounds like you don’t want 2 AGs and you need to consolidate them into 1 AG.

Or rearrange the DBs in the groups into their correct logical groupings.

dupe post

https://www.sqlservercentral.com/forums/topic/connectivity-issues-3

No tech from this decade then?

All jokes aside,

XP out of support

2012 out of support

SQL Native client (all versions) out of support

You shouldn't be running stuff on these platforms any more. ...

No tech from this decade then?

All jokes aside,

XP out of support

2012 out of support

SQL Native client (all versions) out of support

You shouldn't be running stuff on these platforms any more. ...