It is with great pleasure that we at VistaDB announce the release of VistaDB 3.3.  VistaDB is the world’s first non Microsoft database to support syntax compatibility with SQL Server. 

Some of the new features in VistaDB 3.3:

TSQL Procs – You can now run TSQL Stored Procedures in VistaDB.

TSQL User Defined Functions – with support for any return type. Improved SQL compliance with SQL Server – SQL parser has been improved. New SQL Syntax – While / Break / Continue syntax is now supported along with other improvements.

Temp Tables support – Tables that live only for the lifetime of your connection, or for the execution of a stored proc.

With over 500 NUnit tests our code coverage is now over 64% total, and many of our internal objects are quickly approaching the 80% goal we set for ourselves in Apr 2007.  The code coverage tests alone have helped us to improve stability, and prevent regression of code while adding all these new features to the VistaDB engine. Licensing changes are included in this final build.  You are now prompted for your serial number during setup.  This key is transmitted via SOAP to a webserver that generates a license file for your machine.  Look for a blog entry about the new license system in the next few days.   It is not evil, in fact we have tried to be as conscious of how programmers work as possible.  After all, we are programmers too and hate super difficult licenses.  The runtime is license free, you can continue to distribute as many copies of your application as you desire.  We only license per developer, and build machines are free as long as they don’t need to debug the application interactively (the EULA has been updated with this change).

Build #49, 12/31/2007

NOTES

We only have minor issues outstanding from the beta and release candidate cycle so we are going to release. There are SO many new and updated things in 3.3 from 3.2 that I ask you to view the history on the site.

ISSUES AND FIXES

#348:  Unexpected results comparing x = null and x is null syntax - Fixed

#335:  Error executing stored proc - resolved

#42:   Add support for CommandBuilder.DeriveParameters Method - implemented

#351:  Encrypt all columns check box should not be enabled if database is not encrypted - implemented

OTHER NON TICKETED ITEMS

Help files are updated to the 3.3 API calls, and the general help includes some new areas on [database schema] selections.  Also look at the NUnit tests for sample schema queries from the VistaDBConnection object.

VistaDBConnection was allowing you to set IsolationLevels other than ReadCommitted even though they were being ignored.  We now throw an exception if you attempt to set an invalid Isolation level for transactions.  Only ReadCommitted Isolation is supported.

Thanks to SP1 for Dot Net 2 we are modifying our GC.Collect() policy to only collect gen 0 objects when we have just released a large portion of them.  This happens due to indexes being rebuilt, unloaded, etc.  The GC in SP1 is quite a bit better and everyone with the framework should auto get it through Windows Update.  If you have machines running out of RAM check that they have SP1.  That was why we had to Collect before, the 2.0 RTM GC would lose track of large objects and pin them in Gen 2 forever.