For large size databases, such as 100s of GB, you should perform the following additional precautionary steps to ensure adequate migration performance:
Pre-database migration
Deploy your AB Suite model with an empty database. You can consider, SAMPLEDB that represents the Sample Runtime Database in AB Suite and SP— the Sample Runtime Database in EAE.
Ensure that the SQL Server Database Transaction Logging is set to Simple.
To set the Transaction Logging to Simple in SQL Enterprise Manager, you should right-click the Target database, for example, SAMPLEDB.
Point to Properties and then select Options. Change Recovery Model: to simple instead of full. This is important else you might run out of disk space if the database is very large.
Data Migration
Run Data Migration Tool.
This takes some time to complete for a large database and prompts you with either Successfully completed or Successfully completed with warnings. For any errors, open the DBMlogs in C:\AB Suite 7.0\data\public\log and search for ERROR. During DBMigrate execution, all Index Views of conditional profiles are automatically dropped and recreated. You do not need to drop and restore all views manually by using appropriate scripts.
To verify the views and data from SQL Query analyzer, perform the following:
Open SQL Query analyzer.
From the menu, point to Tools, Object Browser, select show/hide to ensure that you can see the databases.
In the Object Explorer, expand <database name>/Views. For example, SAMPLEDB database.
All the views are recreated under the <database name>.
Right-click a view and select Select Top 1000 Rows from the context-menu. The migrated data appears in the result window.
Additionally, you can also verify the views and the migrated data from the DBReorg file available at the Data\Public folder.