Database Extraction Tool
Overview
The purpose of the Database Extraction tool is to create a new database that contains only specific, required information. This database is smaller and therefore easier to manage. Performance is better than the original.
The new database is created from data extracted from an existing Govern database. It contains the same schema as the original database but the data, property records, Profiles, and functions it contains are restricted to one or more modules, one or more years, and a saved dataset. A saved dataset is a predefined set of records that is created in Govern. Note that all the dependencies that are required for those records are also copied.
An extracted database can be useful in troubleshooting, testing, or training. For example, you may want to create a demo on a laptop computer and need only the data from the previous assessment year. You may want to test a new tax rate and need all the tax and CAMA tables but only specific property records. You may need to do some troubleshooting and want to send a portion of the database to a team working in a remote office.
The new extracted database is used in a deployment, as any other standalone Govern database. Once it is created, it is independent of the original database. It needs to be updated and maintained separately. It is designed for temporary use. Whenever you run the Database Extraction on it, the existing data are deleted and replaced with the selected data from the source database.
The new extracted database is:
- Reduced in size
- Easily transferred to another computer or to another team
- Contains only the data essential to a specific purpose
- Provides better performance due to the small size
The database extraction tool:
- Reduces the time required for creating a new database
- Reduces downtime over a full backup and restore
- The source database operates independently of the extracted database.
Read More... For a comprehensive pdf of this page, see the following document: Access to the: The Database Extraction Tool: A full list of all the tables that are copied can be viewed in the following file: MSGDatabaseStructMods.xml This file is accessed from the SystemFiles folder for your deployment. To create an extracted database from an existing database: Once the database extraction process is complete, the newly extracted database is ready to use. You can make it available to a remote team via ftp, or open it in any deployment, with the correct version number. You are ready to begin testing, troubleshooting, or training. The extracted database is the same as the source database. Once the procedure is complete, the extracted database is a standalone database that can be used as any other Govern database. You can run ad database verification, update the database or make modifications as you would to any other database. 103-ut-010 Documentation
103-UT-110-DatabaseExtraction.pdfPrerequisites
This can be any SQL database, such as an empty database, or a database from any Govern version.
All existing data and tables are removed from the destination databae at the beginning of the process.Recommendations
For details on running a database verification, refer to the GNA documentation.
The process clears all data from the destination database.
For example, the A/R records that are associated with the tax records in the dataset are copied. These include the property control records that are associated with the CAMA records.The only records extracted are those in the saved dataset and the dependencies of those records.References
Extracting a Database
Data from all tables for the range of years, selected in the From and To drop-down lists for the selected Saved Dataset.
All Profiles and user forms required for the records in the dataset, as well as all dependencies, are copied.
Tip: If you hover your mouse over the option for the parameter, a tooltip listing all the tables appears.
A confirmation message appears.
This message warns you that the process deletes all data in the destination database.Using the New Database
Maintaining the Extracted Database
There is no synchronization between the source and destination databases, once the process is complete.