Data migration

Presentation of data

The eRegulations Data is stored in several SQL Server Database instances and Hard Disk.

We are listing below each of them and also the persistence location :

  1. Country specific data, persisted in the SQL Server 2012 (30-dbe-CountryName) holds the following type of data:
    • procedures repository
    • requirements repository
    • laws repository
    • contact repository
    • translation of all these data
    • country specific parameters: cost variables, etc
    • public site related info like: procedures menu tree, feedback
    • media files references :holds the name of the files used throughout the system
  2. User accounts data, persisted in SQL Server 2008 in an instance (00-dbe-Global) centralizing the user authentication & authorization information
  3. Consistency review data, persisted in the SQL Server 2008 in an instance (00-dbe-Consitency) centralizing the information for several systems located on the same server:
    • consistency review tickets & comments
    • consistency status of steps
  4. System usage statistics, persisted in the SQL Server 2008 in an instance (00-dbe-Statistics) holding the statistics for several systems located on the same server
  5. Media files, persisted on the HardDisk (Media folder) containing all the physical files in three folders: media, upload, ftp
  6. Public site content, persisted on the HardDisk (folder Config & content) being present within the public web application in the above mentioned folders. They contain:
    • config - the home page information saved in json format, a file for each language of the system
    • content - holds the styles (css), images of the public site. we keep here all the personalization of the site esthetic

Migration transport packages

For migrating the data, we will use different packaging strategy to correctly apply to the specificity of each type of data.

  • Country specific data - we will produce a file holding a full backup of the current database instance with the SQL Server tools. It will be labeled: 30-dbe-CountryName.bak.zip
  • User accounts data, Consistency review data, System usage statistics - for each of the database we will produce a script file listing INSERTs statements for the data. They will be packaged in an archive labeled: 00-dbe-CentralData.sql.zip
    Inside you will find 3 script files, one for each database instance: 00-dbe-Global.sql, 00-dbe-Consistency.sql, 00-dbe-Statistics.sql
  • Media files - we will package the "Media, upload, ftp" folders content in an archive, labeled: Media.zip
  • Public site content - we will package the 2 folders "Config" and "content" in an archive labeled: PublicSite.zip

Migration procedures on local server

Here below the procedure to be followed in order to extract the data from the migration packages into the correspondent persistence locations on the local server. Please proceed in the indicated order:

1. Central Data:

  • extract the archive 00-dbe-CentralData.sql.zip in a findable place
  • execute the script 00-dbe-global.sql in the context of the current 00-dbe-Global database instance, already present
  • execute the script 00-dbe-consitency.sql in the context of the current 00-dbe-Consistency database instance, already present
  • execute the script 00-dbe-statistics.sql in the context of the current 00-dbe-Statistics database instance, already present

2. Country Data:

  • extract the 30-dbe-CountryName.bak.zip in a findable place
  • restore the country database using the 30-dbe-CountryName.bak backup file

3. Media files:

  • extract the Media.zip in a findable place
  • locate the present eRegulations Admin WebApplication
  • delete the current Media file in the Admin web application root folder of the eRegulations system
  • copy the extracted media, upload, ftp folders into the Admin web application root folder

4. Public site content:

  • extract the PublicSite.zip in a findable place
  • locate the present eRegulations Public WebApplication
  • overwrite the folders content, Config with the folders in the extracted archive

Update the configuration files

Update all the config files to reflect the systemId from the migrated data:

In the case of Nicaragua, SystemId is 23

You will have config files for the following applications:

  • Admin WebApp
  • Public WebApp
  • CRAlerts CLI
  • Statistics CLI

Feedback