HAT Connection Timeout on large Tracking Databases

Recently while analysing a large (>15GB) tracking database on a BTS2004 install, my trusty friend HAT was coughing and spluttering – and moaning about timeouts.

Here’s how to increase the timeout value :

(from a MSDN arcticle)

1. Click Start, click Run, type regedit,
   and then click OK.

2. In Registry Editor, locate and then click the following
   subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0

3. If there is a Tracking subkey, go to step 6.

4. To create a Tracking subkey, on the Edit menu,
   point to New, and then click Key.

5. Type Tracking, and then press ENTER.

6. Locate and then click the following subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0\Tracking

7. On the Edit menu, point to New, and then
   click DWORD Value.

8. Type ConnectionTimeout, and then press ENTER.

9. Right-click ConnectionTimeout, and then click Modify.

10. In the Edit DWORD Value dialog box, click Decimal.

11. In the Value data box, type the value in seconds
    that you want to set for the query timeout value, and then click OK.

12. On the File menu, click Exit.

*** NOTE: the timeout value I’ve noticed only works with a value up to 30000. Any
higher causes this value to be igorned. (From what I’ve noticed) ****