← Back to X_TRADER® Help Library

Historical Fill Server Documentation

Create or Upgrade Central Database

By default the HFS installs files in the <root drive>:tthistoricalfillserver directory and includes a file named HFSDB.bat.Typically, the database you create resides on the machine associated with the server name entered to execute the HFSDB.bat file.

To run the batch file to create or upgrade the database:

  1. From the Windows Start menu, click Run. The Run window displays.
  2. In the Open field, type cmd.

  3. Click the OK button. A command prompt opens.

  4. In the command prompt, enter the location of the HFSDB.bat batch file and pressEnter. For example, type: cd <rootdrive>:tthistoricalfillserver
  5. Enter HFSDB.bat and the server name of the machine on which you have the database and press Enter.

    For example, type: HFSDB.bat CHI100876.

    If you would like to use an alternate database name or user, refer to the Renaming the Database, Username, and Password section below.

    Note: Messages will display in the command prompt indicating that a database named TT_CENTRAL_DB has been created or upgraded.

    Failure to provide the command line argument (as noted above), causes the script to output an error message indicating that an SQL Server name is required.

    Note: You also receive a warning if your SQL Server (local) is either not installed or is not running at the time of installation.

    You have successfully run the batch file.

    Note: If you are creating a new database and the SQL Server has complex password requirements, the batch file used to create the tables will need to be updated before it is run. Specifically, locate the file called HFSDB.bat in the tthistoricalfillserver folder. Edit the file and locate the following line (which is just over half-way through the file):

    osql -E -S%1 -d "master" -Q "exec sp_addlogin N'RiskAdmin', N'12345678', N'%DBName%', N'us_english' " -n >> hfs_install_db_04.out

    Change the 12345678 password portion of the line to a password that meets the password complexity requirements for your database.

    The batch file does not handle password updates on existing users; the SQL Server application (e.g. SQL Server Management studio) must be used.