The original Rate & Boundary Import was done using native Dexterity code and local c-tree temporary tables. This import could take a substantial amount of time particularly when using the Zip+4 Option. This prompted us to create the SQL Optimized Import to minimize the time required for this process.

The SQL Optimized Import¹⁾ starts out by using the Transact SQL BULK INSERT command to quickly read some of the larger files included in the Rate & Boundary Database. In order for BULK INSERT to function properly:

• The Rate & Boundary Import must be run on the SQL Server itself.
• The Rate & Boundary Database must be saved to a local drive on the SQL Server machine.
• The user running the import must be assigned the bulkadmin Server Role for the SQL Server.

IMPORTANT: If BULK INSERT fails, the Rate & Boundary Database files will be read in the traditional (and slower) way. Failure of the BULK INSERT process will notslow down the many other import process that have been optimized.

Although maintaining two versions will be extra work, we beleive it will be a great way for us to catch errors in the import process. The Non-Optimized Import also provides our users with an alternative way to perform the Rate & Boundary Import should the SQL Optimized Import fail for any reason.

Modifications