For larger databases (100s of GB), the following additional precautions might ensure adequate migration performance:
Pre-Migration
Deploy your Agile Business Suite model with an empty database. For the sake of these instructions SAMPLEDB represents the Sample Runtime Database in Agile Business Suite and SP the Sample Runtime Database in EAE.
Ensure the SQL Server Database Transaction Logging is set to Simple.
In SQL Enterprise Manager, right-click on the Target database. For example, "SAMPLEDB". Select Properties > Options. Change "Recovery Model:" to Simple instead of Full, this is very important otherwise you will run out of disk space if the database is very large.
Data Migration
Run DBMigrate as described above. This takes some time to complete for a large database and should say either "Successfully completed" or "Successfully completed with warnings." If anything goes wrong check 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 Explorerb 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.
Note: DBMigrate relies on SQL Server's Data Transformation Services. This needs to be installed separately from the SQL Server CDs. Refer to the note during Installation or during the Prerequisite Check in the AB Ready Tool.