DBpulse FAQ
What databases does DBpulse work on?
DBpulse works with all versions of Microsoft SQL Server as well as Sybase 12+.
What Operating Systems does DBpulse work on?
DBpulse works with Windows, Linux, and Solaris. For Windows, it runs on 7, 2008, and 2012. For Linux, it runs on CentOS/RedHat Enterprise Linux 5, 6, and 7. For Solaris, it runs on 8, 9, and 10 SPARC.
Where should I install DBpulse?
Typically DBpulse is installed on the database server itself. That way, all traffic to the database can be seen. However, for diagnostic purposes, DBpulse can be installed on a client machine such as a Web Server, Application Server, or desktop PC. Lastly, DBpulse can be installed on a machine that has access to all packets destined for the database server (e.g. a port on a hub or a span/mirror port on a switch).
Can DBpulse capture local SQL queries (loopback connections)?
Generally no. The exception is Linux which does support packet capture on the loopback interface. Most TCP loopback devices are special optimizations that don't have a well defined API.
How is DBpulse licensed?
The Evaluation license is free. The limitation is that DBpulse will stop after processing 2,000,000 packets. The Registered license has a fee. The limitation is that the software is locked to an IP address (where it's installed, not necessarily the database server) and hostname combination for a period of time (usually 1 year). Thus, if the software is moved to another machine or the machine's IP address or hostname changes, a new license is required.
Is DBpulse secure? Can engineers use DBpulse to break into the database?
DBpulse is secure in the sense that it can only sniff packets for a particular host/port combination (it's programatically prevented from sniffing ports below 1024). It is totally passive and cannot interrupt the flow of packets in any way. However, data in the network packets may include plaintext passwords. Using DBpulse, an engineer may be able to capture plaintext passwords; however, an engineer could use many different tools to capture those passwords. At no time does DBpulse manipulate or store password information.
If I run DBpulse on the database server, what's the overhead involved?
DBpulse is very efficient. Most of the time, it's just waiting for packets to arrive at the network interface. On a moderately busy database server, DBpulse will use less than 5% of the CPU.
Will Foresight engineers help me tune a particular query.
Yes. You can have Foresight engineers help you tune queries on a time and materials basis, or in conjunction with performance management services.