BTS Blade part two setup and installation

So you want to get the BTS datablade running on a database? Well hereis a step by step Quick Reference to get your database ready to use theBTS Datablade.

First you need to register the BTS blade in your database,this is done with the following method:

Next you need to create an external space for your BTSindex. This is accomplished by the following method:

Next you need to set up your instance so that the BTSVirtualProcessor is created. This is done by adding the following to the$ONCONFIG file:

VPCLASSbts,noyield,num=1

Please note that at this point you have two options to start your btsVP, the first is to cycle the instance (ie, onmode -ky folllowed byoninit), the second is via the onmode -p command (ie. onmode -p +1 bts)

Finally you need to create an index using the bts accessmethod. Below is an example of the code.

And now just to validate that the BTS blade is now up an running, let'srun quick test. We'll run the following query:

SELECT company FROM customer WHEREbts_contains(company, '%all');

And so now you should have the BTS set up and ready to run.

In our final Blog on the BTS we will go over some performance tuning,and how to troubleshoot some issues.

Backups of external spaces are handled by traditional OS means. The
instance has no control over external spaces, and as such cannot
back them up. In order to do a fully safe backup of the BTS
external space, you should also run:

Beginning with IDS 11.50xC3, we included a new feature to allow BTS
indexes to be built in a SmartBlob space, while maintaining
backward compatibility with the extspace option. This new BTS
release can be used in HDR and Mach 11 environments, and supports
updatable secondaries. The BTS version was updated to v2.00.

In order to register BTS 2.00, the server needs an additional
setting -- the onconfig variable: SBSPACENAME must be set to an
existing SmartBlob space in order to be configured with a logged
default SmartBlob space. This addtional configuration requirment is
omitted in early documentation and release notes.