This release has an initial version number of 8.3.9.
If an existing version of Precision Bridge is installed, this version will be installed alongside it.
Users upgrading to 8.3 from versions earlier than 8.0 will need to request a new licence from Precision Bridge.
Listed below are the enhancements included in this release:
List of Enhancements
Support for Databricks as a Target
The data warehouse platform Databricks has been added as a target platform. This is primarily to support the Archiving and Replication use cases. Full transform and mapping capability is supported, as it is for all other database targets. The following additional functions are supported for Databricks:
1. JDBC Connection to a Databricks instance
See the following articles for details on how to configure the connection:
Configuring Access to a Databricks Server
Configuring a Databricks Server Connection
2. Generation of tables mirroring the structure of the source server
This supports the same source servers as other database targets. At the same time, Precision Bridge mappings can be generated to perform the migration. This utility makes it a very fast process to set up a basic archiving/replication project. See this article for more details on the Table Generation Utility:
The Precision Bridge Archiving Wizard
3. Migration of attachments into Databricks or a file folder or an S3 bucket
For attachment migration into Databricks, a maximum size of 10MB is supported. There is no fixed limit for migration into S3 buckets or file systems. All attachment options available to other database target platforms are supported by Databricks. See these articles for more information:
Attachment Migration Behaviour
Migrating Attachments from ServiceNow to an Archive Database
4. Deletion of source records once migrated
Safety checks will prevent deletion of the record unless it is confirmed as existing in the target Databricks server. This is supported for ServiceNow, Remedy and database source platforms currently. See here for more information:
5. Deletion of target records
You can configure Precision Bridge to delete any records on the target that have been deleted on the source. See here for more information:
Notice of Support Termination
With the release of Precision Bridge 8.3, support was withdrawn for Precision Bridge 7.2 and below. Customers still using these versions are advised to upgrade to a later release as soon as possible.
Currently, supported versions of Precision Bridge are: 8.3, 8.2, 8.1, 8.0, 7.4 and 7.3.
Support is planned to be withdrawn from versions 7.4 and 7.3 in December 2025.
Advice To Users Upgrading from Precision Bridge 7.0 or earlier
The Use Server ID's Key Mapping option was removed from Precision Bridge 7.1. If this Key mapping option has been used in a project built with Precision Bridge 7.0 (or earlier), the Key Mapping option will default to 'No Key Mappings' when opened in Precision Bridge 7.1 or later.
Note that none of the Precision Bridge Templates used this option in earlier or current versions of Precision Bridge. If you have projects that use this option, be sure to select an alternative key mapping option to use (such as by selecting Key Field Mappings) before executing the project with Precision Bridge 8.1. Failure to do this may result in duplicate records being created if the project is run a second time to update existing records.
Other than the above, projects built using Precision Bridge 7.0 and above will still work with Precision Bridge 8.1 with no changes required.
Comments
0 comments
Please sign in to leave a comment.