Data Grid Text Migration application
The Data Grid Text Migration application is an application you can use to migrate your long text fields from SQL to Data Grid.
Note: Once you start a migration job, the results are permanent. You can't delete a migration job once it has been started.
There are several considerations you should be aware of before and during text migration.
Before running text migration
Before running a text migration job, review the following considerations:
- If your workspace has any custom solutions or third-party applications built on the long text field you're migrating, update them to use the Export API to read long text and metadata fields.
- If you have any custom data which relies on the long text field you're migrating being stored in the SQL Document table, contact Relativity Support to discuss alternative solutions before migration.
- Data Grid only supports the IS SET and IS NOT SET operators. If your workspace uses other operators to query on long text fields, you will need to perform a similar query using dtSearch.
- Mass operations are not supported with Data Grid. If you need to populate a long text field stored in Data Grid, perform an OCR and select the Data Grid field as the destination field.
- Once the text migration job completes, the only index search available for the migrated field is dtSearch. Keyword search is not supported. Data Grid supports all features of dtSearch. If you do not have an active dtSearch index in your workspace, you will need to build one. You can include a combination of Data Grid and SQL fields in your saved search. For more information, see Running the Breakage Report.
For a list of supported and unsupported Data Grid text functionality, see Supported and unsupported functionality.
Running text migration
Review the following considerations for running a text migration job:
- The Data Grid Text Migration application runs at the instance level. However, you must install the application to at least one workspace.
- If you have index build in progress (like dtSearch or Analytics), let the index build finish before starting a migration job.
- If you have a mass replace in progress, let the operation finish before starting a migration job.
- We recommend running a migration job in off hours. However, it is not required.
- You can only have one job in progress at a time. If you start a new text migration job while another is in progress, the new job is added to the queue.
- Although the application automatically deletes the column in SQL, you are still required to reclaim the space that was taken up by your long text document field in SQL.
Once you enable a long text field's access to Data Grid, you can't disable it, so it's important to understand the benefits and limitations of storing text in Data Grid.
|Supported extracted text functionality||Currently unsupported functionality|
The Data Grid Text Migration application runs at the instance level. However, you must install the application to at least one workspace.
To install the Data Grid Text Migration application:
- Navigate to the Application Library tab.
- Select Data Grid Text Migration from the list of Relativity applications.
- Next to Workspaces Installed, click Install.
- Next to Workspaces, click , and then select a workspace.
- Click Ok.
- Click Save.
Once you install the Data Grid Text Migration application, the Text Migration Jobs tab appears under the Data Grid tab.
Installing the text migration agents
After you install the Text Migration application, you must install one Data Grid Migration Manager agent and at least one Data Grid Migration Worker agent to your environment. We recommend installing two Data Grid Migration Worker agents.
Note: You can run the Breakage Report without installing the text migration agents. We recommend running the Breakage Report and resolving any issues before running a migration job.
For more information on installing agents, see
Running text migration
Once you install the Data Grid Text Migration application and configure your migration agents, you can run text migration. See Running text migration.