Steve Lasker's Web Log

Hi Mike,

For database management tools, you’ll need VS 2008 B2.  VS 2005 and SQL Server 2005 Management studio both look for SQLce 3.1.  You could of course create a 3.1 database then update it with the SqlCeEngine.Update() menthod, but you’ll need the newer 2008 VS and Management tools to get the new database tools.

I’ll pass on the SQLMetal 64/bit question to find out if they’ve finished testing.  As far as I know, it should just work as think they’re all managed code, but I’m just guessing here.  I’ll try and confirm.

Steve

Ok, I realized the problem when talking with Dinesh (PM for DLINQ) and Ambrish. (PM for SQLce).  While VS is limited to WOW mode, SQLMetal is fully managed.  Because the LINQ to SQL Designer isn’t enabled for SQLce, you need to use SQLMetal from the command line. That means you’re no longer limited (nicely constrained) by VS to WOW mode.  If you run SQLMetal in full native 64bit mode, and SQLce is in-proc, you’ve got an impedance mismatch.  If you simply run SQLMetal in WOW mode, you should be fine as things will just line up.  

This was a good catch and we’re discussing how to document this behavior until we get SQLce in full native 64bit mode.

Thanks

Steve

Hi Jacqueline,

Visual Studio 2005 and SQL Server Management Studio 2005 will be unable to connect to SQL Server Compact 3.5 databases as they don’t have knowledge of the future/newer format.  However, you did point out that this blog post didn’t point out how to use SQL Server Management Studio with SQL Server Compact 3.1.  

In order to use SQL Server Management Studio with SQL Server Compact 3.1, you’ll need SQL Server SP2.

http://technet.microsoft.com/en-us/sqlserver/bb426877.aspx In addition to the SQL Server Engine, SP2 includes updates to the SQL Server Management Studio, including the Express editions.

Steve

Hi Tech,

The way you create 3.5 databases in code is the same as 3.0/3.1.  Assuming you're working from managed code, you'll just need to reference the new 3.5 version of the System.Data.SqlServerCe provider.

The easiest way is to use the SqlCeEngine.CreateDatabase() method.  Here's a blog post that covers the larger scenario: http://blogs.msdn.com/stevelasker/archive/2007/03/31/creating-your-sql-server-compact-edition-database-and-schema-in-code.aspx

These are covered in the docs listed above as well, but I'm more than happy to help,

Steve

Hi Shalan,

You can install 3.1 and 3.5 side by side so you can easily take advantage of the 3.5 features without having to worry about 3.1 based apps.

Just be aware that we don't have tooling for 3.5 in VS 2005.  Likewise, we don't have tooling for 3.1 in VS 2008.

This is something we'd like to solve in the future, but a current limitation.

Steve

Hi Sam,

Laxmi wrote a very extensive post here: Connectivity Cross Version Compatibility (SQL Server Compact 3.5) discussing the different compat modes.  RDA is part of our Merge stack, so just substitute RDA for Merge.

That said, are you just starting out with RDA?  Or are you using it from a pre-existing app.

If you're new to RDA, you might really want to check out Sync Services.  For some background, you may want to read some explinations here: Q&A on OCS & Sync Services for ADO.NET

Steve