SQL Server Everywhere Gets a New Name

You know you’ve got a successful product when everyone cares about the name.  Since we’ve posted the June CTP, we’ve received feedback that the name was causing some confusion with some partner products.  We care a lot about the partner community and have decided to change the name, again.
And the new name is….
SQL Server Compact Edition
Yup, that’s right, we’ve gone a little retro and have used the original name.  So, why Compact?  Because that’s exactly what it is.  The compact version of the mighty SQL Server family.  I’ve spent a lot of time trying to answer questions about how Express and Everywhere compare.  Calling it Compact Edition worked for several reasons. 

  • It helped identify its role in the SQL Server family.  In order to help clear up the confusion with Express, I’ve written a whitepaper that not only talks about the feature comparison of Express and Compact Edition, but it delves into the differences in a local database programming model.  The paper will be released soon, once we finish the name changes, <g>

  • By leveraging an existing name, it allowed us to quickly turn around the name change and meet our commitment to ship in ’06.  You’d be surprised at how much work goes into naming a product.  In addition to all the legal name issues, we have to localize the product in 20+ languages and release on several mobile platforms.  This all takes time. 

  • In order to maintain backwards compatibility of the source code developers have been writing for years, we never changed the names of the dlls, namespaces or types.  Going back to SQLce meant all the SQLce samples, namespaces, and type names will again be relevant.  By doing a quick search on SQLce, you’ll get years of content available at your fingertips.  Of course, you no longer need to worry about the device limitation.

A couple of Q & A’s

Q  Does SQLCE mean it’s limited to the CE, mobile platform?
 No.  This has caused the most angst about the name.  SQL Server Mobile edition was too limiting as it implied a limitation to mobile scenarios.  We do plan to use SQLce in multiple locations and new environments.  Mobile would have been too limiting.  The trick is to not confuse the fact that we have a CE platform, and use the Compact name as it applies to the SQL Server family

Q Does the new name reflect any changes in supported platforms?
 Yes.  We continue to add to our platforms supported.  Based on your feedback, we’ve added Windows 2000.  SQLce will be an important part of our database strategy to help developers, enterprises, ISV’s and end users manage data wherever they are, whether or not they’re connected to “the network”  As the Microsoft platform reaches further out, SQLce will continue to reach with it.  SQL Server Compact Edition is our default database for local storage.

Q What’s the release date?
 Very, very soon.  We had the RTM bits complete and were ready to launch at our next big developer event.  Because of the name change, we won’t be able to go RTM on that same date as it will take us several weeks to re-localize the runtime, all the docs and update the tooling with the new name.  We will release the current RTM quality bits as a release candidate (RC), and aprox. 5 weeks later release the renamed packages.  All of this fits within the next several weeks. 

What functionality is in the new SQL Server Compact Edition product?
 Since the June CTP, the team has been busy integrating feedback and some minimal feature work including

  • Finished the |DataDirectory| support on all the SqlCeConnection objects. 

  • With the addition of Visual Studio SP1, the DataDirectory macro will automatically be added to your connection string and the ClickOnce bootstrapper will be automatically checked when a SQLce data file is added to your project.

  • With the support of Scott Swigart, the team has done some performance work to deal with the differences in desktop environments.  The team can, and will do more performance work, but they did improve a number of scenarios including new row insert performance. 
    On devices, “disk” space is very expensive.  SQL Mobile only added the minimal amount of partition space when the .sdf file filled up.  That meant that when you’re doing a lot of inserts, the engine was continuing to have to increase disk partitions.  On desktop, we’ve increased the amount of space when the .sdf file filled up.  This work was only applied to the Desktop as we don't want to degrade device scenarios.  The team is looking to expose this configuration option in the next release.

  • Worked out the quirks of creating a desktop MSI and appropriately GAC the managed components.  The native dlls required some updating as well to properly support GAC’d deployment and private deployment

  • Vista work to support UAC

  • Addition of the ClickOnce bootstrapper and integration into VS

  • A number of bug fixes in the Tooling of SQLce within VS – coming with Visual Studio SP1

  • Support for SQLce within SQL Server Management Studio – coming with SQL Server Management Studio SP2

Why so long, for so little amount of feature work?
 Great question.  With the name change, it was felt the product should have a consistent tooling and runtime experience.  While we did have some work to do within the product, most of the time has been waiting for a consistent tooling experience within Visual Studio.  With VS Sp1 the tooling won’t jump from SQL Server Mobile Edition to SQL Server Everywhere Edition to SQL Server Compact Edition.  Visual Studio has a lot of components and teams delivering, so it took several teams to incorporate the name changes. 

Doing all this tooling work, and supporting new scenarios, we didn’t want to take a great product, SQL Server Mobile, and make it less stable, so we wanted to take the time to make sure we had a great end to end experience.  I won’t say it’s perfect, and we’ll be doing more work in Orcas to round out the tooling and experience to make it easier to use SQLce as the default local database for client applications, but we got a lot done within an interim release and service pack.

Q What can we expect from the next release, and when will it be available?
A The SQLce team has spent most of their time this last year working on the next release.  We already have a 3.5 release mostly done which incorporates several new features including all the OCS work we’ve been doing.  You can see on the screen cast I did earlier at: http://blogs.msdn.com/stevelasker/archive/2006/10/13/occasionally-connected-systems-sync-framework.aspx  The 3.5 release is scheduled to release with the next release of Visual Studio code named Orcas, which is scheduled for the end of ’07, beginning of ‘08

Q Will SQLce be in the .NET Framework
A No.  The current design of the. NET framework is anything that ships in the framework, must only ship in the framework and ship on its schedule.  I say current because we recongnize the deployment and servicing issues of the framework and are working on some exciting new things that will make this mo' better.  Because SQLce will ship more frequently, and we're working on some new deployment characteristics of the framework, we’ve taken the painful decision to not ship in the framework.  As an example, if we had shipped in the 2.0 framework for Tablet PCs only, we would not have been able to ship this release to the broader platforms.  Version 3.5 will ship with, or before Orcas.  4.0 will ship at the same time as the next release of SQL Server.  This means SQLce will have shipped 3-4 times in the same time as SQL Server and Visual Studio.  In order to ease deployments, we do support private deployment of the SQLce runtime within each application.  This eases the need to admin deploy the runtime throughout your users.

Q Will Compact Edition Support Side by Side
A Yes.  One of our main goals of SQLce is to make developers productive building client applications that enable end users.  Part of that productivity involves stability of their client apps.  An application that was installed, and working perfectly fine with SQLce 3.1, shouldn’t be forced to upgrade to 5.0 just because they also installed another application that just happened to use 5.0.  We haven’t forgotten dll hell and having MDAC upgrade and break your existing apps. 

That's all for now.  Enjoy, and keep the feedback coming,


Comments (56)
  1. Well they are all one and same thing. SQL CE has gone thru several versions and name changes which has

  2. Austin says:

    I’m a bit confused on some schedules, could you clarify something for me?

    You mention that the new version is very near to shipping, in a matter of weeks – which is awesome.

    Later, you mention that the OCS work is part of the 3.5 cycle, due for Orcas.

    Will the OCS bits work against the release coming out in a few weeks?  In other words – if we get the OCS CTP, can we test it, and create apps with it, against the version that RTMs soon, or will we have to use the CTP only against a v3.5 SQLce CTP?

    Thanks for the update Steve – I’m not trying to be grumpy, just want to understand when things are expected to come out so I can try to plan for pilot projects and things.

  3. Steve Lasker reports that due to customer feedback Microsoft has renamed SQL Server Everywhere to SQL…

  4. Robert Kozak says:

    Hmm. Is there a web page describing the differences between SQLCE and SQl Sever Express?

    Honestly, I am a little confused with these two products now.

    — Robert Kozak

  5. Sean says:

    Yeah, I’m also a bit confused about the release dates.

    I gather that 3.0 is what’s coming ‘very very soon’ and will not include OCS stuff.. 3.5 = OCS + Orcas tooling, 4.0 = Features that will be included with the next version of SQL (Entity SQL-in-the-DB?)

    Seems like a long time to wait for OCS.. 🙁

  6. JohnGalt says:

    Any movement on the 4 gig limit??? To be useful for your intended audience this needs to be removed and you need to limit it to not allow connections across a network share.  The way it is right now is of VERY limited use.

  7. Steve Lasker says:

    Release Dates:

    SQL Server Mobile Edition (3.0) was released with Visual Studio 2005 (Whidbey)

    SQL Server Compact Edition (3.1) will release in the next several weeks.  This will enable the device scenarios on the larger desktop/win 32 platform.  This platform supports Merge Replication and RDA.  In order to tap into the existing tooling within Visual Studio, 3.1 is not the physical version number, but more a reference point.  Technically, they still use 3.0 managed versions.  Consider 3.1 as a service pack for 3.0.

    SQL Server Compact Edition (3.5) will ship with, or before, Orcas (end of ’07).  The new sync runtime will ship with 3.5 and only work with SQLce 3.5.  As you may have seen in the screen cast, the client side portion of sync services are simplified as the knowledge of change tracking is incorporated into the SQLce storage engine.  Yes, the CTP will require 3.5.  3.5 will run side by side, SxS with 3.1 so you can opt-in to which apps will use 3.1 and 3.5.

    We’ll have a CTP available soon, so while it will take a bit to ship, we want to make sure we’re shipping the right thing.  Having the CTP available soon will give you the opportunity for feedback, and to get started soon.  No promises, but if we get enough positive feedback, we could consider a GoLive license for early adopters.

    No problem Austin.  Lots of data to digest

    SQL Server Express, SQL Server Compact Edition

    We have a white paper that we just finished up that will help explain things a bit.  As soon as it’s available, I’ll post a link to it.

    Consider SQLce as the default local database.  Express is the entry point to data services.  

    4gb limit.  This will be relaxed, but not immediately.  4gb was huge for a device.  For desktops, we realize some scenarios may find that limiting.  As discussed with the Insert performance discussion, 4gb is a little hard backed into the product, so it’s not as easy to just flip the bit.  However, we will increase this.  4gb is still a lot of data to move across the wire, so I’d love to hear of scenarios where you really need 4gb locally.  We’ve found most customers partition their data as maintain 4gb across flakey networks can be difficult.  But, we do know there are valid scenarios.  We’d just like to understand the types of data.  Large rows.  Large columns, many tables, embedded images, etc.

    Network Shares

    SQLce does support network shares, but not from concurrent machines which is that I assume you’re asking for.  At this point, we don’t plan to enable this as it encroaches on the data service scenarios that historically open the can of worms we’d like to contain.  Jet was plagued with issues from multiple users working from a shared file.  Everything from file corruption, to scalability issues.  We’d rather leverage the Data Service SKU’s, including the free SQL Server Express Edition for shared data, and the OCS features to synchronize that central data between clients.  We do plan to enable peer to peer as well, but that’s another discussion.


  8. I&#39;m really torn about this post. On the one hand Microsoft has repeated one of their most annoying

  9. JohnGalt says:

    4GB limit:

    Simple scenario:  Documents stored in the database, and images.  Why would you do this? First blob access is way faster in SQL Server 2005 so there is no reason to not do this. Especially if you’ve implimented the blob streaming hack in C#. (please put this into the framework properly!)

    Second reason: Security.  Encrypt the database, and volia you don’t have to worry about the documents being left all over the place on the client machine. This isn’t true of web service type solutions such as share point OR VPN where people will copy the files to their desktop and use them there and hten copy them back later.  End result is CIA losing 60 laptops with easily readable information.  OUr solution encrypts the database with NTFS encryption and locks it to just the System Service account so that nothing else, including loginable users can read it and then we lock out everyone but our user from the current instance.  SQLce does this nicely for us in a lot of ways by encrypting the data, thus getting around the problem.

    My comment about the network use being locked out is only as a solution for the 4gb limit.  Remove the limit entirely, and to ensure people don’t use this in enterprise or even workgroup environments simply prevent network users from connecting to the file.  End result is that you don’t have to have any limit at all (there’s no reason for one if only the local machine can connect to it, thus by defintion ensuring only one user) and you get to keep people on the upgrade path to SQL Server 2005 full edition…

    Now if only you guys had a full wrapper for DataAdapters at design time that could just flip a bit and work wtih SQL or SQLce seamlessly then this thing would be a perfect solution.

    If the 4gb limit (or some larger variation of it) stays, then we will definately be forced to look Firebird, or VistaDB because we can’t have a limit and the current licencing for SQL Server 2005 precludes rolling it out to 200 remote users of our system.  I’d rather stay with MS products, hence why I’m pushing this to be completely removed and also why I’m providing you with a solution that serves the same purpose for you. I’m not demanding you have no revenue, just saying that there is a much more flexible way of doing it without killing the entire concept of "Smart Client" in the process.

  10. Steve Lasker says:

    Hi John,

    Just trying to understand what data types are causing you to hit the 4gb limit.  Blob storage has different heuristics compared to lots of rows and it’s great to hear how you’ll your looking to use SQLce.  One of the ways we keep SQLce so small is we have very tight optimizations so we just want to validate we have the right ones in the box.  You can throw just about anything at SQL Server, including Express, and it can usually turn a bad design into a fast query.  But that comes at the cost of a very big, complicated, and extremely powerful query processor and underlying engine.  

    All the points you make about encrypting the database, and adding EFS encryption on top of that are entirely valid, and will continue to be supported, and enhanced.  Storing documents within SQLce is also viable, although I don’t know how much stress testing we’ve done.  I’ll have to check with the perf team.  While I’m checking don’t read this as it’s either not supported, nor something we wouldn’t enhance if there were perf issues.  On devices, large documents just weren’t main stream, so I don’t want to say we’ve nailed that, just yet.  SQLce has been used for years within several Microsoft desktop products, such as Media Center PC, MSN Client, and several Vista applications.  However, all of these scenarios uses relatively small amounts of data.  4gb has never been an issue, so far.

    Again, the current 4gb limit is purely a device optimization that we will definitely remove now that we’re running on larger desktop scenarios.  Unlike SQL Server Express, SQLce isn’t meant as a free entry point to upper SKU’s.  It’s positioned as our default local database and will receive all the necessary enhancements that make it the best product out there.  The 4gb limit isn’t a “free” restriction as we’ve done with Express.  As with most of our Developer focused tools and runtimes, our revenue stream is on the larger platform.  While SQLce could be used stand alone, or even used to sync with Java and Oracle, we hope the overall platform provides a better together story with SQL Server, Windows and Visual Studio.  The limitations that exist in SQLce are more related to how it’s been used, and how do we keep it the lean, mean, local data machine.  Ok, maybe I watched Stripes too much.

    Do you have more then 4gb of data within a database today?  If so, is it unrealistic to use multiple SQLce data files until we remove the 4gb limitation?

    As for the “smart client”, Rich Client, RIA, or any other term, rest assured, Microsoft will play hard in this space, and SQLce, .NET, VS, and several other components will play an important role in leveraging your skills.  Don’t be swayed by the “flash” of Flash.  The picture will come into focus as time evolves.

    Thanks for the info,


  11. [via Steve Lasker] In the beginning it’s SqlCe, then SQL Mobile, and then SQL Server Everywhere,…

  12. Rexiology... says:

    crosspost from http://rextang.net/blogs/work/ [via Steve Lasker ] In the beginning it&#39;s SqlCe, then

  13. So people where just getting used to the name SQL Everywhere and now Microsoft has decided to rename

  14. Byteabyte says:

    Así es, la versión compacta de SQL Server vuelve a cambiar de nombre, al parecer para quedarse con SQL

  15. Question de marketing oblige je pense, SQL Server Everywhere change à nouveau de nom avant sa sortie

  16. Phoenix says:

    Will 3.5 and 4.0 still have the native DLL’s that we can use with ADO under VB6 and VS2003 as we can with SQLev?

  17. Daren says:

    Any news about hosting this in IIS ? A lot of web developers are looking for an Access replacement, they had hopes for Express but it didn’t live up to the promise of xcopy deployment in a shared hosting environment. The new VistaDB looks like it will fill the gap if this doesn’t like John though many prefer to stick with MS products as much as possible.

  18. According to Steve Lasker in this blog post , M$ has gone and renamed SQL Everywhere to SQL Compact Edition

  19. JohnGalt says:

    Using multiple files, while possible is a real nightmare waiting for bugs as far as I can tell. Further the added code to support such a scenario would be rediculous.

    Basically our database system is designed to provide what WinFS was supposed to do. What Desktop search does badly too.  We have highly optimized our queries so that the blobs don’t get in the way, but have provided a single entry point which is completely searchable with complete revision management all in one.  By doing so, we’re able to provide companies with a completely index, referential document management solution that allows any entity, Customer, Project, Appointment, anything to have documents attached to it, both scanned and electronic… both with full indexing and keyword searching as if it was google but without the hogging of resources that desktop search does.

    This provides us, combined with our custom synchronization system, with immediate offsite backup, instant access with complete security managed through a single entry point, anywhere in the world, online of offline.

    Simply: The holly grail of document management, amoung other things that we do that no one else is doing.  Our only limitation right now is that our single secure data store has a 4 gig limit. We have LOTS of customers that have reached that.  They store archetectural drawings all linked directly to a project plan all shared with every team member with security and revision management.  One acad file being 10s of megabytes. It doesn’t take much to fill up 4 gigs of space.  But we’ve also tested with full SQL Server with databases of 100 gigs of documents and it doesn’t slow down the system at all. It’s still instant. As is our integrated email system that shares emails with everyone instead of emailing them around to 50 people all of the time. Simply attach them to a contact, or a project, or anything, it doesn’t matter, and oh btw, you can search on 1 million emails in < 10 seconds for anything you want, anywhere in the system based on your security permissions.  And not just yours, everyone’s that has been shared.

    What we’re looking for is a database engine for our smart client that compliments the server archetecture we have.  In a perfect world there would be a full SQL Server edition that didn’t support network connections (shared memory only) that was free or say $50-100, that we could distribute with our software onto all of the remote machines (network machines obviously just attach directly to the local SQL Server)

    The same synchronization system means that multinationals can have all of their information anywhere in the world and all divisions can work together seamlessly because they all have all of their data… instant disaster protection… and do so without thinking about it. It’s automatic, no VPNs nothing, just a 3x 512 bit encrypted web service, a smart client and a database.  Think P2P for business but with real information that really matters.

    We’re simply waiting for someone to provide us with a solution that is cost effective on the desktop machines to compliment SQL Server on the servers.  SQLce could be that system I think if it is done right and there is no limit, but if there is, then I can’t use it, because it doesn’t buy me anything over SSE (other than easier intial deployment, but with a nasty kicker when they get to 4 gigs).

    This is what the smart client is. This is the reason why Windows Applications should still exist and the web can rule the world… yet. We’re a poster child for this… All I need is a good desktop database…. suggestions?

  20. SQL Server Everywhere becomes Compact

  21. No new software, but a new/old name… The recently renamed SQL Server Everywhere (the successor to SQL

  22. No new software, but a new/old name… The recently renamed SQL Server Everywhere (the successor to SQL

  23. Sean says:

    We’re in about the same situation as you, John, We need a database to satisfy the smart-client needs

    SQL Compact/Express satisifies this, but we know that 4GB will be a barrier since client data will definately (not might, not may, not have the potential to) exceed this in about 5-6 months after deployment.

    I’m with you, partitioning the DB to seperate physical SQL databases to get by the 4GB barrier starts to get frightening.

    We’re also implementing what amounts to our own OCS stack to support the occassionally connected scenario. I was briefly excited about OCS, but coupled with the new knowledge that OCS in SQL Compact isn’t coming for over a year, we’re looking for a DB.

    You mentioned a few of the DB’s we’re looking at: VistaDB, Firebird. DB4O (DB4O.com) is getting alot of buzz and we’re looking into the viability of the company and the potential of the product.

  24. SQLCE goes back to being SQLCE with a different meaning for "CE". I see this as a positive decision….

  25. Chris says:

    SQLce was in platform builder 5.0 catalog. Do you know why CE 6.0 doesn’t have SQLce in the catalog?

  26. JohnGalt says:

    Here’s for no limit on size and go live licences sooner rather than later (i.e. before christmas would be a very good thing)…

    Come ‘on Microsoft, we know you can do it! 🙂

  27. SQL Server Everywhere はSQL Server Compact Edition3.1に再改名(SP+Windows 2000、Vista+使用分野拡張)

  28. Sean says:

    Would be sweet if SQL Compact could auto-partition it’s data under the covers when it exceeded 4GB…

    Go-live licenses for a >4GB DB + OCS would be a heart-shaped box.

  29. Nino.Mobile says:

    Software / Hardware The Windows Live Soapbox team unveils My Mobile Soapbox msmobiles.com gives us the

  30. At Tech Ed EMEA today SQL Server Compact Edition RC1, formerly known as Everywhere edition, was announced

  31. Nino.Mobile says:

    Microsoft has released SQL Server Compact Edition RC1 to the web, along with some tools for VS2005 (

  32. JohnGalt says:

    Does the RC have a limit?  And if it does, can I get a hard commitment from MS that it will be gone for final?

    I’d start making our app use both SQL server and this right away if I knew for sure that I wasn’t going to get screwed on the 4 gig limit….


  33. Gerrit says:

    We also store thousands of documents in the database and use SQL Server CE for single-user installations and SQL Server Express 2005 for multi-user installations. The 4 GB limit is a problem, we are currently compressing the binary document data and then store it in the database. This gives us some breathing room and also can actually improve performance under some conditions. It would be really nice if you could remove the 4 GB limit in SQL Server CE and SQL Server 2005 Express. Otherwise we may have to switch to different databases.


  34. jamome says:

    We are also looking at storing many documents in SQL Server CE, but 4GB is too small for this.

  35. geblack says:

    Will this architecture handle schema changes on the source database? If so, how is this accomplished?

  36. Jayson Go says:

    I’m developing a game browser that will undoubtably require more than 4 GB over time.  What is this the purpose of this limitation on desktop apps?

  37. Dave Holbon says:

    We chose SQL Server CE (or whatever it’s called now) because it’s only going to run on PDA’s linked together in almost real time over the internet. The PDA’s generate all the base data which has to be kept in sync with all the other PDA’s on that particular node with no reference to any central server. The chances of the data exceeding 4gig on a single device are nil as every day when the app boots it backs up yesterday’s data to the SD card. Our problems relating to the application were very specific, that’s why we chose the product.

    Getting the data from the PDA to the companies system (and other PDA’s) is done via the standard cellular phone system which negates any middleware on any PC although a small interface is required.

    Of much interest to me is the remark that “peer-to-peer” was to be implemented in the product as this may enable the removal of substantial amounts of code from the application running in precious memory on the PDA especially in large metropolises with lots of WIFI hotspots and thus remove the need to use the mobile phone network in some scenarios and to enable the use of distributed database designs.

    I’ve often wondered why it was that a version of Access (front end) was never natively linked to SQL CE specifically for use as a bridge between the two environments, as it exists on just about every corporate and small business PC on the Planet and it’s almost impossible not to use it outside of the large central server systems.

    SQL Server CE needs to be kept tight, lean and mean and stable before any changes to its repository size are implemented as to me it’s first and foremost for the mobile market with desktop devices being of secondary consideration only.

  38. Steve Lasker says:

    Hi Dave,

    It’s called SQL Server Compact Edition.  And with the launch yesterday, I think we can finally put the name changes behind us.  

    As for the p2p scenarios, we are definitely looking at enabling p2p with SQLce and the new Sync Platform.  Our initial release is a little more focused on hub/spoke relational type sync, but rest assured, we are expanding on that.  No info on when, so unfortunately, you’ll likely need to keep your code for a bit longer.  As we have more info, I’ll be sure to publish info on it.

    Thanks for the feedback on the focus.  We discuss it quite often,


  39. Steve Lasker says:

    Hi Jason,

    I talked a bit about the 4gb limit here:


    On devices, it was considered more than enough.  We are looking at expanding the limit, but there were enough assumptions in the code based on the 4gb limit that will require additional time before we can expand the limit to something beyond normal limitations on the desktop, or remove it all together.


  40. So SQL Server Compact Edition has been release officially. Remember? It’s that product that…

  41. TomK says:

    Documentation suggests that storing and reading SQLce databases from a network share is possible.  We recently failed accessing a SQLce file on our network from both SQL Server Manager and a .NET project.  SQL Server Manager returned a message box "Cannot connect to X:shared drive… " and "SQL Server Mobile does not support opening database files on a network share."  Note that we were able to open the same .SDF file in both cases when the file was copied locally.

    Are we doing something wrong?

  42. Bob Li says:

    介绍 SQL Server Everywhere 更名的原因和实施情况。

  43. Raul Moratalla says:

    So, what are the main differences between SQL Mobile 2005 and SQL Compact Edition?

    The main page of SQL Compact edition shows some features but doesn’t show differences between version 3.0 and 3.1

    Actually I’m using version 3.0 and it works fine, but should I use version 3.1?

  44. Steve Lasker says:

    Hi Raul,

    The main difference between 3.0 and 3.1 is the desktop licensing change.  If you’re using 3.0, I assume you’re working on devices, which for this release, there isn’t any change.

    For the desktop experience there were several minor changes to round out the desktop experience.  |DataDirectory| support for ClickOnce deployment, ClickOnce bootrapper for VS 2005 deployment.  There was some performance work done to account for the environment differences between the device and desktop.  There’s a good KB article describing the changes here: http://support.microsoft.com/kb/920700

    Hope that helps,


  45. Steve Lasker says:

    Hi Tom,

    Visual Studio and SQL Server Management Studio don’t support network shares, which is a definite bummer.  I actually didn’t realize that, and will see about opening a bug to fix this in Orcas.  

    The SqlCeConnection object does support UNC shares, as well as different extensions.  So, for development with VS and Management Studio, I’m afraid you’ll have to have everything local.


  46. Raul Moratalla says:

    Thanks Steve for the information 🙂

  47. Henrik W H says:

    Sommerferie og interne konferencer (TechReady for nørder og MGX for ikke nørder) er så småt ved ramme

  48. Sommerferie og interne konferencer (TechReady for nørder og MGX for ikke nørder) er så småt ved ramme

  49. Jason says:

    Monday, November 20, 2006 4:35 PM by geblack

    Will this architecture handle schema changes on the source database? If so, how is this accomplished?

  50. tech_tantra says:

    Hi Steve,

    What is the difference between sql server mobile edition 2005 and sqlce 3.0

    Can I use both as a database for my pocket pc based devices.

    Pls do let me know

  51. Steve Lasker says:

    Hi Tech,

    SQL Server 2005 Mobile (aka v3.0) and SQL Server Compact 3.1 are the same product: ++. You could think of SQLce 3.1 as a service pack to SQL Mobile. Since we changed the name to reflect the larger desktop scenarios, we decided to bump the version to .1 as well. Don’t ask, it’s a long story <g>

    3.1 adds bug fixes, applicable to devices, and of course the remove of the desktop restrictions. We added some ClickOnce support for desktop as well.

    So, the short story for devices, is yes, you should think of 3.1 as a service pack. As with service packs, it’s fully backwards compatible.


  52. markovich says:

    Is there a web page describing the differences between SQLCE and SQl Sever Express?

    Honestly, I am a little confused with these two products now.

  53. panayiotis says:

    Is SQL compact going to be release along with Visual Studio 2008 late in Nov 2007?

  54. Steve Lasker says:

    Yup, SQL Server Compact 3.5 will be included within Visual Studio 2008, which Soma announced would be released in November.

    We’ll also be releasing direct to the web, but with the integrated experience, we’ll be within VS as well.


Comments are closed.

Skip to main content