March 31, 2015 at 7:22 am
Hi All,
I just wanted to know if anyone had experienced the same problem and if they had did they get a resolution. I have recently started a new DBA role; the company has 15-20 SQL instances (all different versions) supporting many different 3rd party applications. I would like to rationalise this down to much smaller number of servers and utilise AlwaysOn to provide HA. Almost every supplier that I have spoken to will not support their application if we migrate the database to AlwaysOn (some are even Microsoft certified partners). If anyone has any suggestions on how I can progress this I would be very appreciative.
Thanks
Phil
March 31, 2015 at 7:29 am
You mention you have a mixture of SQL versions, which you would have to upgrade to SQL 2012 to use this feature.
Is it specifically using AlwaysOn Availability Groups that they say they won't support? Or are they just saying they don't support the application on SQL 2012 in general?
The Redneck DBA
March 31, 2015 at 7:31 am
Hi,
They will support SQL 2012 but not if we use AlwaysOn.
Thanks
Phil
March 31, 2015 at 7:53 am
My company sells a software package of which the official statement is that we do support SQL Server Clustering but not always a failover. A failover can sometimes require a full (lengthy) restart.
I've been told that AO does not cause a possibly disruptive hickup but have to read up on the subject to get my facts straight.
Maybe a similar viewpoint here? I wonder what it actually would mean that a vendor supports AO. What if any software developments are required to support it?
March 31, 2015 at 8:55 am
There are SOOOOOO many things that come into play with Always On that it isn't even funny. Most people don't have ANY clue what they are getting into or the issues/hassles they face when they first go down the AG road. Properly "supporting" an ISV app on AG requires changes to code in the app, ENTERPRISE EDITION SQL SERVER throughout the ISV development stack (likely hundreds of thousands of dollars in licensing, if not more), more testing scenarios (actually you are lucky if they have ANY true database-level testing), training and operational experience for DBAs, etc, etc. If I were an ISV there is absolutely NO WAY I would even THINK of supporting AGs either unless I made a TON of money off of HIGH END clients.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
March 31, 2015 at 9:03 am
In my previous employment we (I) successfully migrated a Microsoft Dynamics Nav 2009 application from SQL Server 2008 R2 clustered instance to a 3 node SQL server 2012 Always On availability group. This involved lots of testing but absolutely NO changes to the Nav code.
March 31, 2015 at 12:06 pm
I'm with Kevin. And the way around this is to try out the third party software on your own. Don't look to them for support. Test it and see if it will hold up connecting to a Listener and during a failover. You may wait a long time for the vendor to say its OK.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply