SQL Server Magazine

Sylvain Faust's SQL-Programmer, a third-party, general-purpose SQL Server utility development tool, provides cross-platform capability for any combination of SQL Server, Sybase Adaptive Server, and Oracle. Sylvain Faust's latest release, SQL-Programmer IX, and its use with SQL Server 7.0 are the focus of this review.

SQL-Programmer consists of five basic modules: SQL-Explorer for browsing databases, Access Manager for quick access to database objects, SQL-Documenter Report Interface for documenting objects, SQL Scripter for scripting objects through a script interface, and Free SQL! for querying. You can invoke all modules from SQL-Programmer's button bar.

SQL-Explorer lets you explore a tree view of databases and their objects, similar to the view in SQL Server's Enterprise Manager. Unlike Enterprise Manager, SQL-Explorer's tree view is developer-oriented and it doesn't include as many administrative nodes (such as SQL Agent); it adds nodes only for Transact SQL (T-SQL) developers. You can find nodes for triggers and indexes more easily in SQL-Explorer than in Enterprise Manager. SQL-Explorer's Show Code mode lets you view the T-SQL code for each object in the right-hand pane of the Explorer interface, with color-syntax highlighting. You don't have to open an object or view its properties to see the code. The Show Code feature also extends to logins; you can select a login and see the login's script immediately. Another useful feature is the ability to drag and drop objects, including tables, from one database to another. (As with Enterprise Manager, SQL-Programmer can occasionally go into a Not responding mode.)

Access Manager is an alternative way to select database objects more quickly than through SQL- Explorer. The Access Manager interface lets you choose an object by selecting the database and the object type. You can click a button on the lower button bar to perform any of the same features you can invoke somewhat more laboriously in SQL-Explorer. You can also use standard Windows keystrokes to copy and paste objects from one database to another. And, you can click the Edit button to view the contents of a table. The Access Manager is an example of less is more—a simple design that is more efficient than the flashier drill-down Explorer design.

The SQL-Documenter utility is a valuable feature for creating reports about your database. This kind of utility doesn't come with the default SQL Server toolset. You can use SQL-Documenter to document programmable objects in a database. The report format is appropriate for printing, binding, formatting information, and keeping source code in a readable fashion.

SQL Scripter lets you extract object scripts for backup. SQL Scripter doesn't have as many options as Enterprise Manager's Generate SQL Scripts dialog box; however, it can produce table scripts without square brackets to make it easier to spot T-SQL keywords used as column names. Also, SQL Scripter doesn't script ordinary column defaults with constraint names as Enterprise Manager's scripting utility does (an annoying aspect of Enterprise Manager).

Free SQL! is a query utility that contains some of the SQL Server Query Analyzer's features. Free SQL! is a quick way to send code to the server and edit batch objects.

Search Utility
SQL-Programmer and SQL-Explorer can access a search utility, which you can invoke from each application's Edit and Find menu, as Screen 1, page 52, shows. You can search for text strings across all objects in a database. The return dialog box lets you select and edit an object. However, this search utility doesn't include a companion replace function.

Source Control and Batch Objects
SQL-Programmer comes with two additional Access Manager features. One is a proprietary source-code control system, which keeps its data in the SQL_Programmer_In_Out table. The source-code control system lets you check objects in and out and record their histories in the database. In addition, SQL-Programmer can indirectly interface with other source-code control systems, including Visual SourceSafe.

The other Access Manager feature lets you create and save T-SQL code as batch objects in your database. The Sylvain Faust batch object can contain more than one batch of T-SQL code. (A T-SQL batch can contain many T-SQL statements, and a Sylvain Faust batch object can store many T-SQL batches.)

Stored-Procedure Editor
You can edit a stored procedure from either SQL-Explorer or Access Manager. To edit a stored procedure in SQL-Explorer, right-click the stored procedure and choose Edit. Screen 2 shows the result. In the Virtual SQL Editor, you can enable the debugger toolbar. The stored-procedure editor has many features besides editing and debugging. In addition to editing a stored procedure, you can set up a test environment by pre-appending code in the Prologue tab and appending code to the Epilogue tab. The editor also has tabs for arguments, results, privileges, and dependencies. It has an activity log, which records activity about the object and stores it in the SQL_Programmer_History table of the database. Then, if you save your work as a SQL-Programmer Development Window (SPDW) file, you can save and restore work in progress, along with the arguments, prologue, and epilogue for a given stored procedure. The Virtual SQL Editor also lets you save specified test cases on disk.

You can also retrieve statistics and showplan data from a Virtual SQL Editor's dialog box. But the Virtual SQL Editor's graphical display doesn't show all the information you can get from the SQL Server Query Analyzer's estimated execution plan.

   Prev. page   [1] 2     next page