This charm builds directly on top of the features already offered by the SQL Server Express charm, including all the features provide by Microsoft SQL Server Standard or Enterprise and most important, support for AlwaysOn Availability Groups when deployed in conjunction with the Failover Clustering and Active Directory charms. This allows a great degree of fault tolerance and scalability in no time, by simply increasing the number on nodes deployed by the charm.
juju deploy mssql
juju add-relation mssql active-directory
juju add relation mssql wsfc
juju add-unit wsfc
As the mssql charm is a subordinate charm to the wsfc(Windows Server Failover Cluster) charm, adding a failover cluster unit will add a new node to an Always On availability group.
juju destroy-unit wsfc/
The Always On feature requires an x64 Enterprise Microsoft SQL Server version.
|mssql-service-user-password||The password for the mssql-service-username||string||None|
|always-on-listener-netmask||The netmask for Always On Listener network.||string||255.255.255.0|
|mssql-admin-username||The local administrator that will be used as an MSSQL admin account.||string||None|
|mssql-features||The MSSQL features to be installed. Possible features are stated at
|enable-always-on||If set to “True”, it enables the Always On MSSQL feature.
The following requirements are necessary:
– An MSSQL Enterprise x64 ISO
– The node will be part of a Windows Failover Cluster
– The failover cluster will have a node and fileshare majority
– The fileshare will be an SMB share, provided by an SMB charm
Restrictions that must be considered:
– One database availability group will have only one primary replica
and a maximum of 8 secondary replicas
– The secondary replicas can have read only properties(if set)
– A database availability group can have a maximum of 3 synchronous
– A database availability group can have a maximum of 2 automated
– A database availability group must have a listener, comprised of:
– a listener DNS
– a listener port
– a listener static IP or DHCP enabled
– a netmask for the listener IP
|always-on-listener-port||The port for the Always On Listener.||string||5023|
|mssql-iso-location||The path for the MSSQL ISO file. It can be an URL or an SMB share path.
|mssql-sa-password||The password for the sa account||string||None|
|always-on-listener-network||The Network of the Always On Listener.||string||None|
|always-on-listener-dhcp||DHCP will be used to obtain an IP using the always-on-listener-network
|always-on-group-name||The Always On Availability Group name.||string||aoggroup|
|mssql-version||The mssql version. Supported versions are:
|mssql-admin-password||The password for the local administrator that will be used as an MSSQL
|mssql-instance-name||The MSSQL instance name||string||mssql|
|mssql-service-username||The username under which the mssql service runs||string||mssql|
|always-on-replica-synchronization||The prefered type of database synchronization on the replicas.
The total maximum number of replicas is 8.
The maximum number of replicas with SYNCHRONOUS_COMMIT is 3(including primary replica).
The maximum number of replicas with ASYNCHRONOUS_COMMIT is 5(including primary replica).
For example, when SYNCHRONOUS_COMMIT is chosen, the first 3 replica
nodes will be configured to SYNCHRONOUS_COMMIT and the rest with
|always-on-listener-name||Always On Listener name.
It must be less than 15 characters, as it is an Active Directory unit
Please fill out the form below for pricing information and for a free trial: