Database License Issue when having a fail over activity

[Mohammed_Aboela]

we are encountering an issue while performing fail over on the database nodes,

Data source : multi user or single user server license has expired its pilot time period

we are connected to DB listener which have 2 Nodes with always on status.

and when the first node goes down and the second node become active we face the above issue.

and in order to resolve the issue we always need to go back to the primary node [the first one].

any ideas how to avoid this?

[Jeff_Long]

@ rick nicholls  We have a similar issue with our Always On Availability Group where we have to either go back to the original node or apply a new license key to the new node. How do we avoid this? Your Database reference guide says AOAG are supported, but if the license has to be renewed each time there is a failover that does not seem like it is supported.

[Rick_Nicholls]

Licenses are designed to transfer from original node to the secondary node in a Always On Availability Group.  If you are experiencing an issue with having renew your license, please contact your first line of support and they should be able to assist you in diagnosing the problem.  

[Dominique_Pluch]

Hi all,

You might also take in account that the 'hsi' user is not the same in each of the DB as they have not the same ID.

'hsi' user can be set higher at the level of the SQL server instance. Then  the user 'hsi' then become a unique user for the 2 DB.

This has solve the automatic switch for us that become transparent.

Before OnBase 18, we were obliged to switch back to primary or to Recreate DBuser each time a switch was detected ...

With OnBase18 this is solved.

[Ashish_Srivasta]

Hey Dominique,

You mentioned

>>Before OnBase 18, we were obliged to switch back to primary or to Recreate DBuser each time a switch was detected ...

>>With OnBase18 this is solved.

We are on OnBase 18 and using OnBase 18 RecreateDBusersHighSecurity module and we created a database user as db_owner as suggested in the MRG. In this case, will we have to run ReCreate DB User with switching from primary to secondary node in Production or switching from Production to DR in case of DR event. I understand that not everyone understands the high security model in detail and suggest to run ReCreate DB User every time but since you mentioned about it, I thought to get your experienced view on this topic. Please note that DR database is just a copy to Prod at this time and will be refreshed every 15 minutes from Prod to DR.

Kind Regards,

Ashish Srivastava