SQL Server Compact 3.5 SP1 Released

I'm happy to announce the release of SQL Server Compact - SP1 

This release includes several key features and bug fixes following up on the asks of our customers.

The new features in SQL Server Compact 3.5 SP1 are:

  • ADO.NET Entity Framework provider. The Entity Framework enables you to work with data in the form of domain-specific objects and properties, such as customers and customer addresses, without having to concern yourself with the underlying database tables and columns where this data is stored.

    • Support for the ADO.NET Entity Framework allows you to create flexible, strongly typed queries against the Entity Framework object context by using LINQ expressions and the LINQ standard query operators directly from the development environment.

  • Case-sensitive collations for those C# folks that were allowed into the database <g>

  • Native 64bit support. No more locking your apps to WoW mode or Target = X86. And yes, we support a single version of your app that can privately deploy Compact 32 and 64 so your customers don't have to figure out whether they're running 32 or 64bit operating systems.

We'll have a KB article out soon that covers the rollup of bug fixes since RTM as well.

We're still waiting on the main landing/content pages to be updated, so for those of you too impatient, here's the download links directly:

August 7th update: Links updated to reflect download pages with 32bit and 64bit downloads, along with the localized versions

SQL Server Compact SP1 will be included in Visual Studio 2008 SP1 as well.  So, you won't need to download it separately like you did in Visual Studio 2005 SP1.  ...we've gotten better about integrating things for you...  These links are mostly for those that need SQL Server Compact SP1 for VS 2005 support, or those that can't install VS 2008 SP1 for some reason.  The Visual Studio 2008 SP1 setup is sooooo much better than VS 2005 SP1.

More posts to come, but just to answer the first Q&A:

Q: What .NET FX Versions does Sp1 Require:
A: Compact SP1 can be used with VS 2005, .NET FX 2.0, 3.0, 3.5 and 3.5 SP1.  When using the Entity Provider, you will need .NET FX 3.5 SP1 as this is where the entity framework ships.

Thanks, and as always, we welcome your feedback,

Steve and the rest of the SQL Server Compact team

Comments (31)
  1. Raman says:

    Hi Steve,


    Will your team be releasing the tool to export data to SQLCE from SQL Server?  Last time I checked with you, you told me that testing was not complete and planning to release by end of summer.



    RND Technology Solutions, Inc

  2. The title pretty much says it all but for more information, check out Steve Lasker’s post .

  3. Steve Lasker made the announcement that SQL Server Compact 3.5 SP1 has been released to the wild.&#160;

  4. AlexZ says:

    When the EF going to available for devices?

  5. SQL Server 2008 RTM is out! Microsoft Sync Framework v1.0 RTM is out! Sync Services [now @ v2] is “synchronized”

  6. Miguel Madero says:


    Does the EF provider works for devices?

  7. Steve Lasker just announced that SQL Server Compact 3.5 service pack 1 is released, read his announcement

  8. Steve Lasker just announced that SQL Server Compact 3.5 service pack 1 is released, read his announcement

  9. Daniel Smith says:

    If we install SQL Server Compact 3.5 SP1 now, will that causes any problems once VS2008 SP1 comes out?

    Is it worth waiting for VS2008 SP1 to get this, or could it be a while away?

  10. E&#39; stata rilasciata l&#39;SP1 della versione 3.5 di SQL Server Compact Edition: http://blogs.msdn

  11. Peter Foot says:

    To coincide with the RTM release of SQL Server 2008 the SQL Compact Team have delivered Service Pack

  12. Peter Foot says:

    To coincide with the RTM release of SQL Server 2008 the SQL Compact Team have delivered Service Pack

  13. Steve Lasker says:

    A few Q&A’s on the SP1 release:

    Q: Will Entity Framework be available for devices?
    A: Unfortunately no.  With the size constraints of the .NET Compact Framework, and the target of Entity Framework 1.0 being mostly a mid-tier technology, we still need some more work to make it a great client model as well.  Since the server and desktop versions of the .NET Framework are the same, we sort of “get this for free” with the desktop version of SQL Server Compact.  While it’s still too early to commit to anything, we have been demonstrating project codename “Astoria” – Offline, which uses the Entity Model on the server, REST based programming across the network, and a local SQL Server Compact Entity Store.   We hope to make this a consistent story across all our Microsoft client programming models.


    Q: Will installing the SP1 release have a negative effect when you install Visual Studio 2008 SP1?
    No.  We have fully tested these scenarios.  SQL Server Compact SP1 is its own MSI.  When VS 2008 SP1 installs, it simply checks if Compact 3.5 SP1 is already installed.  If so, skip.  If not, install. 


  14. beqiraj.net says:

    Microsoft SQL Server Compact 3.5 Service Pack 1 now available

  15. August 6th 2008 UPDATE : SQL Server Compact 3.5 SP1 has shipped: SQL Server Compact 3.5 SP1 Released

  16. 真见 says:


  17. 真见 says:


  18. cnblogs.com says:

    自定义Visual Studio主题 SQL SERVER 2008最好的特性-sqlps.exe??? &#160; Yahoo! UI Library: YUI Compressor for .Net

  19. Dave Mc in Cork says:

    I’m confused. I’ve just installed the Microsoft Sync Framework v1.0 which includes Sync Services for ADO.NET v2.0. I notice that this requires SQL CE 3.5 SP1 but when I go to download that I see that it in turn comes with Sync Services for ADO.NET v1.0 included. What’s going on? Can I not just install SQL CE 3.5 SP1 without Sync Services for ADO.NET v1.0?

  20. Jack Bond says:

    When will the platform builder update be released?

  21. Steve Lasker says:

    Hi Dave,

    I realize the packaging is a bit confusing.  This is the result of ship cycles and some packaging decisions we made for Sync Services 1.0 and what we’re doing long term.

    For Sync Services 1.0, we choose to package the desktop runtime with SQL Server Compact as we weren’t able to spin up another product packaging team in time to ship with Visual Studio 2008.  Shipping individual products carries a significant cost for a company as broad as Microsoft as we must deal with localization, accessibility, security, sustained engineering and lots of other “taxes”.  It was our belief the value in delivering the end to end scenarios, including the designer support in VS was worth the short term packaging issues.  If you look at Sync Services for devices, we’ve already rolled out the Sync Services to a separate download.

    Why does Compact SP1 include Sync Services?  We can’t remove a component in a service pack.  The fact that Sync Framework 1.0 actually ships Sync Services 2.0 was another timing issue.  The reality is shipping in a product as big as VS requires a very long lead time to be finished before it actually ships to customers.  Between the point we finished Sync Services 1.0 and Sync Framework 1.0, we were able to get a lot more work done that we didn’t want to wait.

    Luckily, the size of these components are very small, and the impact to the developers machine is nill as there’s no services running etc.  It’s just disk space.  As for your end users, you certainly have a choice for which to use.  

    For the long road, in Dev10, the next major release of SQL Server Compact, we will be removing the Sync Services components from the SQL Server Compact packaging.  So, this will “clean up” as we move along.  

    Hope that explains the what and why,


  22. Steve Lasker says:

    Hi Dave,

    Platform Builder for CE 5.0 and 6.0 will be released in the next platform builder update.  They have a regular monthly update, so soon…



  23. hintzen says:


    Sorry for a newbie question but 2 days of searching / reading books online and googleing hasn’t helped ( I problably haven’t used the right words in the google search).

    I have a SQL Compact 3.5 sdf file, if I connect to it in Visual Studio 2008 data connection, in a simple table, I can add two rows.

    I also have a simple hello world windows app in VS2008 that databinds a gridview to the same table, if I run the application I can see the two rows I added in Visual Studio.  I can then add more rows.  

    I start and stop the application and all my changes show up in the windows app (I can even restart my machine and all changes are persisted).. BUT the minute I then view the same table in Visual Studio data connections, all my changes are gone, and the original two rows I entered show up. And then if I run the Application it also has lost all changes.

    Same thing happens if I view the data thru SQL Management Studio (2008).

    What is going on?  How can I make changes in a Windows application and then have those changes persisted to the table so that if I view the table in Visual Studio Data Connection, the changes show up there?

    Thanks for any help you can offer.

    Matthew Hintzen

  24. the_architect says:


    I bet you’ve been asked this several times before, but here goes:

    Can I use SQL Compact Edition as a client/server database for around 20 Users if I put a Data Access Layer Service in front of it such as Enterprise Services??

    As far as the SQL CE DB is concerned, it would only be interacting with this DAL.

    The benefits and ease of SQL CE vs SQL Express for deployment are too good to ignore. And it is surprising to see the lack of any information by Microsoft in providing a built-in mechanism to hide the database design from administrators. As more and more canned applications are being remotely deployed, and to avoid server-side data manipulation, this becomes more important.

    Thanks a lot.

  25. We’ve started to get a number of request whether SQL Server Compact will support 64bit. The answer is

  26. beqiraj.net says:

    Microsoft SQL Server Compact 3.5 Service Pack 1 Released

  27. Stephen says:


    Our developers have been looking at Visual Studio 2008 and SQL Server Compact and it looks very good I must say.

    We are about to rewrite our companies biggest software product. It is a Windows Application that currently stores data in MS Access files (the data storage must be portable – must be possible to email, put on memory stick etc.).

    Would Microsoft now recommend that we use SQL Server Compact now and leave MS Access behind?

    It’s going to be a two year project to re-write the product. So we need to make a decision on technology in the next month or two.

    Many thanks,


  28. Sid says:

    Is the link for books online also supposed to contain 3.5 SP1 samples?

    The downloadcenter page instructions say following: "Click the Books Online OR the Samples Download button". However, there is no "Samples Download button".

    I installed the SSCEBOL-ENU.msi from that page but after install the samples folder only contains northwind.sdf. There are no cpp/cs files in C:Program FilesMicrosoft SQL Server Compact Editionv3.5Samples.

    Is this a user error? Or is there an environment requirement for installing samples?

  29. Steve Lasker says:

    Hi Stephen,

    Microsoft is a big company, so it’s hard to make a blanket recommendation.  Compact is the focus for local databases, from the SQL Server divisions point of view.  Jet, or now ACE is still being evolved by the Office team, but it hasn’t been tightly enabled with Visual Studio and .NET.  The problem is we really don’t have a fully integrated story for SQL Server Compact within Office Apps.  You can use Visual Studio Tools for Office (VSTO) to enable .NET code within most Office apps.  It’s the tool bar data wizards that don’t “just work” with Compact.

    So, if you’re writing a managed code app (WinForms or WPF), than you’ll get “more love” by using Compact as it is our primary focus.  For instance, we do have a 64bit version of Compact, but not Jet.  We are doing even more managed code investments with Compact, so I’d say it is a good investment.

    Hope that helps,


  30. Stephen says:


    Thanks for your reply – that’s exactly what I was after.

    Our application is not based in Office – it will be done in Visual Studio with the .Net framework – so we’ll go down the SQL compact route.

    Many thanks,


Comments are closed.

Skip to main content