Licensing database changes

Here is the documentation related to deprecate StudioDB to use the Generic Infrastructure DB to storage the licenses

Diagrams

The following models need changes in order to met all the licensing requirements that have been postponed due to the necessity of a new database.

The "License" and "LicenseDownloadData" model will be deleted and replaced with LicenseModel, now LicenseModel will have AvailableActivations and TimesDownloaded

Some important points that must be considered:

  • Validaciones si el usuario tiene o no internet.

  • En la validación online de la licencia, devolver license Model o licenseResponseDTO. Esto es para poderle hacer update a la licencia local

  • Comunicarle a Snow que va a cambiar la implementación de usar todas las lineas en todas las PCs

  • Preguntar a Snow acerca de Start Day, si lo quieren incluir en el fomr de creación de licencia

  • Agregar tabla de Usuario y de AllowedFeatures

  • Guardar fingerprint in DB para la validación

  • Posiblidad de futuros test de retrocompatibilidad

  • Validar createdBycomputer con VBUC

  • Considerar LicenseType como Tag?

  • Revisar el momento en el que se setea LicenseAssemblyVersion ( probablemente es en saveLicenseModel).

  • LicenseAssemblyVersion no debe ir en la base de datos

SQL Scripts

Create new tables in a Database with the Assessment DB Schema

Databases in which this can be run

  • AssessmentDB

  • AssessmentDB-test

Never run this script in another database besides those two. It will erase the PRODUCT table, which already exists in StudioDB, StudioDB-staging and others.

Functionality

Creates the following tables, with their indices, foreign keys and constraints:

  • LicenseProduct

  • LicenseFeature

  • License

  • Customer

  • Feature

  • Product

Script

Here we have the SQL Code for this script and also the .sql file. If you update any of them, please update the other so they are both equal at all times.

Create new tables in a Database with the Studio DB Schema

Databases in which this can be run

  • StudioDB

  • StudioDB-dev

  • StudioDB-staging

Functionality

Moves the data from the StudioLicense table into the following tables :

  • LicenseProduct

  • LicenseFeature

  • License

  • Customer

  • Feature

  • NewProduct (equivalent to Product in the AssessmentDB Schema)

Script

Here we have the SQL Code for this script and also the .sql file. If you update any of them, please update the other so they are both equal at all times.

Move Licensing Data from Old Tables to New Tables

Databases in which this can be run

  • StudioDB

  • StudioDB-dev

  • StudioDB-staging

Functionality

Moves the data from the StudioLicense table into the following tables:

  • LicenseProduct

  • License

  • Customer

  • NewProduct (equivalent to Product in the AssessmentDB Schema)

Script

Here we have the SQL Code for this script and also the .sql file. If you update any of them, please update the other so they are both equal at all times.

Last updated