A better way to license xSQL database deployment tools

Today we are introducing a new, more efficient and much more affordable way to license our database deployment tools, SQL Schema Compare, SQL Data Compare, xSQL Builder and Script Executor - instead of purchasing a perpetual license for each tool you can now purchase a one year Silver Subscription that includes all four tools.

How is the subscription better? The answer is simple - it is a lot cheaper initially, $399 versus $1,497, and the cost differential gets better every year, subscription renewal is only $199 versus the yearly maintenance cost of $250 for the 4 tools.

I have a Comparison Bundle license, can I switch to a subscription? Yes, if you have a Comparison Bundle license you can purchase a Subscription Renewal for only $199. You will need to provide the Comparison Bundle license.

xSQL Profiler prices slashed more than 70%

Recently we took a "deep dive" into the feedback we have received regarding our xSQL Profiler and have come to realize that while the single SQL Server instance license is sufficient for a good percentage of our users, there are many of you that would have liked to trace multiple SQL Server instances simultaneously but found the prices for a 5 or more SQL Server instances license prohibitively expensive.

Today we are changing that, we have slashed the xSQL Profiler prices to the point where we believe anyone who needs a multi-server license can easily afford it. Here are the new prices for xSQL Profiler:

• 1 SQL Server -> $0 (no change)
• 5 SQL Server Instances -> $199
• 10 SQL Server Instances -> $349
• 20 SQL Server Instances -> $699
• 100 SQL Server Instances -> $1,299

Keep sending us your comments and suggestions - we greatly appreciate it!

xSQL Builder v4 with support for SQL 2012 released

We just released version 4 of xSQL Builder for SQL Server. The new version is built on top of the new, much more efficient and robust database schema compare API that was released on November of last year. Here is what’s new on xSQL Builder v4:

• Improved performance thanks to the new schema compare API
• Support for a new optimized schema snapshot definition
• Full support for SQL Server 2012, SQL Server 2008 and SQL Server 2005
• New C# template built for Visual Studio .NET 2010
• New command line module for generating executable packages from the command line

You can download the new version from our site at: http://www.xsql.com/download/package.aspx?packageid=30

 

Important: if you are running a licensed old version of xSQL Builder and your license was purchased before February 21, 2013 then you might want to hold off on installing the new version until you have made the decision to upgrade since the new version overwrites the old and your license does not support the new version. Of course you can always try the new version on a different machine.

Installing xSQL Comparison Bundle on Windows 8

When installing our comparison tools (SQL Schema Compare and SQL Data Compare) on a Windows 8 machine the installation may fail with the message “SQL Server Comparison Bundle v4 Setup Wizard ended prematurely because of an error” (see screen shot below).

Cause: by default on a Windows 8 machine only .NET Framework 4.5 is enabled whereas previous versions of the .NET Framework are not enabled.  

Solution: enable .NET Framework 3.5 (this includes .NET 3 and .NET 2) on your machine. To do this go to Control Panel / Programs / Programs and Features / Turn Windows Features on or off and then check the “.NET Framework 3.5.1” checkbox and click OK (the machine needs to be connected to the Internet while this is being done. After enabling .NET Framework 3.5.1 re-run the installation of xSQL Comparison Bundle and it should install without a problem.

SQL Server Comparison bundle - new build available

A new build of the SQL Server Comparison Bundle is available for download. The changes implemented are relatively minor however, we recommend that if you are using version 4.x of the tools you download and install this new build, which:

• Fixes an issue with the GUI scaling on different resolution/DPI settings (both, schema and data compare).
• Fixes an issue with user membership to roles (schema compare).
• Fixes a bug related to the order of the included columns in an index (schema compare).
• Adds two new command line options for the data compare where clauses, allowing you to set different filters on each table/view on the pair (data compare).

SQL Schema Compare – schema filters

xSQL Schema Compare for SQL Server allows the user to define schema filters that determine which objects will be included or excluded in the comparison and synchronization process. The process of setting schema filters is fairly straight forward and does not need much explaining however, there is one critically important element that has the potential to create some confusion hence this article.
First, a schema filter expression is defined for a particular object type and contains one or more filter criteria. The schema filter expression has a parameter called "FilterValidationType" that can be set to "AtLeastOneCriteria" or "AllCriteria". Each filter criteria has an "Action" parameter that can be set to "Exclude" or "Include" meaning that the object that meets this particular criteria will be excluded or included.
So, let's consider the schema filter expression defined as below:
<SchemaFilterExpressions>
    <SchemaFilterExpression ObjectType="StoredProcedure" FilterValidationType="AllCriteria">
        <SchemaFilterCriteria Action="Exclude" FilterType="StartsWith" Criteria="sp_MSins" />
        <SchemaFilterCriteria Action="Exclude" FilterType="StartsWith" Criteria="sp_MSdel" />
        <SchemaFilterCriteria Action="Exclude" FilterType="StartsWith" Criteria="sp_MSupd" />
    </SchemaFilterExpression>
</SchemaFilterExpressions>

Here is what might confuse things: whether you have defined the criteria action as"exclude" or "include" behind the scenes xSQL Schema Compare for SQL Server translates the object filter expression into an include statement, in other words the final statement selects objects that will be included in the comparison.

So, the above schema filter expression translates into something like this:
   SELECT all stored procedures WHERE [sp name] NOT LIKE 'sp_MSins%'
   AND [sp name] NOT LIKE 'sp_MSdel%' AND [sp name] NOT LIKE 'sp_MSupd%'

Interpretation: all stored procedures the name of which starts with one of those three strings will be excluded whereas all other stored procedures will be included in the comparison.

What if you had set the FilterValidationType = "AtLeastOneCriteria"? Behind the scenes the expression would then translate into something like:
   SELECT all stored procedures WHERE [sp name] NOT LIKE 'sp_MSins%'
   OR [sp name] NOT LIKE 'sp_MSdel%' AND [sp name] NOT LIKE 'sp_MSupd%'Well, as you see when written this way this filter is as good as not being there at all since every stored procedure, regardless of the name will pass this validation and will be included in the comparison.
xSQL Schema Compare for SQL Server is free for SQL Server Express Edition and you can download it from:  http://www.xsql.com/download/package.aspx?packageid=10

SQL Schema Compare with Snapshot Utility

We just published a new build of xSQL Schema Compare for SQL Server. Here are the highlights of the new build:

1. Snapshot Utility - allows you to take database schema snapshots via the command line. You can now for example, automatically take a daily snapshot of the database schema and then, whenever you need to, go back and see what schema changes were made from one snapshot to another or from one snapshot to the live database.
2. Snapshot Converter - a standalone tool that allows you to convert in bulk database snapshots created with previous versions of the xSQL Schema Compare.
3. UI support for old schema snapshots - adds UI support for snapshots created with previous version of the xSQL Schema Compare
4. New command line features - object exclusion by type or name, new element for complex schema filters, new elements for comparison options etc.
5. Bug fixes - fixes some issues with the Command Line utility.

You can download the new build of xSQL Schema Compare for SQL Server from our site: http://www.xsql.com/download/package.aspx?packageid=10