-->APPLIES TO: SQL Server, including on Linux Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse
![Sql server compact edition download Sql server compact edition download](/uploads/1/2/6/6/126646297/174622279.jpg)
Agree with ErikEJ. And as is mentioned in this article, SQL Server Compact 4.0 is supported until 2016. Currently, besides the SQLite product, you can also use SQL Server Express or SQL LocalDB. LocalDB is created specifically for developers.
A SQL Server Compact connection manager enables a package to connect to a SQL Server Compact database. The SQL Server Compact destination that Microsoft SQL Server Integration Services includes uses this connection manager to load data into a table in a SQL Server Compact database.
Note
On a 64-bit computer, you must run packages that connect to SQL Server Compact data sources in 32-bit mode. The SQL Server Compact provider that Integration Services uses to connect to SQL Server Compact data sources is available only in a 32-bit version.
Configuration the SQL Server Compact Edition Connection Manager
When you add a SQL Server Compact connection manager to a package, Integration Services creates a connection manager that will resolve to a SQL Server Compact connection at run time, sets the connection manager properties, and adds the connection manager to the Connections collection on the package.
The ConnectionManagerType property of the connection manager is set to SQLMOBILE.
You can configure the SQL Server Compact connection manager in the following ways:
- Provide a connection string that specifies the location of the SQL Server Compact database.
- Provide a password for a password-protected database.
- Specify the server on which the database is stored.
- Indicate whether the connection that is created from the connection manager is retained at run time.
You can set properties through SSIS Designer or programmatically.
For information about configuring a connection manager programmatically, see ConnectionManager and Adding Connections Programmatically.
SQL Server Compact Edition Connection Manager Editor (Connection Page)
Use the SQL Server Compact Edition Connection Manager dialog box to specify properties for connecting to a SQL Server Compact database.
To learn more about the SQL Server Compact Edition connection manager, see SQL Server Compact Edition Connection Manager.
Options
Enter the database file name and path
Enter the path and filename for the SQL Server Compact database.
Enter the path and filename for the SQL Server Compact database.
Browse
Locate the desired SQL Server Compact database file by using the Select SQL Server Compact Edition database dialog box.
Locate the desired SQL Server Compact database file by using the Select SQL Server Compact Edition database dialog box.
Enter the database password
Enter the password for the SQL Server Compact database.
Enter the password for the SQL Server Compact database.
SQL Server Compact Edition Connection Manager Editor (All Page)
Use the SQL Server Compact Edition Connection Manager dialog box to specify properties for connecting to a SQL Server Compact database.
To learn more about the SQL Server Compact Edition connection manager, see SQL Server Compact Edition Connection Manager.
Options
AutoShrink Threshold
Specify the amount of free space, as a percentage, that is allowed in the SQL Server Compact database before the autoshrink process runs.
Specify the amount of free space, as a percentage, that is allowed in the SQL Server Compact database before the autoshrink process runs.
Default Lock Escalation
Specify the number of database locks that the SQL Server Compact database acquires before it tries to escalate locks.
Specify the number of database locks that the SQL Server Compact database acquires before it tries to escalate locks.
Default Lock Timeout
Specify the default interval, in milliseconds, that a transaction will wait for a lock.
Specify the default interval, in milliseconds, that a transaction will wait for a lock.
Flush Interval
Specify the interval, in seconds, between committed transactions to flush data to disk.
Specify the interval, in seconds, between committed transactions to flush data to disk.
Locale Identifier
Specify the Locale ID (LCID) of the SQL Server Compact database.
Specify the Locale ID (LCID) of the SQL Server Compact database.
Max Buffer Size
Specify the maximum amount of memory, in kilobytes, that SQL Server Compact uses before flushing data to disk.
Specify the maximum amount of memory, in kilobytes, that SQL Server Compact uses before flushing data to disk.
Max Database Size
Specify the maximum size, in megabytes, of the SQL Server Compact database.
Specify the maximum size, in megabytes, of the SQL Server Compact database.
Mode
Specify the file mode in which to open the SQL Server Compact database. The default value for this property is Read Write.
Specify the file mode in which to open the SQL Server Compact database. The default value for this property is Read Write.
The Mode option has four values, as described in the following table.
Value | Description |
---|---|
Read Only | Specifies read-only access to the database. |
Read Write | Specifies read/write permission to the database. |
Exclusive | Specifies exclusive access to the database. |
Shared Read | Specifies that other users can read from the database at the same time. |
Persist Security Info
Specify whether security information is returned as part of the connection string. The default value for this option is False.
Specify whether security information is returned as part of the connection string. The default value for this option is False.
Temp File Directory
Specify the location of the SQL Server Compact temporary database file.
Specify the location of the SQL Server Compact temporary database file.
Data Source
Specify the name of the SQL Server Compact database.
Specify the name of the SQL Server Compact database.
Microsoft Sql Server Compact Edition 3.5 Sp2 X64
Password
Enter the password for the SQL Server Compact database.
Enter the password for the SQL Server Compact database.
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.
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]
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
Official Name | Common Name |
---|---|
SQL Server 2000 Windows CE Edition | SQL CE 1.0 |
SQL Server 2000 Windows CE Edition | SQL CE 1.1 |
SQL Server 2000 Windows CE Edition | SQL CE 2.0 |
SQL Server 2005 Mobile Edition | SQL CE 3.0 |
SQL Server 2005 Compact Edition | SQL CE 3.1 |
SQL Server Compact 3.5 | SQL CE 3.5 |
SQL Server Compact 4.0 | SQL CE 4.0 |
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]
Filename extension | .sdf |
---|---|
Developed by | Microsoft |
Type of format | Relational database |
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]
![Sql server compact edition download Sql server compact edition download](/uploads/1/2/6/6/126646297/174622279.jpg)
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]
See also[edit]
References[edit]
- ^ ab'Microsoft SQL Server Compact 4.0 is available for download - Microsoft's Embedded Database - SQL Server Compact - Team Blog - Site Home - MSDN Blogs'. Retrieved 2011-03-01.
- ^ abcde'SQL Server 2005 Compact Edition Datasheet'. Archived from the original on 2007-03-16. Retrieved 2007-07-03.
- ^'Search product lifecycle'. Microsoft Support. Retrieved 2017-04-30.
- ^ abcd'A Lap Around SQL Server 2005 Compact Edition'. Retrieved 2005-07-03.
- ^ abcd'SQL Server Everywhere: Just Another Database?'. Retrieved 2007-07-03.
- ^ ab'What's New (SQL Server Compact Edition)'. Retrieved 2007-07-03.
- ^'How do i run SQL Server Compact 3.5 on Windows 8 developer preview?'. social.msdn.microsoft.com. Retrieved 11 March 2013.
- ^'Maintaining Databases (SQL Server Compact Edition)'.
- ^'Transactions (SQL Server Compact Edition)'. Retrieved 2007-07-03.
- ^ ab'Overview of Databases (SQL Server Compact Edition)'. Retrieved 2007-07-03.
- ^'Overview of Databases (SQL Server Compact Edition)'. Retrieved 2007-07-03.
- ^ ab'Data Storage Architecture with SQL Server 2005 Compact Edition'. Retrieved 2007-07-03.
- ^Barranis, Patrick (2013-01-11). 'Port SQL Compact to Windows RT'. Microsoft Connect. Retrieved 2016-06-25.
- ^'Search product lifecycle'. Microsoft Support. Retrieved 2017-04-30.
Bibliography[edit]
External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=SQL_Server_Compact&oldid=917911485'