Microsoft SQL Server Compact (SQL CE) is a compactrelational database produced by Microsoft for applications that run on mobile devices and desktops. Prior to the introduction of the desktop platform, it was known as SQL Server for Windows CE and SQL Server Mobile Edition.

It includes both 32-bit and 64-bit native support.^[1] SQL CE targets occasionally connected applications and applications with an embedded database.^[2] It is free to download and redistribute.^[2] An ODBC driver for SQL CE does not exist, nor is one planned. Native applications may use SQL CE via OLE DB.

SQLite/SQL Server Compact Toolbox: If you use embedded databases like SQLite or SQL Server compact edition for development purposes then this extension will really stand out for you. The extension provides a very convenient to script tables and data, helps in migrating from SQLite or SQL Server Compact to SQL Server (LocalDB/Express) or SQL.

The latest, and last, release is the SQL Server Compact 4.0.^[1] As of February 2013 SQL Server Compact Edition had been deprecated; no new versions or updates are planned, although Microsoft will continue to support until July 2021.^[3]

SQLite & SQL Server Compact Toolbox. A Visual Studio add-in and standalone app, for managing all aspects of your SQL Server Compact/SQLite database files, including generation of code, database diagrams and database documentation. This repository also contains the ExportSqlCe command line tools and scripting API. SQL Compact Toolbox is a third-party tool. The Lansweeper support team cannot troubleshoot potential issues with this tool. Run the Toolbox executable as an administrator on your Lansweeper server. Right-click No SQL Server Compact Data Connections found and choose Add SQL Server Compact. Microsoft SQL Server 2005 Compact Edition Tools for Visual Studio 2005 software updates the Microsoft Visual Studio 2005 SP1 smart device development components with the design time environment. How to use SQL Server Compact 4.0 in Visual Studio 2015 Community (no voice) - ATTENTION - SQL SERVER COMPACT IS NOT INTENDED TO ASP.NET (;( ) - Try differe.

Overview[edit]

SQL Server Compact shares a common API with the other Microsoft SQL Server editions.^[4] It also includes ADO.NET providers for data access using ADO.NET APIs, and built-in synchronization capabilities,^[2] as well as support for LINQ and Entity Framework. Future releases will unify the synchronization capabilities with Microsoft Synchronization Services.^[5] Unlike other editions of Microsoft SQL Server, SQL CE runs in-process^[5] with the application which is hosting it. It has a disk footprint of less than 2 MB and a memory footprint of approximately 5 MB.^[2] SQL CE is optimized for an architecture where all applications share the same memory pool.^[6]Windows Store apps for Windows 8 cannot use SQL Server Compact edition, or any other edition of SQL Server.^[7]

Versions

Visual Studio For Mac Sql Compact Toolbox Windows 10

Support[edit]

SQL CE databases can support ACID-compliance, but do not meet the durability requirement by default because AutoFlush buffers changes in memory (including enlisted ambient transactions and explicit SQL CE transactions that do not override the Commit() call with an CommitMode.Immediate value). Therefore, committed transaction changes can be lost. To meet the durability requirement the commit call on the transaction must specify the immediate flag.^[8] Like Microsoft SQL Server, SQL CE supports transactions, referential integrity constraints, locking as well as multiple connections to the database store.^[4] However, nested transactions are not supported, even though parallel transactions (on different tables) are.^[9] The current release does not support stored procedures^[4] or native XML data type either.^[5] It uses a subset of T-SQL^[2] for querying and due to lack of XML support, XQuery is not supported either.^[5] Queries are processed by an optimizing query processor.^[10] SQL CE databases also support indexing, as well as support remote data replication (local caching of data in remote databases) and merge replication (bidirectional synchronization with master databases).^[11]

SQL CE databases can be created and managed from Microsoft Visual Studio and some older versions of SQL Server Management Studio as well.^[10]

File format[edit]

SQL CE databases reside in a single .sdf file,^[12] which can be up to 4 GB in size.^[4] The .sdf file can be encrypted with 128-bit encryption for data security.^[12] SQL CE runtime mediates concurrent multi-user access to the .sdf file. The .sdf file can simply be copied to the destination system for deployment, or be deployed through ClickOnce. SQL CE runtime has support for DataDirectories.^[6] Applications using an SQL CE database need not specify the entire path to an .sdf file in the ADO.NET connection string, rather it can be specified as |DataDirectory|<database_name>.sdf, defining the data directory (where the .sdf database file resides) being defined in the assembly manifest for the application.^{[citation needed]}

SQL Server Management Studio 2005 can read and modify CE 3.0 and 3.1 database files (with the latest service pack), but SQL Server Management Studio 2008 (or later) is required to read version 3.5 files. Microsoft Visual Studio Express 2008 SP1 can create, modify, and query CE 3.5 SP1 database files. SQL Server Management Studio cannot read CE 4.0 files. Visual Studio 2010 SP1 can handle CE 4.0 database files.^{[citation needed]}

The .sdf ('Sqlce Database File') naming convention is optional, and any extension can be used.^{[citation needed]}

Setting a password for the database file is optional. The database can be compressed and repaired with the option of the compacted/repaired database to be placed into a new database file.^{[citation needed]}

Deprecation[edit]

In February 2013, Microsoft announced that SQL Server Compact Edition had been deprecated.^[13]

Although no new versions or updates are planned, Microsoft will continue to support SQL Compact through their standard lifecycle support policy. This support will end in July 2021.^[14]

Visual Studio For Mac Download

See also[edit]

References[edit]

1. ^ ^ab'Microsoft SQL Server Compact 4.0 is available for download and use with WebMatrix'. Retrieved 2020-03-11.
2. ^ ^abcde'SQL Server 2005 Compact Edition Datasheet'. Archived from the original on 2007-03-16. Retrieved 2007-07-03.
3. ^'Search product lifecycle'. Microsoft Support. Retrieved 2017-04-30.
4. ^ ^abcd'A Lap Around SQL Server 2005 Compact Edition'. Retrieved 2005-07-03.
5. ^ ^abcd'SQL Server Everywhere: Just Another Database?'. Retrieved 2007-07-03.
6. ^ ^ab'What's New (SQL Server Compact Edition)'. Retrieved 2007-07-03.
7. ^'How do i run SQL Server Compact 3.5 on Windows 8 developer preview?'. social.msdn.microsoft.com. Retrieved 11 March 2013.
8. ^'Maintaining Databases (SQL Server Compact Edition)'.
9. ^'Transactions (SQL Server Compact Edition)'. Retrieved 2007-07-03.
10. ^ ^ab'Overview of Databases (SQL Server Compact Edition)'. Retrieved 2007-07-03.
11. ^'Overview of Databases (SQL Server Compact Edition)'. Retrieved 2007-07-03.
12. ^ ^ab'Data Storage Architecture with SQL Server 2005 Compact Edition'. Retrieved 2007-07-03.
13. ^Barranis, Patrick (2013-01-11). 'Port SQL Compact to Windows RT'. Microsoft Connect. Retrieved 2016-06-25.
14. ^'Microsoft SQL Server Compact 4.0 Support Dates'. Retrieved 2020-09-17.

Bibliography[edit]

External links[edit]

Sql Management Studio For Mac

Looks like there is some sort of bug with the install program for the Visual Studio Tools. The error message says that some required component is missing, or that there is an version conflict. There is a fix for this posted at the MSDN Forums by Ginny Caughey, I’ll repeat it here:

Ms Sql Toolbox

Install sqlmobile30devtoolsenu.msi from the Visual Studio install media, located in the folder: vswcuSQLCE first. Then the CE tools will install.

I had this problem, and it was probably because I uninstalled the SQL Server Mobile Edition tools first. This seems to be a bug from Microsoft in that it requires the previous version of the database or that the uninstaller simply uninstalls too much.

The reason I uninstalled the Mobile Editon tools was because it showed up in the datasource list in Visual Studio. After installing the .msi file above, and installing the CE Tools – everything looks right in Visual Studio finally.