This documentation is archived and is not being maintained.

Data Warehouse Sizing Considerations

Speech Server 2007

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The Business Intelligence Tools (BIT) in Speech Server are samples that illustrate how to build a data warehouse of large volumes of Speech Server data and Online Analytical Processing (OLAP) cubes for reporting on the data.

  • Ensure that an appropriate amount of disk space for the TempDB database exists before executing BIT Package B. In general, you need twice the current database size for TempDB during the migration process. However, when the migration is complete, you can reduce the size of TempDB to fit normal business execution needs.
  • Ensure that an appropriate amount of disk space for the destination database log file exists before executing BIT Package B. In general, you need half of the current database size for the log file during the migration process. However, when the migration is complete, you can reduce the size of the log file to fit normal business execution needs.
  • Ensure that an appropriate amount of disk space for the destination database file exists before running BIT Package B. In general, you need 150 percent of the size of the current database.
  • For scenarios where migrations are run on a regular basis, if new data is incrementally added to the source database between each migration, the migration time increases according to the magnitude of the existing old data in the source database. Removing old data from the source database on a regular basis is recommended.
  • Parallel BIT PackageB_DM migrations targeted at one database is supported.
Show: