The data report is summarized, displays SQL Server environment information, and supports an unlimited number of server connections.
Typically, linked servers are used to handle distributed queries, and the rowset request may be in the form of executing a query against the provider or opening a base table from the provider. SQL Stripes supports the concept of linked servers, which enables the DBA to configure SQL Stripes to communicate with one SQL Server using another.
Some features of linked servers are not supported in SQL Stripes. For instance, SQL-DMO functions are not supported, and the specified linked server must be a SQL Server, otherwise monitoring data is not collected.
SQL Stripes also supports remote connectivity via Microsoft Terminal Services, pcAnywhere, or VNC.
Key features include:
- Integration with SQL Query Analyzer.
- Integration with SQL Profiler.
- Integration to Enterprise Manager.
- Built-in object viewer (tables, views, etc.).
- Dynamic setup screen.
- Automated startup.
- Auto start command line options.
- Linked servers support (allowing you to communicate with one SQL Server using another).
- Most displayed data can be exported to Excel/XML.
- Multiple object search.
Installation and Configuration
As mentioned in the features section, SQL Stripes can be configured for high-level monitoring of hard disk space and extended server information, and has the ability to start and stop SQL Server services and essential components, such as SQL Query Analyzer, SQL Profiler and Enterprise Manager. SQL Stripes can also be configured for low-level monitoring such as analyzing various SQL Server databases and their objects, with extended server and database information available via e-mail, and audio or visual alerts.
SQL Stripes uses few resources and can be installed on a workstation to monitor a SQL Server farm. The installation process is straight-forward and user-friendly, with screen pop-up and self-explanatory messages.
After installation, the following message appears:
IMPORTANT: In order to run smoothly, the user must have MDAC version 2.7 or above installed. You can download the latest MDAC Package from Microsoft as specified above.
SQL Stripes is a single component application that can be installed on any machine. It connects using the default authentication method familiar with SQL Servers, such as “Windows only” or “mixed-mode.” Either way, you configure the application to connect to a SQL Server.
As a DBA, you can set SQL Stripes as a service to start when the OS is started. A confirmation is displayed with a message: “Service Added: SQL Stripes will load next time when you start your machine.” You can also remove the feature if you want to load SQL Stripes at your convenience.
Below are screen shots of the SQL Stripes configuration window, which appears when the product is installed successfully on a workstation. The initial configuration is required to add the SQL Servers to monitor:
Enter the name of the SQL Server instance, which is recognized as an ID in SQL Stripes, the IP Address, and the port number listened by that SQL Server. The default port numbers for a TCP/IP protocol is 1433. Refer to the SQL Server network utility for the port number for your server. Set the Connection Protocol to either TCP/IP or Named-pipes, otherwise SQL Stripes uses “Last Used” as a default. You can define any notes with regard to that SQL Server you want to remember, which is helpful if you have many SQL Servers to monitor. When the AutoStart mode is specified, SQL Stripes connects and monitors the specified server. Lastly, click the “OK” or “Apply” button to save the configuration.