There are a couple of tuning settings that you should change keep your Counterpoint SQL installation running efficiently. Starting with the SQL server itself, there are a couple of settings that can help.
First, is the memory usage. The default, is a minimum of zero, and a maximum of all memory. It is much better to set these to specific values. Since the operating system should have a couple of gigabytes to work with, I like to set the minimum and maximum a couple gigabytes below the installed memory. So, say given eight gigabytes of RAM, I would set both the minimum and maximum memory to 6,144 (1,024 x 6) megabytes. By setting both the minimum and maximum to the same value, the need for the server to try to dynamically allocate and deallocate memory is alleviated. It can just work on processing the SQL transactions.
The second setting that I try to use, is the SQL priority boost. If you are running a dedicated SQL server, and are not using the same computer for other processing, then definitely set the priority boost. I will give the SQL programs a slight edge on using resources over other processes that run. These other processes would be some of the Windows housekeeping, and background processing.
If you are using your SQL server for other processing, also, then using the SQL priority boost would need to be evaluated. Many times it can be turned on, without significant impact on the other processing that you are doing. Turn it on, and see how it goes. If it does slow your other processing too much, it can be turned off again.
Dave.