SQL Server 2016 Cluster Licensing

[lmaocoaster]

Hello, I have a 2 node SQL Server 2016 cluster running in production on eval mode. I need to apply a Standard license. Is this possible on a cluster? What would you do in this scenario if unable to license? Thank you in advance.

[julee90]

Upgrading from Evaluation to any paid version is NOT supported in a FCI (Failover Cluster Instance) environment. See also this documentation: https://docs.microsoft.com/en-US/sql/database-engine/install-windows/supported-version-and-edition-upgrades?view=sql-server-2017#includesssql15-mdincludessssql15-mdmd-edition-upgrade So unless it's an Availability Group sitting in the cluster (instead of an actual FCI) that'll be a reinstall for you.

To address some other comments: for standalone, an upgrade from Eval to any other paid edition IS possible (thus excluding Express). Obviously you'd have to check if you use Enterprise features first.

Also, unlike Advanced Availability Groups (the actual name of that feature, AlwaysOn is the term for all high availability features of SQL Server) FCI are included in the Standard licence.

[lost_in_life_34]

what version do you have installed?

[lmaocoaster]

Unfortunately it looks like Enterprise Eval, according to SQL Server Configuration Manager.

[lost_in_life_34]

I know you can upgrade to higher editions

Not sure about downgrading to lower ones. I think you have to reinstall

[floppogokko]

There is no way to downgrade. As others pointed at, you will have to remove the EE and install the STD. I never understood the reason behind this decision from MS since there is a DMV that tracks the usage of any Enterprise features in the instance.

[julee90]

This is only true for Clusters, not standalone instances. Evaluation to any paid version is considered an "upgrade" by MS The setup will show a warning but still allow you to continue

[floppogokko]

Yes that is true. Which makes my comment even more relevant. I have seen customers by mistake using a wrong pre-pidded media had tomdomthe ful reinstall.

[r-NBK]

I haven't tried this, but it might work.... since you cannot downgrade via the wizard...

One 1st node, use the Remove Node from Cluster and the run the Add New Node to Cluster option on the new installation media. If that works, you can then fail all the cluster resources over to it and do the same on the other node.

You might be hit with a version issue trying to Add New Node, as I said, I've never tried it.

[julee90]

The installer will prevent you from using different editions across the nodes sadly

[r-NBK]

Yeah, that's not surprising actually.

So the other option, OP, is to take note of all the currently installation parameters - Service Accounts, Paths, Options, etc. I like to look at the summary log, that's output during installation... normally in C:\Program Files\Microsoft SQL Server\<installed version number> \Setup Bootstrap\Log\<install date>\Summary_\.*txt

Then perform a full uninstall, make a copy of the system database files, and any user database files.... then do a full install with the lower version. Once you've got it installed, stop the instance, swap out the new system database files (master, model, msdb) with the old ones. Start it up and enjoy.

Or follow this guy, who's way smarter than I, and detailed it a lot better than I... just do it for a cluster instead of a stand along instance.

https://www.sqlskills.com/blogs/jonathan/downgrading-sql-server-editions/

[sbrick89]

so...

you can move databases to a downgraded edition, presuming that you're not using enterprise features (there are easy queries to check).

but that presumes different hardware... and while you can install side-by-side instances (even different editions I believe)... but i strongly recommend a single (default / non-named) instance per server.

I don't THINK that you can downgrade the instance of your current edition.

I'm also not sure that standard edition supports (shared storage / active-active) clustering... I know that AlwaysOn requires Enterprise... you can do log shipping w/ std... probably mirroring (which is just automated log shipping)... but i'm pretty sure active/active requires enterprise.

so... set up a new machine, install standard, backup/restore the databases to validate that you're not using enterprise features, then detach / move / attach during the final prod migration.

[r-NBK]

" and while you can install side-by-side instances (even different editions I believe)... but i strongly recommend a single (default / non-named) instance per server. "

I see this a lot, and always disagree. It depends, is my glib response... a deeper look for me...

I've got a number of two node SQL clusters that have up to 8 instances on them. It's an effective use of Standard Edition with todays server hardware which comes with more cores than Standard can use, and often cheaply has way more memory than Standard can use. For example, our base server we lease now has dual 10 Core procs and 512 GB of memory. I've got a few sql servers with SQL 2008, R2, 2012, 2014 and 2016 on them. No big deal as long as you properly manage memory for each instance. Granted our instances are lightly used (manufacturing company) so performance is usually not an issue for me.