

To run a text migration job, complete the following steps:
Identify the workspace(s) you want to migrate. Be sure to review the special considerations for text migration as well as the list of supported and unsupported functionality for Data Grid. For more information, see Considerations.
Identify which long text field(s) you want to migrate. You can migrate up to three fields per migration job.
To create a text migration job, complete the following:
Note: You can migrate up to three fields per job.
To run the Breakage Report, click Breakage Report from the text migration console. The Breakage Report provides a list of all views, saved searches, indexes, and custom objects that will no longer function once you migrate SQL text to Data Grid. We recommend resolving these issues before running a migration job.
One of the primary functions of the Breakage Report is to identify areas where any of the objects above are tied to a keyword search or using keyword search specific functions like Contains or Does Not Contain. Most of the issues identified can be resolved by modifying the object to use an active dtSearch index.
The Breakage Report contains the following columns:
Most of the issues identified by the breakage report can be resolved by modifying the object to use an active dtSearch index. To create or activate a dtSearch index, see Creating a dtSearch index.
Note: Ensure all fields you want to search on are included in the searchable set for the dtSearch index. You can include a combination of Data Grid and SQL fields in your saved search.
The Data Grid Text Migration application includes logical to automatically fix active dtSearch indexes using the <all documents in workspace> searchable set. This logic only applies if the fields being migrated have the Include in Text Index field set to Yes.
The Data Grid Text Migration application creates a saved search called SS_TextMigration_[JobName] which contains all fields where Include in Text Index is set to Yes. It also creates a new dtSearch index called Migration_[existing dtSearch index name] which uses this new saved search. Once text migration completes, navigate to the old dtSearch index and click Swap Index. Select Migration_[existing dtSearch index name] as the replacement index.
Use the results of the breakage report to help you resolve index or field-level search issues that affect saved searches and views
Note: We recommend copying saved searches prior to making edits.
Data Grid only supports the IS SET and IS NOT SET operators. If your field-level search uses another operator, you need to convert the search as follows:
Operator | Example search | Conversion |
---|---|---|
is | Jane has a broken search | "Jane has a broken search" |
is not | Jane has a broken search | NOT "Jane has a broken search" |
is set | Supported operator | No modification required |
is not set | Supported operator | No modification required |
is less than | N/A | N/A |
is greater than | N/A | N/A |
is less than or equal to | N/A | N/A |
is greater than or equal to | N/A | N/A |
is like | Jane has a broken search | *Jane has a broken search* |
is not like | Jane has a broken search | NOT *Jane has a broken search* |
begins with | Jane has a broken search | Paul* |
does not begin with | Jane has a broken search | NOT Paul* |
ends with | Jane has a broken search | *broken search |
does not end with | Jane has a broken search | NOT *broken search |
contains | Jane has a broken search | *Jane has a broken search* |
does not contain | Jane has a broken search | NOT *Jane has a broken search* |
Once you've resolved or taken note of any items in the breakage report, click Start Job to start the text migration job. If another text migration job is already in progress, the new job is added to the queue and begins as soon as any running or pending jobs complete
The job displays one of the following statuses which you can use to monitor the state of your migration:
The Migration Job Details table shows the progress of each workspace in the migration job. This table refreshes every two seconds. Once the job completes or completes with errors, you can filter the table.
The table contains the following columns:
After a successful migration, the application runs a verification step to ensure all documents migrated from SQL to Data Grid. Then, the application drops the SQL column, permanently deleting the migrated text from SQL.
Run the Data Grid Migration Error Report from the Text Migration Reports tab to view migration errors. To run this report, click Run. Click the drop-down to toggle between Field Level Errors and Document Level Errors. Once you've resolved any errors, return to the migration job and click Retry. The job status returns to In Progress and any errors on the fields marked with errors are reset.
The following results populate the bottom of the window:
The following results populate the bottom of the window:
On this page
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!