SQL Server Compact 3.5 SP2 Downloadable Update List
The updates for SQL Server Compact 3.5 SP2 are now referred to a CU (Cumulative Update), which is what the hotfixes also were previously. The difference now is that the CU installation overwrites the existing installation, and a remove of the RTM bits is no longer required before installing the CU.
The table below gives an overview of the current CUs. All CUs apply to SQL Compact 3.5 SP2, version 3.5.8080.0.
|8081||982565||FIX: "An SqlCeParameter with ParameterName '<Parameter Name>' is not contained by this SqlCeParameterCollection" error message when you use the .NET Compact Framework Data Provider for SQL Server Compact to access SQL Server Compact 3.5||x86, x64|
FIX: A Deadlock occurs when two transactions try to perform a DML operation on a table that contains a TABLOCK locking hint or an XLOCK locking hint
|8082||2300599||FIX: Heap corruption occurs when you use SQL Server Compact 3.5 Service Pack 2||x86, x64|
FIX: Some "Image" column content does not open in SQL Server Compact 3.5 SP2 after the "SqlCeEngine.Compact" or "SqlCeEngine.Repair" method is called
FIX:"A call to SQL Server Reconciler failed" error message occurs when you try to add or reinitialize a subscriber of SQL Server Compact 3.5 for a merge publication
|Server Tools only, |
FIX: Incorrect result when you run a query that contains a conjunction and a disjunction in SQL Server Compact 3.5
|8087||2585082||FIX: "A specified value violated the integrity constraints for a column or table" error if the merge publication contains many articles and constraints in SQL Server Compact 3.5||x86, x64|
|8088||2527494||A hotfix is available for SQL Server Compact 3.5 SP2 that adds support for replication with SQL Server "Denali"||x86, x64, Server Tools, WinCE 5,6,7 (?)|
|8089||2665342||Incorrect sort order for a subscriber in SQL Server Compact 3.5 SP2 which synchronizes with a publisher in SQL Server||Server Tools only, |
Please let me know if there are errors or omissions.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)