|
|
|
|
|
One of the best features this product has
is an error window. When you have an error in your batch, the error window will
appear with a reference to the line number(s) in the script and the associated error
message. Simply double clicking on the error will position your cursor on that
line. I'm sure a few people have seen the error on line 1052 type of message and
then been forced to count 1052 lines down from the top of the script to try and find the
error. Just hope no one walks in or the phone doesn't ring while you do this.
I have had to do this and it wasn't fun. During this time was my first introduction
to RapidSQL. I was putting together a set of huge scripts for Sybase that were in
excess of 6000 lines each. The only thing that could accommodate that was good old
isql and vi is definitely not a user friendly editor. RapidSQL easily accommodated
the scripts I was building. The cursor is automatically positioned at the line of
the first error in the window. The first script was painstakingly constructed over
the space of two weeks. When we brought in RapidSQL, the next script which as even
larger than the first took just a day and a half to finish. This amount of time
savings was worth the entire purchase price and then some. Even with the error
window, it would have been nice to see errors get identified before sending the SQL off to
the database. Granted, errors involving object names and such can not be
detected. But simple errors where parenthesis do not match, keywords are misspelled,
arguments are not defined for a function, basic SQL syntax is violated, etc. can be
detected by the tool itself before ever issuing the SQL to the database. (It can't
hurt to ask for more features since Embarcadero has supplied almost every one I have
requested in the past.)
Along with the error window, color coded syntax, object browser, search engine, and email capability, there are still three more very powerful, time saving features. There is a window that can be opened or closed that contains a list of favorite scripts. RapidSQL already comes packaged with quite a few for each platform to return basic object information. To these, you can add any others you want. These can be any text file you wish. I have added in text files for script headers, triggers and stored procedure templates, and small blocks of code I frequently use. You can then insert these directly into the script you are currently working on. In addition to the ones you can add, RapidSQL already comes packaged with a wide array of scripts for each the three supported DBMSes.
|
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.
