New in Release 2.2 (Build 707)
Enhancements
#847 - SQL Server 2005 Full Support
* The SQL-DMO API is now used for legacy use only, SMO is used by
default. The parser was modified extensively to handle the new
SQL script style. For example, SQL within apostrophe-style
quoting is now supported. Also, AdventureWorks can be compared
and transformed.
* Schemas are supported.
* XML Schema Collections are supported.
#820 - Re-open Last "Unnamed Project"
The "re-open last project" option was introduced in earlier versions of
SQLMatcher to facilitate the use of projects. One of the limitations of
this feature is that SQLMatcher is often used in an ad-hoc manner. When
used in this way the "re-open last project" actually gets in the way-
SQLMatcher keeps reverting back to the last project that was saved even
if the user last worked with an unnamed project (i.e. ad hoc).
In this version of SQLMatcher it loads the last project automatically if
the user was working with a project. If the user was not working with
a project then SQLMatcher loads the source and target database references
only and all of the project options revert back to their defaults. This
is the default behaviour when not working with a project.
#829 - Performance Improvement (up to 15%)
This mainly affects comparisons that don't generate scripts from live databases
though.
Fixes
#814 - "EXISTS" EXPECTED, BUT "@@microsoftversion" FOUND INSTEAD
The SQL parser didn't support "IF NOT EXISTS..." conditional statements
that referred to @@microsoftversion.
#828 - Feedback "Name" and "E-mail" Fields Reset Incorrectly
The "Name" and "E-mail" were reset incorrectly under the following conditions:
* Clicking on "Submit Serial #" checkbox.
* Clicking on "Submit Additional Data" checkbox.
* Clicking on the "Append Clipboard Text" button.
#832 - Unique Unnamed Constraints Not Handled in Table Defn
For example, in this SQL:
CREATE TABLE [dbo].[EmployeeTable] (
...
[SSN] [char] (11) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
UNIQUE NONCLUSTERED
(
[SSN]
) ...
#833 - "UNION ALL" Not Supported in View Definition
For example, SQLMatcher would log two parsing errors when parsing this:
CREATE VIEW Customers AS
SELECT *
FROM Customers_33
UNION ALL
SELECT *
FROM Customers_66
UNION ALL
SELECT *
FROM Customers_99
#835 - EOutOfResources Exception with Database Browser
This occurred on some system configurations that had SQL Server 2000,
an MSDE SQL 2000 instance, and Visual Studio 2005 and/or SQL Express 2005.
This has been resolved by moving from SQL-DMO to SMO.
#839 - Embedded Quotes Not Handled Correctly In View Table Refs
ISSUE 1:
CREATE VIEW VW_TEST AS SELECT * FROM "SOME TABLE ""'"
(i.e. quote, SOME TABLE, quote quote apostrophe quote)
was parsed as if it was:
CREATE VIEW VW_TEST AS SELECT * FROM "SOME TABLE""'"
(i.e. the space was swallowed)
This could lead to problems when determining dependencies and
could cause transform problems with views (i.e. sequence of SQL
statements could be incorrect).
ISSUE 2:
CREATE VIEW ['"'"QUOTES], [QUOTE '"VIEW NAME 2]
AS SELECT * FROM [SOME TABLE "']
was parsed as if it was:
CREATE VIEW ['"'"QUOTES], [QUOTE '"VIEW NAME 2]
AS SELECT * FROM [SOME TABLE "]
#841 - Improved Options Form Validation
The form validation would result in the form closing. It should've
rather failed validation and required correct input before closing.
#842 - Improved Error Message when Temp Folder Doesn't Exist
The message given when comparing side-by-side text was very cryptic.
Now it has been improved to say that the directory doesn't exist.
#843 - Parse "if (@@microsoftversion > 0x07000000 )"
This style of SQL script is now handled properly.
