Summary

This document is targeted to Managed Service Providers (MSPs) of FlexNet Manager Suite and describes how to delete tenants from a multi-tenanted system without disrupting FlexNet Manager Suite online operations. This is a manual process using the attached SQL script and is supported with FlexNet Manager Suite 2019 R1 and later. This process doesn't involve Broker Tools.  

Deleting tenants from FlexNet Manager Suite while databases remain online

To manually delete tenants from a multi-tenanted environment (while databases remain online):

1. Important! Ensure that the following databases have been backed up prior to performing any of the remaining tenant deletion steps:
   

   • Compliance

   • Inventory 

   • Data warehouse
     
     
2. Download the TenantDeletion-Online.sql file that is attached to this Knowledge Base article.
   
   
3. In TenantDeletion-Online.sql file, update the SET @TenantUIDs line to include all the tenant UIDs that need to be removed. If specifying multiple tenant UIDs, separate with a space or comma (or both):
   
   Example 1 (To remove a specific TenantUID, such as 'TAD9HUVMUQ5RHBMY'):
   SET @TenantUIDs = 'TAD9HUVMUQ5RHBMY'
   
   Example 2 (To remove three tenants):
   SET @TenantUIDs = 'TAD9HUVXYX5RHBMY, 3MNAXYX8CTL2R85M, Z2ARXYXRKSVSGQQK'
    
   You can identify the UID for particular tenants by looking at the Tenant table in the compliance database with a query like the following:
   
   SELECT * FROM Tenant
   
4. Note that the deletion process is irreversible. Ensure that you have recent database backups completed from Step 1.
   
   The only option to retrieve the deleted data is to restore the database to a previous point in time. If you are sure you're ready to continue, uncomment the following line in the SQL file by removing the two dashes (comment) at the start of the following line:
   
   --SET @OutputOrExecute = 'Execute'
   
   
5. Ensure that there is sufficient disk space for the transaction log (where "sufficient" varies depending on the amount of data). If there is not enough space, the SQL script stops with an error such as: 
   
   
   The transaction log for database 'FNMSCompliance' is full due to 'ACTIVE_TRANSACTION'.
   
   
6. Execute the resulting SQL statement against each of the following databases before the next reconciliation starts so that the tenant is not automatically recreated:
   • Compliance
   • Data warehouse
   • Inventory

Deleting data for a tenant may take some time (proportional to the amount of data to be deleted).