3.2 Update this week We are currently planning to release a new build of 3.2 this week.  The build will include some updates to the parser for complex GROUP BY statements, but the largest update is the relaxed keywords. We took a good hard look at the keyword support in SQL Server 2005.  Our initial update was a little too aggressive in that it also pushed the future keywords for SQL Server 2008 into the keywords list.  Since almost no one is using the 2008 version yet, it seems silly to force people into that keyword list now.  I think in the future we will have to either provider two parsers, or build in a syntax compatibility level similar to how SQL Server allows the app to set a requested level. 3.3 Beta coming soon We are internally testing our TSQL Procs support now!  Documentation is in progress, and test cases are being written.  I expect we will release a first beta in the next few weeks, and then continue to push out betas for the next 6-8 weeks. Initial support The initial support for TSQL Procs will no doubt have some rough edges.  We are still adding the support to the Data Builder, and the samples will probably be sparse as well.  But we are very excited about the ability, and want to get feedback from as many users as possible.  As always our initial concerns are going to be parsing, and running the procs.  Then we will work on optimization later.  Get it working, make sure it is safe, and then make it faster. Temp Tables Another feature that is being requested hand in hand with TSQL Procs is temp tables.  I know a lot of users put the two hand in hand since they use temp tables so often within their stored procs.  We will not have temp tables support in the initial betas of 3.3.  It is on the list to try and squeeze into the initial release of 3.3, but it may slip into a later build of 3.3. Help us test All current subscribers will be eligible to download the 3.3 beta and help us test, provide feedback, etc.  I fully expect to find a lot of syntax that is totally new to us from users throwing their SP’s at the engine.  We need to indentify the functions and features users need within their stored procs.  They may not all make it in the initial release (like temp tables), but we will document them and continue to release updates. Performance optimizations We also have some ideas for new optimizations that we will continue to test and deploy as they are implemented.  We have a number of options available to us now since Dot Net 2 is our baseline for the provider.