Introduction
Projects where data is migrated from a source server into a database can make use of some additional functionality in Precision Bridge. Deletion of the Source Record after migration can be supported for some source adaptors, and all adaptors support a very simple wizard-based generation of the database tables and form mappings needed to perform the migration.
Archiving Wizard
This feature is slightly misnamed, as its use is not limited to archiving projects. Any migration that has a database target, where the structure of the data on the source is to be migrated without transformation onto the target can use this feature. The wizard can:
- Create (or update) the tables on the database that will store the migrated data
- Add the mappings to the Precision Bridge project that will perform the migration.
This wizard is enabled if the target is a database, and can be run using the menu item Projects -> Generate -> Generate Archive Targets. To see more information, read the article The Precision Bridge Archiving Wizard
Attachment Handling
Where the target is a database, you have three options on how attachments can be stored:
- Within a database table ( this table can be created using the Project->Generate->Create Attachment Table menu item)
- In a folder on the server (or an accessible network folder)
- In an AWS bucket.
Which method used in your project is specified in the Execution options, under the Attachments tab.
To find out more about migrating attachments when the target server is a database, see this article: Defining Attachment Options
Source Deletions
Source Deletions Complete an Archiving operation by removing the source record once it has been archived to database. Currently, this feature is only available for Service Now -> Database and ServiceNow -> ServiceNow projects.
With source deletions, you can configure safety checks to ensure that records that are cascade deleted are also present on the target before the deletion is allowed. Similarly, you can check that attachments have been migrated.
You can also ensure that no audit records remain related to the deleted record. Particularly useful if storage reduction is the primary reason for Archiving.
To find out more about configuring source deletions, see this article: Configuring Source Deletions
Comments
0 comments
Please sign in to leave a comment.