|   | ![]() |
|
|
SQL-Programmer 2.2 1 2 3 4 5 6 7 Within your main workspace and from SQL-Explorer and Access Manager, you can access the scripting engine. This allows you to select multiple objects and generate a script file for them. The one difference with the implementation in SQL-Programmer is that the scripting engine runs in the background. This allows you to set up a script generation and then continue working inside SQL-Programmer while the script file is generated. I would have like to see a much more compact file generated though. The scripts that are generated have a considerable amount of white space and added comments that are really not needed.If all of that wasn't enough, there are five more items to touch upon. SQL-Programmer comes with interfaces to the most popular source code control products on the market.
But, it doesn't stop there. You don't need to have a source code control product to take advantage of source code control. This is a feature for those companies/departments where everyone uses SQL-Programmer. It contains the ability to turn on a native check in/ check out for your objects. It maintains this information in two tables within the database. If another developer attempts to modify an object you have checked out, SQL-Programmer prevents this by querying this table. This is seamless to the developers, because anytime an object is opened in an editor, it is automatically checked out. All checked out objects are designated as such within the explorer and can be listed via a report. The developers are also given the option to add comments and store these as a track on the changes that were made. Via a mechanism called batch objects, SQL-Programmer gives developer's the ability to store script fragments, templates and other objects inside a database as nonexecutable objects. Essentially, these are stored within a table on the database. But, the nice thing is that these objects integrate directly into the Access Manager, Reports, and SQL-Explorer. They can be accessed, incorporated, and used just like any other database object. This is a great place to store templates for all of your objects as well as frequently used scripts and script fragments that you don't want to create as object within your databases, but still need them to be accessible. SQL-Programmer would not be complete without an ad hoc SQL module. This is called FreeSQL.
Yes, I know this hurts your eyes. It gets even worse when you start typing SQL into it. Picture a variable which is a light olive green, keywords which are blue, and comments which are green on this background. Definitely not a pretty sight. It took me a little digging to change this background and I'd like to relegate the person who picked this color as the default to spending 15 hours a day in a room that is painted this color while wearing 3D glasses. Since it hurts your eyes as much as mine, here is how you turn it off so that you don;t have to dig around like I did. With the FreeSQL window active, select View | Options. The yellow block toward the bottom that is labeled background should literally scream at you. Simply click the block and you will be presented with a color palette. Pick the color you want and answer yes/ok to the numerous prompts. You now have no more bright yellow. |
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.