SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Licensing Question - Different version instances on one machine


Licensing Question - Different version instances on one machine

Author
Message
GoldenDBA
GoldenDBA
Hall of Fame
Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)

Group: General Forum Members
Points: 3950 Visits: 959
So we currently have a licensed 2014 Standard default instance on a machine. We were thinking about installing a named instance of 2017 to be a non-licensed failover only instance for a 2017 Enterprise AlwaysOn Availability Group. Wondering if this use case is thought out properly? Can we have a non-licensed 2017 Enterprise instance on the same machine with a licensed 2014 Standard if the intention of the 2017 instance is that it will only ever be active in case of a full failover of the AG(s), in which the other Enterprise server will at that point be completely inactive? This is a stop gap measure until we add a large fully licensed server later that will be more active/active.
anthony.green
anthony.green
SSC Guru
SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)

Group: General Forum Members
Points: 77055 Visits: 8653
GoldenDBA - Monday, December 4, 2017 1:54 PM
So we currently have a licensed 2014 Standard default instance on a machine. We were thinking about installing a named instance of 2017 to be a non-licensed failover only instance for a 2017 Enterprise AlwaysOn Availability Group. Wondering if this use case is thought out properly? Can we have a non-licensed 2017 Enterprise instance on the same machine with a licensed 2014 Standard if the intention of the 2017 instance is that it will only ever be active in case of a full failover of the AG(s), in which the other Enterprise server will at that point be completely inactive? This is a stop gap measure until we add a large fully licensed server later that will be more active/active.

As with anything licensing, go speak to Microsoft directly or your software vendor, anything detailed on public forum is opinion only and may not be the case for your company.

Now with that said and reading the 2017 licensing guide (note "Guide") as long as you have valid Software Assurance for your 2017 Enterprise licenses then yes you should (note the italics, as it is only speculation not fact) be ok, but for a complete and concise answer go speak to Microsoft or your vendor, you may have special preferences and terms and conditions to your licenses that we as the public don't know about.




How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger


arr.nagaraj
arr.nagaraj
SSCarpal Tunnel
SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)

Group: General Forum Members
Points: 4740 Visits: 1636
GoldenDBA - Monday, December 4, 2017 1:54 PM
So we currently have a licensed 2014 Standard default instance on a machine. We were thinking about installing a named instance of 2017 to be a non-licensed failover only instance for a 2017 Enterprise AlwaysOn Availability Group. Wondering if this use case is thought out properly? Can we have a non-licensed 2017 Enterprise instance on the same machine with a licensed 2014 Standard if the intention of the 2017 instance is that it will only ever be active in case of a full failover of the AG(s), in which the other Enterprise server will at that point be completely inactive? This is a stop gap measure until we add a large fully licensed server later that will be more active/active.

2017 Enterprise Edition on a machine which is going to participate in AG for failover?
May i know the server edition n version that is going to be active?


Regards,
Raj

http://Strictlysql.blogspot.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search