Version 3.0.21 (BETA) is now available for download. To download, please use the same link on the product home you used before. Here is what's new and fixed in this build:

1. Hopefully fixed issues with Class Not Registered error in add-on for SQL Server Management Studio and similar for VS Database Team Edition and VS 2005/NET versions
2. Updated Sybase ASE catalog queries to support older versions including 12 and 12.5
3. Updated Sybase ASA catalog queries to support older versions including all versions in 7.0 to 10.0 range
4. Added SQL Reference for DB2 UDB version 9.
5. Fixed issue in the API for "DB2 provider "error
6. Added support for Sybase ASE 12.x ODBC driver
7. Fixed issue with similar schema name and aliases
8. Fixed issue with MySQL and extra-text inserted in front of column names when using active code snippets
9.Documentation fixes and a number of other minor fixes and enhancements.

Last edited by SysOp on Thu Sep 17, 2009 10:52 pm; edited 1 time in total

Mon Nov 19, 2007 1:14 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Version 3.0.23 (BETA) is now available for download. To download, please use the same link on the product home you used before. Here is what's new and fixed in this build and the prior build (note that internal build 3.0.22 was skipped and not released separately)

1. Corrected inconsistent display of table aliases in the WHERE and HAVING clauses.
2. Enhanced code snippets to support variable-column pairs for dynamically-generated UPDATE, SELECT statements. See "Special Cases" topic in the help file for more details and usage instructions.
3. Improved auto-indent for FROM, WHERE, GROUP BY, ORDER BY and HAVING.
4. Fix issue with Notepad target crashing if the target is open while SQL Assistant options are modified.
5. All pre-configured DB2 targets are set by default to use new DB2 SQL Reference (DB2 SQL reference. introduced in 4.0.21).
6. Fix for line wrapping and position of FROM keyword when selecting lots of columns using SQL Assistant's popup appearing after SELECT keyword.
7. Increased default query timeout for ADO.NET connections from 5 seconds to 10 seconds.
8. Added "hack" to prevent "Connection Busy" errors during typing of code while the connection is busy executing some query in background - affects connections shared with the target only.
9. Fix for quoted database names and syntax error occurring when SET QUOTED IDENTIFIER is turned OFF in the target editor and the connection is shared.
10. Enhanced code snippets to support variable-column pairs for dynamically-generated UPDATE, SELECT statements. See "Special Cases" topic in the help file for more details and usage instructions.

Fri Nov 23, 2007 8:24 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Version 3.0.24 (BETA) is now available for download. To download, please use the same link on the product home you used before. Here is what's new and fixed in this build

1. Fixed issue with JOIN candidates. A regression bug introduced in 3.0.23 made SQL Assistant to show JOIN candidates only for the last table referenced in the FROM clause.
2. Improved parsing of subqueries in Oracle targets. Corrected issue with derived tables for which not always correct columns of derived tables where displayed in the top level query.
3. Updated several pre-defined code snippets for DB2 and MySQL.
4. In Procedure Code View for Oracle packages and types a couple of empty line are added automatically to separate package body and package declaration.
5. Fixed issue with occasional table alias concatenation in JOIN clause.
6. Documentation updates.

Wed Nov 28, 2007 1:58 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

The following internal builds haven't been made public. We used them to fix issues reported during the beta testing
3.0.25
3.0.26
3.0.27

The only functional enhancements added in these builds were
-- Automatic quoting of objects and columns whose names match reserved keywords.
-- New error handling method using non-interruptible system tray notification messages and automatic recovery of broken database connections.

Wed Dec 05, 2007 11:01 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Version 3.0 has been released. Thank you all beta participants for your help with the testing and your valuable feedback.

If you actively participated in the testing, you are eligible for a free license with 1-year maintenance and support included. To obtain your free license, email to our sales guys, and as a proof of beta participation, provide a reference to at least 1 post in this forum indicating your input or attach a copy of an email sent to support.

Thu Dec 06, 2007 11:40 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Build 3.0.31 is now available.

Please note that builds 3.0.29 and 3.0.30 were internal and not released separately. Here is a cumulative list of changes in builds 3.0.29 - 3.0.31

Enhancements:
1. Support for temp and non-temp tables in DB2 and MySQL declared using CREATE [TEMPORARY] TABLE statement. Assistance for such table names and their columns is provided in the same SQL block (stored procedure, function, compound statement)

2. Support for non-temp tables in T-SQL declared using CREATE TABLE statement. Assistance for such table names and its columns is provided in the same SQL block

3. Code Structure View now recognizes INSERT..EXEC commands as EXEC not as INSERT making it easier to see nested procedure calls

4. Formatting for SELECT statements with OUTER and FULL joins modified to avoid breaking parts of the JOIN syntax on multiple lines

Fixes:
1. MySQL Query Browser repainting issues after SA closure

2. Assistance for SET command and brackets inserted for certain keyword in T-SQL

3. DB Tools popup menu - images appear in the menu as they appear when SQL Assistant is not used

5. Code snippets with long text – the editor is scrolled automatically after the generated code is inserted so that the caret is visible on the screen and user can continue typing without touching the mouse.

6. Spell checker doesn't understand repeating single quotes within strings, such as "don't" and treats them as string separators

3. Support for MS Access as a back-end database, via direct integration with Access IDE and via ODBC database connection from other SQL editors (for example, you can now run MS Access queries and make data changes from Notepad).

4. Data export to Excel and text files.

5. SQL Code Structure support for CALL statements and other enhancements in the Structure view.

6. DB2 and MySQL – support for FOR NOT FOUND and CURSOR..FOR constructs.

12. Formatting code enhancements – added support for code structures beginning with the same keyword, for example, BEGIN and BEGIN TRY

13. Logical join completion for subqueries - joins between tables referenced in the main query and tables referenced in subqueries.

14. Support for join candidates using matching column names.

15. Improved code auto-indent handling.

16. Reworked and expanded database connection handling. Starting with this version ADO.NET-based and ODBC-based connections can be used with all supported database systems. For ODBC-based connections both DSN and DSN-less connections are now supported.

17. Client-side authentication is now supported for DB2 and Sybase database connections using ADO.NET interfaces.

Please note that builds 3.1.20 and 3.1.21 didn't pas the internal tests and have not been publicly released.

Build 3.1.22 introduces several improvements and new features:

1. Full column aliasing is not used in simple statements referencing to a single table or view without an alias.

2. Increased command timeouts for intercepted connections from 10 to 60 seconds to make it easier to work with SQL Assistant in very large or very slow databases and network connections.

3. Fixed issue with snippets not working correctly in SQL Query Analyzer. The cursor is now properly set to the position positioned at the marker

4. Simple code snippets like sm, ss and similar have been enhanced with macro variables making their use more efficient.

5. Four new macro-variables have been added for vertical column and parameter lists. Note that positions of commas depend on where they are specified in the code snippet, for example, if you use ",$COLUMNS_V$", commas will be inserted in front of column names. If you use "$COLUMNS_V$," commas will be inserted after column names. Other 3 new snippets are $COLUMNS+TYPES_V$, $ARGS_V$, and $ARGS+TYPES_V$

6. Visual appearance of SQL Reference Index has been updated and it now works more like a treeview making easier to navigate the reference

7. Fixed issue with code formatting confusing LEFT and RIGHT functions with LEFT and RIGHT JOINS

Mon Mar 10, 2008 2:34 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6509

Build 3.1.24 has been released as an emergency bug fix after it has been reported that SQL Assistant build 3.1.22 crashes certain targets when it is active during DDL command typing, for example, after CREATE and DROP keywords.

This build also includes changes from internal build 3.1.23 containing a fix for issue with column names in Oracle matching keywords. In that case column name is pasted in lower case and enclosed in double quotes making column name case sensitive. An attempt to execute such query results in unknown column name error.
[/b]

Please note that builds 3.5.12 to 3.5.20 have not been publicly released.

Build 3.5.21 contains several improvements and bug fixes:

1. Introduced new graphical menus with icons. Menu appearance may different on different platforms and in different target editors and should be generally consistent with appearance of menus in the target editor

3. Fixed crashing in MS Access when entering subqueries referring to objects in the main query.

4. Fixed issue in T-SQL code formatting for SET statements referring to subqueries in a form like SET @variable = (some query here).

5. Fixed issue with SQL Assistant erroneously inserting INTO keywords in a wrong place. This issue could occur in a situation when user is coding SET statement after INSERT statement and INSERT has no INTO part.

6. Added support for hot tracking and plain name lists, in other words, support for cases object names are entered on separate lines as a plain text, and not as a valid SQL code.