64-bit application running SQL Server Compact

Hi
I have read your article sql-server-compact-4-desktop-app-with...
I have some questions
1: The app I have is 32/64-bit (installer will detect and install). Will 64-bit app work with SQLCE40?
2: The target framework is .NET 4.0. Will this work?
In the entity project of this application, I have included the following files
database.sdf
SQLCE40 (folder)
- amd64 (folder)
- Microsoft.VC90.CRT (folder)
 - Microsoft.VC90.CRT.manifest
 - msvcr90.dll
- sqlceca40.dll
- sqlcecompact40.dll
- sqlceer40EN.dll
- sqlceme40.dll
- sqlceqp40.dll
- sqlcese40.dll
x86 (folder)
- Microsoft.VC90.CRT (folder)
 - Microsoft.VC90.CRT.manifest
 - msvcr90.dll
- sqlceca40.dll
- sqlcecompact40.dll
- sqlceer40EN.dll
- sqlceme40.dll
- sqlceqp40.dll
- sqlcese40.dll
Under references I have,
- System.Data.Entity
- System.Data.SqlServerCe
- System.Data.SqlServerCe.Entity
All these files are taken from
C:\Program Files\Microsoft SQL Server Compact Edition\v4.0\Private
Do I strictly need to follow your example where you copy the 32-bit files to the root level?
app.config
<runtime>
 <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
 <dependentAssembly>
 <assemblyIdentity name="System.Data.SqlServerCe.4.0" publicKeyToken="89845dcd8080cc91" />
 <bindingRedirect oldVersion="4.0.0.0-4.0.0.1" newVersion="4.0.0.1" />
 </dependentAssembly>
 </assemblyBinding>
</runtime>
<entityFramework>
 <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlCeConnectionFactory, EntityFramework">
 <parameters>
 <parameter value="System.Data.SqlServerCe.4.0" />
 </parameters>
 </defaultConnectionFactory>
 <providers>
 <provider invariantName="System.Data.SqlServerCe.4.0" type="System.Data.Entity.SqlServerCompact.SqlCeProviderServices, EntityFramework.SqlServerCompact" />
 <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
 </providers>
</entityFramework>
<system.data>
 <DbProviderFactories>
 <remove invariant="System.Data.SqlServerCe.4.0" />
 <add name="Microsoft SQL Server Compact Data Provider 4.0" invariant="System.Data.SqlServerCe.4.0" description=".NET Framework Data Provider for Microsoft SQL Server Compact" type="System.Data.SqlServerCe.SqlCeProviderFactory,
System.Data.SqlServerCe, Version=4.0.0.1, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
 </DbProviderFactories>
</system.data>

>>
Do I strictly need to follow your example where you copy the 32-bit files to the root level?
No, you can use x86/AMD64 with Entity Framework, but I suggest you use my NuGet package, see my blog post
here:
http://erikej.blogspot.dk/2014/10/entity-framework-6-and-sql-server.html
You should not have references to:
System.Data.Entity and System.Data.SqlServerCe.Entity
Those are not EF version 6 files. Install the package mentioned above, and you will get the correct references.
App.config: EF6 configurastion is missing, again install https://www.nuget.org/packages/EntityFramework.SqlServerCompact.PrivateDeployment/
and things will be right
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

Similar Messages

Build error on EF 6 + SQL Server compact 4.0 privately deployed application

I've been migrating a desktop application from EF4 + SSCE 3.5 into EF6 + SSCE 4.0 and have a problem with running the project
on a machine without SSCE 4.0 installed. I used "Entity Framework 6 & SQL Server Compact 4 (2)–Easy Private Desktop
Deployment" article for instructions how to do that. The project builds and runs ok if the server installed, but when I uninstall it there is a build error occurs, but project runs (although, not all the time :) ).
The error is "The ADO.NET provider with invariant name 'System.Data.SqlServerCe.4.0' is either not registered in the machine or application config file, or could not be loaded."
Config file is:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />

</configSections>
<connectionStrings>
<add name="ADAPTdatabase" connectionString="metadata=res://*/ADAPTmodel.csdl|res://*/ADAPTmodel.ssdl|res://*/ADAPTmodel.msl;provider=System.Data.SqlServerCe.4.0;provider connection string="Data Source=|DataDirectory|\APTdata.sdf"" providerName="System.Data.EntityClient" />
</connectionStrings>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
</startup>
<entityFramework>
<defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlCeConnectionFactory, EntityFramework">
<parameters>
<parameter value="System.Data.SqlServerCe.4.0" />
</parameters>
</defaultConnectionFactory>
<providers>
<provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
<provider invariantName="System.Data.SqlServerCe.4.0" type="System.Data.Entity.SqlServerCompact.SqlCeProviderServices, EntityFramework.SqlServerCompact" />
</providers>
</entityFramework>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Data.SqlServerCe.4.0" publicKeyToken="89845dcd8080cc91" />
<bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.0.1" />
</dependentAssembly>
</assemblyBinding>
</runtime>
<system.data>
<DbProviderFactories>
<remove invariant="System.Data.SqlServerCe.4.0" />
<add name="Microsoft SQL Server Compact Data Provider 4.0"
invariant="System.Data.SqlServerCe.4.0"
description=".NET Framework Data Provider for Microsoft SQL Server Compact"
type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=4.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
</DbProviderFactories>
</system.data>
</configuration>
packages.config created by NuGet:
<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="EntityFramework" version="6.1.0" targetFramework="net45" />
<package id="EntityFramework.SqlServerCompact" version="6.1.0" targetFramework="net45" />
<package id="Microsoft.SqlServer.Compact" version="4.0.8854.1" targetFramework="net45" />
</packages>
Do you know what I'm doing wrong here? I used ObjectContext instead of DBContext. Can i be the cause of the problem?

Remove the runtime section below from app.config
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Data.SqlServerCe.4.0" publicKeyToken="89845dcd8080cc91" />
<bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.0.1" />
</dependentAssembly>
</assemblyBinding>
</runtime>
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

JDBC driver for SQL Server Compact Edition

Hi,
I'm trying to run pc java application on Pocket Pc (Mobile 5.0) with SQL Server Compact edition.
The error message is:
java.lang.UnsatisfiedLinkError: java/sql/DriverManager.getCallerClassLoader()Ljava/lang/ClassLoader;
at java.sql.DriverManager.getConnection(Unknown Source)...
Should I use a special jdbc driver for SQL Server Compact Edition? Is there one?
Mixxo

Hi,
I got an answer from msdn forum:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2307542&SiteID=1.
There is no jdbc driver for SQL Server Compact Edition. OleDB and ADO.net are available. Now I need to know how to use them (in Java)...
Thanks, Mixxo

Any problems if run SQL Server 2005 and Essbase Server on 1 machine?

Hi, I would like to know if there's any problems in terms ofperformance when running SQL Server 2005 and Essbase Server on 1machine? Currently, my users are using Excel File (Lock & Send) toupload data to the Essbase Server and it took about 30 mins perexcel file upload. Application Manager is installed on client's andserver PC for adminstration. Now, I need to implement Datawarehouse and wish to installSQL Server 2005 on the current machine my Essbase Server isrunning. I will need to do simple SQL statements on the SQL Server2005 such as Update, Select, Insert etc. When comes to performance issues, will my current Essbase Serverbe affected? What if 2 users are accessing the Essbase Server andSQL Server at the same time? Will any data be lost in the midst ofextracting data? I hope someone can advise. Appreciate that. Thank you.

<blockquote>quote: <hr>Originally posted by: roy_choy Currently, my users are using Excel File (Lock & Send) to upload data to the Essbase Server and it took about 30 mins per excel file upload. I hope someone can advise. Appreciate that. Thank you.<hr></blockquote> My test server is running both Essbase and SQLServer, but I think that you have a bigger problem. If a lock and send is taking 30 minutes, you are using the wrong technology to load Essbase. You should really consider doing the load using a data load rule. If that isn't the problem, it may be that you are having a real performance problem. If you are moving enough data to require a half hour load, it should be probably be loaded from a text file, or even a spreadsheet, using a data load rule. Text file loads are a bit better than excel, especially when there are formatting issues. Lock and sends are fine for changing parameters and doing adjustments, but heavy duty data loads really work a lot better with load rules.

SQL Server Compact 3.5 Merge Replication With SQL Server 2012 - Causing IIS App Pool to Crash

Hi, I may be the only person in the world doing this but I wanted to give this information to anyone else who may follow this path in the future, and hopefully avoid a headache, or at least a paid support call to Microsoft.
My original scenario was we had a SQL Server 2008 Server using Merge Replication through and IIS (web server) to several Windows Mobile 6 devices. This has worked fairly well for a few years.
Recently we upgraded our SQL server to version 2012 SP 1. After moving the database over to the new server, and re-setting the merge replication stuff, we couldn't get merge replication to work on the Windows Mobile 6 handheld devices. The replication
would appear to start, and then we would get a message saying that the device could not get to the web site. The message on the handheld device was this:
"The IIS service is not available."
After doing some more research, we found that the start of the replication process was causing the Thread Pool that was running the SQLCESA35.dll to crash.
The SQLCESALOG.txt file had this information:
Date Time == SQLCESA Version ==> 3.5.8088.0
Date Time Hr=80004005 ERR:Couldn't find existing RSCB 1
After 2 days of trying to figure out the issue on our own, we gave in and called for paid Microsoft support. They eventually found a known issue where a cumulative update was able to fix the problem.
We installed the update on the IIS server and everything ran smoothly again.
FIX: Merge replication fails when you use SQL Server Compact to perform a merge replication that synchronizes changes with a publisher in SQL Server 2012
http://support.microsoft.com/kb/2845550
Seth O'Neal

Hi sonealtx,
Glad to hear that the issue is resolved. Thanks for your sharing, other community members could benefit from your solution.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Commercial distributed application with SQL Server 2008 back-end

Hi All, I am suffering some confusion and wondered if anyone could clear up a few questions for me.
I am currently developing an application to be sold commercially, to be deployed locally on a customer's site. It is a client-server application and the server utilises an SQL Server 2008 back-end. Client applications however do connect directly to the SQL
Server.
We probably want to support about 100+ client applications. Each client application could feasibly be making several SQL query requests per second.
Firstly, what are the licensing implications of this for the customer? I understand SQL Server 2008 can support 30000+ concurrent connections, but am I correct in thinking that each client application will require CALs? Or I understand there is a "processor
licence"...
Secondly, and I know this is quite a broad question, but can anyone offer a rough estimation of the processing/storage requirements for the server?
Thanks in advance!

Hi click,
Usually, SQL Server is licensed through Microsoft Volume Licensing programs using two software licensing models, one is the Per Processor (Core-based) licensing model, another is Server plus Client Access License (Server+CAL) licensing model which is based
on the users or devices accessing the product.
Using the Per Core Licensing Model When running SQL Server in a physical operating system environment (OSE), all physical cores on the server must be licensed. When licensing SQL Server software under the Server+CAL model, customers purchase a server license
for each server and a client access license (CAL) for each device (Device CAL) and/or user (User CAL) accessing SQL Server or any of its components.
For more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide
to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

[Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
03:32:03:764]:
MainEngineThread is returning 1618
Figure 1: Error -1
<03/03/14 03:32:03>
srsrp.msi exited with return code: 1618
Figure 2: Error -2
Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
the return code means.
ERROR_INSTALL_ALREADY RUNNING
1618
Another installation is already in progress. Complete that installation before proceeding with this install.
KB link:
http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
related Component (Figure 3). The Resource Manager confirms this (Figure 4).
Event Log:
Event ID: 1004
Source: Msinstaller
Level: Warning
Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed. The resource '' does not exist.
Figure 3: Event Log
Figure 4: Resource Manager
Resolution: the error is exactly what the following KB describes.
KB Link:
http://support.microsoft.com/kb/2793634
After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

System.Data.SqlServerCe.SqlCeException (0x80004005): Native components of SQL Server Compact engine are not loaded. Please reinstall Microsoft SQL Server Compact.

Hi
I have followed http://technet.microsoft.com/en-us/library/ms173298(v=sql.110).aspx to support private deployment for my application in anycpu mode.
Though its working fine on several XP and Windows 7 , on on particular XP machine , I get this
System.Data.SqlServerCe.SqlCeException (0x80004005): Native components of SQL Server Compact engine are not loaded. Please reinstall Microsoft SQL Server Compact.
   at System.Data.SqlServerCe.NativeMethods.ThrowIfNativeLibraryNotLoaded()
   at System.Data.SqlServerCe.SqlCeEngine.Dispose(Boolean disposing)
   at System.Data.SqlServerCe.SqlCeEngine.Finalize()
Can anybody give me directions on this?

Do you use LINQ to SQL or EF or ADO.NET, is what
Yes, I would start by investigating:
- Do you REALLY need "any CPU", or can you cope with just x86 to make things simpler (See my LINQ to SQL blog post)
- Is SQL Server Compact installed on this PC, and which build (is it same or different from the one you distribute)
- Use Process Explorer from sysinternals on the machine to find out where the app tries to load the native libraries from (and fails)
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

How to deploy a sql server compact 4.0 in windows xp?

My program is developed by visual basic 6.0 with sql server compact 4.0. How can I deploy it in windows xp sp3?
Should I install .netframework version X in windows xp before sql server compact 4.0 ?
When I copy my program to windows xp and run it , it shows not found provider error.

I you use ADO, the OLEDB provider must be registered. To do the simply install the SQL Server Compact 4.0 SP1 runtime MSI
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

SQL Server Compact Visual C++

Is SQL Server Compact a viable platform for future development? I'm using VS 2010, Native C/C++ and need a good tutorial to walk me through the process of creating a simple db application. Any suggestions?
If SQL Compact is not a viable platform, I would appreciate some direction. My application is very well suited for the 'Compact' single file database with a small number of users. I'm not interested in .NET.
Thanks,
Bob Nichols
Bob Nichols

AFAIK, Microsoft stopped SQL Server Compact development and today SQLite is most used on devices.
It seems that for new application it could be the best choice also portable on other platforms.
Paolo.
Paolo Patierno

Can I use Microsoft SQL Server Management Studio version 11.0 to write SQL queries for "SQL Server Compact 4.0 Local Database"

Hi, Can I use Microsoft SQL Server Management Studio version 11.0 to write SQL queries for "SQL Server Compact 4.0 Local Database" ?
When I use Connect Object Explorer, the "Connect to Server" dialog box which pops up has only 4 selections in the Server Type Drop Down List. They are Database Engine, Analysis Services, Reporting Services & Integration Services. I have read
somewhere that there should be a compact database option. but I do not see it.
What I would like to do is use free form SQL Queries against the tables in "SQL Server Compact 4.0 Local Database" .
Once I have validated these queries, then I will use them in my Visual Studio 2012 C#, ASP.NET application. I created the Local Database using Visual Studio 2012 for use by my application.
Thank you for your help..
diana4

Hello,
With SSMS 2005 we have had the Option to work with SQL CE database files, but not with higher Version of SSMS.
You can use the free SQL CE Toolbax instead; see
http://sqlcetoolbox.codeplex.com/
Olaf Helper
[ Blog] [ Xing] [ MVP]

Accessing typed dataset in SQL Server Compact Toolbox in VS 2013

I am a novice with coding so this could be a very simple answer. I am coding an application in Visual Studio 2013 with VB. I included a Compact SQL Server database using the SQL Server Compact Toolbox add in. The database shows up in my solutions explorer.
I plan on using a typed dataset for my application but when I try to reference the dataset using this code the intellisense doesn't recognize it.
Dim newCustomerRow As DHA_dbDataSet.CustomerRow
My database is named "DHA_db". I am sure there are steps I am missing.
How do I reference the typed dataset so I can add rows and data to it?
Thanks in advance.
Hmm...

The Toolbox (I am the author of it) does not support Typed DataSets (and neither does VS 2013, I believe). You should use LINQ to SQL instead, and the Toolbox supports code generation for this.
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com
Thank you a ton. I started off with an incorrect assumption about the dataset. Your advice and a google search led me to description of how to add a typed DataSet.
http://msdn.microsoft.com/en-us/library/04y282hb.aspx
I like the Toolbox add in. Thanks for authoring it!
Hmm...

Winsock error when running SQL Server Stored Proc

I have a SQL Server stored procedure that is trying to read emails from an IMAP server (I am using mail.dll from www.limilabs.com).
The SP works fine on my local computer/db, and the code also runs fine when run from a console application on my remote server. When I try to run it from SQL Server however I get this error message:
Msg 6522, Level 16, State 1, Procedure GetEmails, Line 0A .NET Framework error occurred during execution of user-defined routine or aggregate "GetEmails": Limilabs.Client.ServerException: The requested name is valid, but no data of the requested type was found ---> System.Net.Sockets.SocketException: The requested name is valid, but no data of the requested type was foundSystem.Net.Sockets.SocketException: at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostAddresses(String hostNameOrAddress) at System.Net.Sockets.Socket.Connect(String host, Int32 port) at Limilabs.Client.ClientBase.Connect(String host, Int32 port, Boolean useSSL)Limilabs.Client.ServerException: at Limilabs.Client.ClientBase.Connect(String host, Int32 port, Boolean useSSL) at StoredProcedures.GetEmails()
I suspect it is something to do with permissions (??) but it is beyond my knowledge of SQL Server. Anyone have some pointers? I am using the IP for the IMAP server, I have switched off the firewall.
Thanks

Reading emails in a stored procedure? Hm...
Unless you are impersonating the actual user in your CLR procedure, the access will be under the service account for SQL Server. If this is Local Servic or similar and may not have the permission or configuration to access whatever System.Net.Dns.InternalGetHostByName
is trying to access.
Try running SQL Server under a domain account to see what happens.
Erland Sommarskog, SQL Server MVP, [email protected]

ASP Website - Web Config provider problem with EF4 / Sql Server Compact 4.0

I am setting up a website which will exchange data with remote Windows Desktop applications and am using SQLCE4.0 and EF4.0 to upload and deserialize an entity to the database with the following code:
Using dc As ContribDataEntities = New ContribDataEntities
 Dim sc As SaleComp = ByteToCSC(comp)
 dc.SaleComps.Add(sc) <-- Exception occurs here
 dc.SaveChanges()
End Using
The exception I get is:
System.Data.Entity.Core.MetadataException was unhandled by user code
HResult=-2146232007
Message=Schema specified is not valid. Errors:
App_Code.ContribData.ssdl(2,2) : error 0152: No Entity Framework provider found for the ADO.NET provider with invariant name 'System.Data.SqlServerCe.4.0'. Make sure the provider is registered in the 'entityFramework' section of the application config file.
See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
Source=EntityFramework
I do not see an entity framework section in my Web.Config, but SqlServerCe.4.0 appears to be there.
Any ideas? Thanks.
-BGood

Thanks, ErikEJ.
Deleting and re-installing the NuGet packages got around the metadata exception, but I am now having a new problem relating to my DateTime database columns. This is described in a separate thread:
http://social.msdn.microsoft.com/Forums/en-US/59befc98-bbd0-4b1a-93a0-f32c94a53b1b/overflow-when-saving-datetime-data-type-in-sql-server-compact-40-with-ef4?forum=sqlce
-BGood

Is SQL Server Compact Dead ?

Hi have a new project that needs a small footprint,t not networked, database for storage and retrieval during desktop program operation (no data needs to be stored after program is closed). This is multithreading program that retrieves web pages asynchronously
puts retrieved data into a temp database and will need to display whatever it has at the moment (even if some requests are not processed yet) in a grid with SQL filtering. Also the PCs that this will run on will be old and I do not want to install
a database server on each one...
So the question is should I use SQL compact or is it currently used by those that already had it in a project ? and no new projects should look at it ?
Thanks
Will access from desktop C# winforms program, using 3.5 maybe 4.x framework.

I also started to worry about this product and everything I have found on the net so far points to SQL Server CE being deprecated. There has been nothing officially announced by Microsoft with the closest being a response to a MS Connect issue:
"SQL Server compact edition is in deprecation mode with no new releases planned near future. Last release SQL CE 4.0SP1 (and earlier releases that are still in the support cycle) will continue to be supported through its lifecycle and Microsoft is committed
to fix any major, production blocking issues found in these releases." (Microsoft Connect)
The mainstream support for CE 4.0 will end on 2016-07-12 and extended support 2021-07-13 unless they release a new service pack, which I see as doubtful (Microsoft
Support).
Support for SSCE has also not been included in Visual Studio 2013 and SQL Server 2014 Management Studio. Erik's SQL Server Compact Toolbox can be used to add support back to VS2013 (CodePlex). SQL
Server CE has even now been removed from the SQL Server website. It still shows up in search results from Microsoft search (Micorsoft)
but sometime back in March or April the page was removed (Wayback Machine).
There are a couple of UserVoice suggestions asking for Microsoft to support and develop SQL Server CE further:
Support Sql Server Compact in VS2013
Sql server Compact 5
So overall even though nothing has been announced it seems pretty clear to me that Microsoft are not continuing development of SQL Server CE and do not want people to use it. It's dead!

64-bit application running SQL Server Compact

Similar Messages

Maybe you are looking for