Build #69, 10/24/2008

NOTES

Trial users

This build is the first public trial version for VistaDB 3.4.  It is available as a separate download and does include timeouts on the runtime.  The runtime will stop working in 30 days if it is a trial binary.  The full developer builds have no limits on the runtime or license validation since it is free to distribute the runtime for all licensed developers.

The Visual Studio designer will prompt the user to show them they are on day x of their 30 day trial.  This will only happen ONCE per day (trying to not be annoying).  At the end of the 30 days it will prompt you that your trial has expired and not load the designer or engine.

Connection Pooling

Connection Pooling defaults have been changed to Min Pool size of 1 and a Max Pool of 100.
The pool is disabled by default.  It already was in 3.4, but the flag was set to true even though the pool had a size of 0 to disable it.  This is bad behavior.  We now set the flag to false and leave the default value at a reasonable number. Do not test for Min Pool size to see if connection pooling is turned on, you should test for Pooling=true. 
Some sample connectionstrings:

Pooling OFF
Data Source=mydatabase.vdb3;Pooling=false

Pooling On using defaults (MIN 1, MAX 100)
Data Source=mydatabase.vdb3;Pooling=true

Pooling On using custom values
Data Source=mydatabase.vdb3;Pooling=true;Min Pool Size=10;Max Pool Size=20

Garbage Namespaces Issue

The Obfuscated namespaces exposed to Visual Studio intellisense.  They really should not be displayed any of these because they are tagged as internal.  But we do expose them for internal NUnit testing this is done through an attribute on the assembly.  It appears that this attribute (even though it spells out a very specific dll and strong name pair) will also expose them to normal intellisense as well.  Not what we intended, we now just conditional compile that attribute only on debug builds for internal test purposes.

How index names are generated

TSQL Foreign key generation naming used to be auto prefixed with sys#.  Now auto prefix with the type of key, the table name (relationtable if required) and then a number if the key already exists.  This is to be more inline with SQL Server naming of keys and indexs based upon the table and columns they actually change.  It does not impact their generation or how they operate, just the default name given if you do not supply one.  Hopefully will make the default generate names easier to use.

OLD: Sys1
NEW: FK_PrimaryTable_ChildTable
NEW: PK_Table
NEW: UC_Table_Column  (Constraint)
NEW: IX_TableName
 

Encrypted Database Issue

TSQL generation of a table on an encrypted database does not set the encryption flag on the new table.  This item is still open, we just wanted to make everyone aware of it.  You should open your tables in the Data Builder and ensure the encryption flag is set on the tables you want encrypted.  We will address this in a future build to ensure that all newly created tables in a database are encrypted by default.  Right now only DDA ones add the attribute by default.  Removing and reapplying encryption to a database will properly encrypt all of the tables.

ISSUES AND FIXES

#1438: GC namespace conflict for short naming.
#1415: Visual Studio unable to drag a stored proc from server panel onto a schema file - Fixed
#1497: Create View SQL Cannot Exceed Max Char Length 8192 - Internal type was using nvarchar which cannot exceed 8192, changed internal type to TEXT.  This is for the output from tables and views.