I would like to dig deeper into SQL AlwaysOn, as I have not had the chance to implement it before.
As part of our recent GP 2018 upgrade, our DB Team set up a SQL Availability Group. So, we already have a secondary SQL Server with the all the GP data. Our DBA team wants me to repoint everything to a SQL alias so we could fail-over if it became necessary. I would like to hear of any gotchas, issues, show-stoppers, or just good advice on what to watch out for when implementing this (in test first, of course).
Areas I have concerns about
I have read that GP supports AlwaysOn and have the SQL 2012 document "Guidance for running Microsoft Dynamics GP with Microsoft SQL Server AlwaysOn Availability Groups".
We are on GP 2018 R2 and SQL 2014. An upgrade to SQL 2017 is being planned for early next year.
If you've found this thread useful, dive deeper into User Group community content by role