Run Package A
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.
BIT Package A is a sample package to illustrate the migration of data in a Speech Server 2004 R2 reports database to a Speech Server tuning database.
BIT Package A can be run with:
Microsoft SQL??Server Business Intelligence Development Studio.
SQL Server Agent service to schedule the run time.
In all cases, Package A must run on the computer holding the target database. It is not possible to run Package A on a remote computer.
BIT Package A migrations can only be made when the collation of the source and target databases are identical. It is not possible to change the collation of the target database after the Speech Server schema is created; however, you can alter the collation of the Speech Server source database.
Configuring the Connection
In all cases, a configuration file must be supplied and located in the same directory as BIT Package A. By default, the BIT Package A installation includes a sample configuration file named PackageA.xml. Open PackageA.xml in a text or XML editor and then edit the values in the connection string so the values apply to the source and target servers and databases in your environment. For example, [insert source server name here] should be replaced with the name of the source server and [insert source database name here] should be replaced with the name of the source database.
Important Security Notice
Storing SQL??Server credentials in the BIT Package A configuration file is a security risk. When possible, BIT Package A users should use Windows Authentication to connect to the SQL??Server database. Windows Authentication is the default and preferred means of connecting to the database.
When SQL??Server credentials are required to connect, users are strongly advised not to store their credentials in the BIT Package A configuration file. If credentials are stored in the configuration file, users should implement appropriate security measures, such as setting the access control list or using the Encrypting File System feature, to prevent unauthorized access to the configuration file.
By default, the remote connection time-out on the source server running SQL??Server is likely set to 600 seconds. This might not be long enough for large migrations or for migrations over a slow network. In such cases, the remote connection time-out on the source server should be disabled by setting the time-out to zero or setting the time-out to a higher value.
Using Business Intelligence Development Studio
Business Intelligence Development Studio offers an environment similar to Microsoft Visual Studio 2005 to run and debug BIT Package A. For more information about using Business Intelligence Development Studio to run BIT Package A, see SQL Server Management Studio and Business Intelligence Development Studio.
Using the DTExec.exe Utility
The following sample command line is for running BIT Package A with DTExec.exe:
DTExec.exe /f PackageA.dtsx /config PackageA.xml [> BITPkgA.log]
You can rename the optional output log file titled BITPkgA.log. This log file is useful for tracking the progress of the migration, including timing issues and errors or exceptions.
DTExec.exe can also be used within batch or script files. For more information about using DTExec.exe, see dtexec.
Using the DTExecUI.exe Utility
While it is possible to use the DTExecUI.exe utility, it is not recommended. For more information about using DTExecUI.exe, see How to: Run a Package Using the .
Using SQL??Server Agent to Schedule the Package
SQL??Server Agent can be used to manage data migrations. Use SQL??Server Management Studio to access the agent and schedule the run time. For more information, see Automating Administrative Tasks (SQL Server Agent).