SQL Server Compact - Compact & Capable : Release

SQL CE Binaries - Details

laxminro — Wed, 07 Oct 2009 11:27:00 GMT

Many times developers get puzzled on which exact set of binaries one should consume in their application. There is also a misconception that SQL CE engine is too big in size. This may be because there was no effort from our side to clarify on “Which binary is for what purpose?”.

In an effort to get clarity in these aspects, I have published a blog post on my blog. Please do read and provide your comments.

Thanks,

Laxmi Narsimha Rao Oruganti

Released - SQL Server Compact v3.5 SP1, SQL Server 2008 RTM, Visual Studio 2008 SP1, .NET Framework v3.5 SP1

laxminro — Wed, 13 Aug 2008 17:37:00 GMT

Yes, all of them are released on August 11, 2008.

SQL Server Compact v3.5 SP1:

What is new in this Service Pack? - Click here and here

Where to download?

SQL Server Compact v3.5 SP1 for Desktops (32-bit and 64-bit)

SQL Server Compact v3.5 SP1 for Devices (all platforms & processors)

Server Tools (32-bit and 64-bit) (See Also: this)

Documentation, Books Online

Visual Studio 2008 SP1

What is new in this Service Pack? - Click here

Where to download? - Click here

.NET Framework v3.5 SP1 - Download it here

SQL Server 2008 RTM - Click here

The good thing is with VS 2008 SP1, you will get "SQL Server Compact SP1 for Desktop (32-bit)", and of course updated "SQL Server Compact SP1 Design Tools".

We received a huge feedback from you on VS 2005 SP1 that we should limit the Service Pack Size. With that feedback, we felt it is a reasonable to ask customers to download "SQL Server Compact v3. SP1 for Devices" explicitly than including it with Visual Studio 2008 SP1 there by bloating VS 2008 SP1 size. We also made a decision to not include "SQL Server Compact v3.5 SP1 for Desktops (64-bit)" so as to make sure we do not trouble all VS 2008 SP1 customers.

What about Platform Builder Updates?

Platform Builder 5.0 and 6.0 Updates for SQL Server Compact v3.5 SP1 are also released to Platform Builder team and they should be available in the next Platform Builder 5.0 and 6.0 Update. I will update this blog post with the download URL soon after they are available.

Windows CE 5.0 Platform Builder Monthly Update (July 2008) - Download it here

Windows Embedded CE 6.0 Platform Builder Monthly Update (July 2008) - Download it here

Thanks,

Laxmi Narsimha Rao Oruganti

Download available for SQL Server Compact 3.5 SP1 Beta for ADO.Net Entity Framework Beta 3

SQLCEBLOG — Thu, 21 Feb 2008 09:30:00 GMT

The SQL Server Compact 3.5 SP1 Beta for ADO.Net Entity Framework Beta 3 is available for download at Microsoft Download Center.

To install SQL Server Compact 3.5 SP1 Beta Release for ADO.NET Entity Framework Beta 3

Install ADO.NET Entity Framework Beta 3 from Microsoft Download Center. You must ensure that the pre-requisites specified on the download page are installed before installing ADO.NET Entity Framework Beta 3.
In Control Panel, double-click Add or Remove Programs. Uninstall SQL Server Compact 3.5 or SQL Server Compact 3.5 SP1 Beta.
Install SQL Server Compact 3.5 SP1 Beta Release for the ADO.NET Entity Framework Beta 3 (SSCERuntime-ENU.msi) from the Microsoft Download Center. Note that administrator rights are required on a computer to install SQL Server Compact 3.5 SP1 Beta Release for ADO.NET Entity Framework Beta 3.

To install ADO.NET Entity Framework Tools December 07 Community Technology Preview (CTP)

Install the ADO.NET Entity Framework Beta 3 and SQL Server Compact 3.5 SP1 Beta Release for the ADO.Net Entity Framework Beta 3 as specified above. Install ADO.NET Entity Framework Tools December 2007 CTP from the Microsoft Download Center. You must ensure that the pre-requisites specified on the download page are installed before installing ADO.NET Entity Framework Tools December 2007 CTP. The CTP installs on a Visual Studio 2008 installation.
Copy the SQL Server Compact 3.5 SP1 Design Tools Beta (SSCEVSTools-ENU.exe) to your computer by clicking on Save or Save this program to disk and after the download is complete install SSCEVSTools-ENU.exe by double-clicking it. Do not install the SSCEVSTools-ENU.exe by clicking on the Run. While running the SSCEVSTools-ENU.exe file, Microsoft.SqlServerCe.Client.dll is extracted to %ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE folder. The SSCEVSTools-ENU.exe will create a backup of the existing DLL at the location %ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE.

For uninstalling SQL Server Compact 3.5 SP1 Beta refer to the read me.

The steps to create a sample application are as given below:

1. Start Visual Studio 2008 and create a console project by clicking on the menu item File à New à Project. In the New Project window expand Visual Basic or Visual C#, select Windows and then select Console Application. For the project the .Net Framework version should be .Net Framework 3.5. Name the project as SQLCompactEDMProject. On clicking OK the project is created

2. To generate the Entity Data Model for the Northwind.sdf, copy the Northwind.sdf from the folder %Program Files%\Microsoft SQL Server Compact Edition\v3.5\Samples to the users folder like C:\Users\<login name>\Documents\Visual Studio 2008\Projects\SQLCompactEDMProject\SQLCompactEDMProject. Select the SQLCompactEDMProject in the Solution Explorer and right-click, point to Add, and then click New Item. Select ADO.NET Entity Data Model in the Templates pane. Enter Northwind.edmx for the model name and click Add. The opening page of the Entity Data Model Wizard is displayed.

3. Select Generate from database in the Choose Model Contents dialog box and click Next. Click the New Connection button. The Connection Properties dialog box is displayed.

4. In the Connection Properties dialog click the button Change in the Data Source. In the Change Data Source dialog box select Microsoft SQL Server Compact 3.5 and click OK. Click the radio button My Computer in the Data Source. In the Connection Properties browse to the Northwind.sdf and click OK in the Connection Properties dialog. The Choose Your Data Connection screen in the Entity Data Model Wizard comes up.

5. The checkbox in front of Save entity connection settings in App.Config as: will be clicked by default. Change the name in the dialog from Entities to NorthwindEntities. Click Next to continue.

6. The Choose Your Database Objects dialog box is displayed. By default all the tables in the database are selected and will be included in the EDM. Uncheck the box next to Tables. This deselects all the tables in the database. Expand the Tables node and select the Customers, Orders, and Products tables. Change the Model Namespace: from Model to NorthwindModel

7. Click Finish to complete the wizard.

a. The wizard does the following:

b. Adds references to the System.Data, System.Data.Entity, System.Core, System.Security, and System.Runtime.Serialization assemblies.

c. Generates an .edmx file which encapsulates the information from the EDM mapping files.

d. Creates an App.Config file.

8. Double click the App.Config file in the Solution Explorer to open it. Change the provider entry from provider=Microsoft.SqlServerCe.Client.3.5 to provider=System.Data.SqlServerCe.3.5

9. Add an Imports (Visual Basic) or using (C#) statement at the beginning of the file to reference the EDM created from the Northwind database. (The name of the model corresponds to the value of the namespace attribute in your .edmx file).

Visual Basic

Imports SQLCompactEDMProject.NorthwindModel

using NorthwindModel;

10. Add the following code to the Main subroutine (Module1.vb or Program.cs)

Visual Basic

Using db As NorthwindEntities = New NorthwindEntities

Dim customers = From c In db.Customers _

Where c.City = "London" _

Order By c.Company_Name Select c

For Each c As Customers In customers

Console.WriteLine(c.Company_Name)

Console.ReadLine

End Using

using (NorthwindEntities db = new NorthwindEntities())

{

var customers = from c in db.Customers

where c.City == "London"

orderby c.Company_Name

select c;

foreach (Customers c in customers)

{

Console.WriteLine(c.Company_Name);

}

Console.ReadLine ();

}

11. Press CTRL+F5 to run the application. After the results display on the console screen press enter to exit the application

For more information and samples please see the ADO.NET Entity Framework Beta 3 Documentation and ADO.NET Entity Framework Samples

Regards,

Ambrish Mishra

Program Manager - SQL Server Compact

SQL Server Compact Release Versions

Laxmi Narsimha Rao ORUGANTI — Fri, 08 Feb 2008 17:41:00 GMT

This blog post is meant to give different build version numbers of our SQL Server Compact Releases. This blog post is a living one and gets updated for every release we make.

Before getting into the mapping, first you want to know the version you are having. There are multiple means:

Registry: HKLM\Software\Microsoft\Microsoft SQL Server Compact Edition\*\DesktopRuntimeVersion

File Properties: Check file properties of some SQL CE DLL and check for "File version" the first line of version tab

Product Name	Release Vehicle	Version
SQL Server 2005 Mobile Edition	Visual Studio 2005 RTM	3.0.5206
SQL Server 2005 Mobile Edition	SQL Server 2005 RTM	3.0.5207
SQL Server 2005 Compact Edition	Visual Studio 2005 SP1	3.0.5300
SQL Server 2005 Compact Edition	SQL Server 2005 SP2	3.0.5300
SQL Server 2005 Compact Edition	Download Center	3.0.5300
SQL Server 2005 Compact Edition	Windows Mobile 6.0	3.0.5289
SQL Server Compact 3.5 Beta1	Visual Studio 2008 Beta1	3.5.5339
SQL Server Compact 3.5 Beta2	Visual Studio 2008 Beta2	3.5.5365
SQL Server Compact 3.5 RTM	Visual Studio 2008 RTM	3.5.5386
SQL Server Compact 3.5 RTM	Download Center	3.5.5386
SQL Server Compact 3.5 SP1 Beta	SQL Server 2008 CTP5 OR SQL Server 2008 Nov07 CTP	3.5.5608
SQL Server Compact 3.5 SP1 Beta for ADO.NET Entity Framework Provider Beta	Download Center	3.5.5626
SQL Server Compact 3.5 SP1 Beta	SQL Server 2008 CTP6 OR SQL Server 2008 Feb08 CTP	3.5.5626
SQL Server Compact 3.5 SP1 RTM	Visual Studio 2008 SP1 RTM	3.5.5692
SQL Server Compact 3.5 SP1 RTM	SQL Server 2008 RTM	3.5.5692
SQL Server Compact 3.5 SP1 RTM with .NET Framework 4 Beta Support	Visual Studio 2010 Beta 1	3.5.5802
SQL Server Compact 3.5 SP2 Beta	Microsoft Visual Studio 2010 and .NET Framework 4 Beta 2	3.5.8044
SQL Server Compact 3.5 SP2 Beta	SQL Server Compact 3.5 SP2 Beta for Windows Desktop Web Download	3.5.8049

Update: This information is now available as a KB Article 950550. The KB article list only the final release versions and not beta/CTP/alpha versions.

Thanks,

Laxmi Narsimha Rao ORUGANTI

Connectivity Cross Version Compatibility (SQL Server Compact 3.5)

Laxmi Narsimha Rao ORUGANTI — Wed, 19 Dec 2007 03:47:00 GMT

Connectivity Cross Version Compatibility

This blog post explains the Merge Replication connectivity cross version compatibility scenarios for the SQL Server Compact 3.5 release. For more information about the connectivity cross version compatibility scenarios in SQL Server Compact 3.1, see SQL Server Compact 3.1 Connectivity Tools.

This post is not applicable/refer-to Sync Services for ADO.NET. Please refer to this post by Mr. Steve Lasker to know the differences between Sync Services for ADO.NET and Merge Replication.

Product Version Information:

The following table demonstrates the product names and code names used throughout this blog post.

Version	Product Official Name(s)	Product Codename	Nickname
Client 2.0	SQL Server 2000 for Windows CE SQL Server Compact 2.0	<None>	SQL CE 2.0
Client 3.0	SQL Server 2005 Mobile Edition SQL Server Compact 3.0	<None>	SQL CE 3.0
Client 3.1	SQL Server 2005 Compact Edition SQL Server Compact 3.1	<None>	SQL CE 3.1
Client 3.5	SQL Server Compact 3.5	<None>	SQL CE 3.5
Server 8.0	SQL Server 2000	Shiloh	SQL Server 8.0
Server 9.0	SQL Server 2005	Yukon	SQL Server 9.0
Server 10.0	SQL Server 2008	Katmai	SQL Server 10.0

Summary:

1) SQL Server Compact 3.5 can synchronize with only SQL Server 2005 not with SQL Server 2000.

2) SQL Server Compact 3.5 Server Tools package enables synchronization between SQL Server Compact client versions 3.0, 3.1, and 3.5 and SQL Server 2005 through SQL Server Compact3.5 IIS components.

3) SQL Server Compact 3.5 SP1 can synchronize with both SQL Server 2005 and SQL Server 2008.

4) SQL Server Compact 3.5 SP1 Server Tools package enables synchronization between SQL Server Compact client versions 3.0, 3.1, 3.5 and SQL Server 2008 through SQL Server Compact 3.5 SP1 IIS components.

Server Tools Release Plan:

Our release plan for server tools package is as follows: In Phase1, we are releasing SQL Server Compact 3.5 Server Tools package for SQL Server 2005 (Yukon) and SQL Server Compact 3.5 SP1 Beta Server Tools package for SQL Server 2008 (Katmai). In Phase2, we will release the SQL Server Compact 3.5 SP1 Server Tools package for both SQL Server 2005 (Yukon) and SQL Server 2008 (Katmai). This new package will replace the Phase 1 packages.

Important:

This blog post does not describe the following deployment scenarios:

1) Upgrading clients from SQL Server Compact version 2.0 to versions 3.0 and 3.1

2) Upgrading from SQL Server 2000 to SQL Server 2005

3) Mixed installations including SQL Server compact client versions 2.0, 3.0, 3.1 and SQL Server or publisher versions SQL Server 2000 (8.0), and SQL Server 2005 (9.0)

For more information about these deployment scenarios, please see SQL Server Compact 3.1 Connectivity Tools documentation.

General Information for Deployment:

1) You can always install SQL Server Compact client versions 3.0 and 3.5 side-by-side.

2) The version of SQL Server IIS components must be equal to or lesser than the version of SQL Server Publisher.

3) You can install the SQL Server IIS components side-by-side . When installing side-by-side, the SQL Server IIS components should be in two different physical and virtual directories.

4) SQL Server IIS components and SQL Server Compact IIS components reside in IIS server.

5) You can install the SQL Server IIS components from the SQL Server Installation CD. In feature selection page, choose Shared Features, and then Client Tools to install the SQL Server IIS components.

The new rules that apply only to SQL Server Compact v3.x:

1) The version of SQL Server Compact v3.x client components must be equal to or lesser than the version of SQL Server Compact v3.x IIS components. In other words, SQL Server Compact 3.0 client can connect to 3.0, 3.1, 3.5 IIS components. SQL Server Compact 3.1 client can connect to 3.1, 3.5 IIS components. SQL Server Compact 3.5 client can connect to 3.5 IIS components.

2) SQL Server Compact 3.x IIS Components are not side-by-side installable.

1 Cross Version Compatibility

1.1 Cross Version Compatibility Support Matrix

The following table provides the cross version compatibility support for each different type of deployment scenario. The table includes:

· “Dx”: An identifier for each different scenario.

· “Existing Support”: A deployment that is already supported. For more information, see SQL Server Compact 3.1 Connectivity Tools.

· “New Support”: A new supported deployment. This new deployment is explained in this blog post later.

· “Pending Support”: Specifies that SQL Server Compact 3.5 RTM does not support synchronization to SQL Server 2008 but this support will be enabled in SQL Server Compact 3.5 SP1.

Deployment Scenario No	SQL Server Compact Client Version	SQL Server Publisher Version	Supported (Yes/No)	Notes
D1	2.0	N/A	N/A	N/A
D2	3.0/3.1	SQL Server 2000 SP3a or later	Yes	Existing Support
D3	3.0/3.1	SQL Server 2005	Yes	Existing Support
D4	3.0/3.1	SQL Server 2008	Yes	New Support
D5	3.5 RTM or later	SQL Server 2000	No	Retired/Deprecated
D6	3.5 RTM or later	SQL Server 2005	Yes	New Support
D7	3.5 RTM	SQL Server 2008	No	Pending Support
D8	3.5 SP1 or later	SQL Server 2008	Yes	New Support

SQL Server version--à	SQL Server 2000	SQL Server 2005	SQL Server 2008
SQL Server Compact Version ↓	SQL Server 2000	SQL Server 2005	SQL Server 2008
2.0	Old	Old	Not Supported
3.0/3.1	Old	Old	New
3.5 RTM	Not Supported	New	Not Supported
3.5 SP1 or later	Not Supported	New	New

1.2 Compatibility with SQL Server and IIS components

The following table summarizes the compatibility with SQL Server Compact, SQL Server and server IIS components. For more information, see Section 2 Deployment Scenarios. This section requires thorough understanding of Merge Replication deployment.

SQL Server Compact Client Version	SQL Server Compact IIS Components Version	SQL Server IIS Components Version	SQL Server Publisher Version
2.0	N/A	N/A	N/A
3.0/3.1	3.1	8.0	8.0
3.0/3.1	3.1	9.0	9.0
3.0/3.1	3.5 SP1+	10.0	10.0
3.5 RTM+	N/A	N/A	8.0
3.5 RTM+	3.5 RTM+	9.0	9.0
3.5 RTM	N/A	N/A	10.0
3.5 SP1+	3.5 SP1+	10.0	10.0

2 Deployment Scenarios

This section describes how to upgrade the existing deployment and how to set up a new deployment. In addition, this section also describes how to setup a deployment of the mixed subscribers.

The mixed subscribers represent the SQL Server Compact clients that are of different versions. For example, a single deployment might have different versions of SQL Server Compact clients connecting to the same SQL Server Publisher through either same or different IIS servers. In this case, these SQL Server Compact clients are called as mixed subscribers. For more information on how to configure the IIS Server Environment, see http://msdn2.microsoft.com/en-us/library/ms172441(SQL.100).aspx.

Note: SQL Server Compact includes a connectivity wizard, "Configure Web Synchronization Wizard", which helps you configure a virtual directory in Internet Information Services (IIS). Whenever a virtual directory URL is changed, you need to update the Virtual Directory Information to refer to a new URL. For more information about how to do this, see http://msdn2.microsoft.com/en-us/library/ms172450(SQL.100).aspx and http://msdn2.microsoft.com/en-us/library/ms171862(SQL.100).aspx. You also need to update the clients to point to this new URL.

2.1 New Deployment

This section describes how to set up a new deployment for the new deployment scenarios introduced with SQL Server Compact 3.5 and/or SQL Server 2008.

2.1.1 SQL Server Compact 3.5 RTM+ and SQL Server 2005 (D6)

1) Install SQL Server 2005 on a Publisher computer

2) Install SQL Server Compact 3.5 RTM+ on a client computer

3) Install SQL Server 2005 IIS Components on IIS server

4) Install SQL Server Compact 3.5 RTM+ Server Tools Package on IIS server

5) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.1.2 SQL Server Compact versions 3.0 or 3.1 and SQL Server 2008 (D4)

1) Install SQL Server 2008 on a Publisher computer

2) Install SQL Server Compact versions 3.0 and 3.1 on a client computer

3) Install SQL Server 2008 IIS Components on IIS server

4) Install SQL Server Compact 3.5 SP1+ Server Tools Package on IIS server

5) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.1.3 SQL Server Compact 3.5 SP1+ and SQL Server 2008 (D8)

1) Install SQL Server 2008 on a Publisher computer

2) Install SQL Server Compact 3.5 SP1+ on a client computer

3) Install SQL Server 2008 IIS Components on IIS server

4) Install SQL Server Compact 3.5 SP1+ Server Tools Package on IIS server

5) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2 Upgrading an Existing Deployment (Full)

2.2.1 Server Upgrade Only: from SQL Server 2000 or 2005 to SQL Server 2008

2.2.1.1 SQL Server Compact version 2.0 clients

This scenario is not supported. In this case, clients must be upgraded along with the server.

2.2.1.2 SQL Server Compact versions 3.0 and 3.1 clients

1) Upgrade SQL Server

2) Retain SQL Server versions 3.0 and 3.1 on a client computer

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server

4) Optionally uninstall SQL Server 2000/2005 IIS Components on IIS server

5) Remove the SQL Server Compact 3.1 Server Agent ISAPI Virtual Directories

6) Install SQL Server 2008 IIS Components on IIS server

7) Install SQL Server Compact 3.5 SP1+ Server Tools Package on IIS server

8) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2.2 Client Upgrade Only

2.2.2.1 Upgrade from SQL Server Compact 2.0 to SQL Server Compact 3.5

2.2.2.1.1 SQL Server 2000

This scenario is not supported. In this case, the server must be upgraded.

2.2.2.1.2 SQL Server 2005

1) Upgrade SQL Server Compact clients

2) Retain SQL Server on a Server computer

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server (if any)

4) Uninstall SQL Server Compact 2.0 Server Tools Package on IIS server

5) Optionally uninstall SQL Server 2000 IIS Components on IIS server

6) Install/Retain SQL Server 2005 IIS Components on IIS server

7) Remove the SQL Server Compact 2.0 Server Agent ISAPI Virtual Directories

8) Install SQL Server Compact 3.5 RTM+ Server Tools Package on IIS server

9) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2.2.2 Upgrade from SQL Server Compact versions 3.0 and 3.1 to SQL Server Compact 3.5

2.2.2.2.1 SQL Server 2000

This scenario is not supported. In this case, the server must be upgraded along with the clients.

2.2.2.2.2 SQL Server 2005

1) Upgrade SQL Server Compact Clients

2) Retain SQL Server on a Server computer

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server

4) Retain SQL Server 2005 IIS Components on IIS server

5) Remove the SQL Server Compact 3.1 Server Agent ISAPI Virtual Directories

6) Install SQL Server Compact 3.5 RTM+ Server Tools Package on IIS server

7) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2.2.2.3 SQL Server 2008

This deployment scenario describes an incremental upgrade where servers are upgraded from SQL Server 2000 or 2005 to SQL Server 2008 as described in section 2.2.1.2 above and then clients are getting upgraded. This deployment scenario might be useful in some cases where you might choose to upgrade the servers first and then the clients.

1) Upgrade SQL Server Compact clients

2) Retain SQL Server on a Server computer

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server

4) Retain SQL Server 2008 IIS Components on IIS server

5) Remove the SQL Server Compact 3.1 Server Agent ISAPI Virtual Directories

6) Install SQL Server Compact 3.5 SP+ Server Tools Package on IIS server

7) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2.3 Client and Server Upgrade in Parallel

2.2.3.1 SQL Server Compact Clients: from 2.0 to 3.5, SQL Servers: from 2000 to 2005

1) Upgrade SQL Server Compact clients

2) Upgrade SQL Server

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server (if any)

4) Uninstall SQL Server Compact 2.0 Server Tools Package on IIS server

5) Uninstall SQL Server 2000 IIS Components on IIS server (optional)

6) Remove the SQL Server Compact 2.0 Server Agent ISAPI Virtual Directories

7) Install SQL Server 2005 IIS Components on IIS server

8) Install SQL Server Compact 3.5 RTM+ Server Tools Package on IIS server

9) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2.3.2 SQL Server Compact Clients: from 2.0 to 3.5, SQL Servers: from 2000 or 2005 to 2008

1) Upgrade SQL Server Compact clients

2) Upgrade SQL Server

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server (if any)

4) Uninstall SQL Server Compact 2.0 Server Tools Package on IIS server

5) Uninstall SQL Server 2000/2005 IIS Components on IIS server (optional)

6) Remove the SQL Server Compact 2.0 Server Agent ISAPI Virtual Directories

7) Install SQL Server 2008 IIS Components on IIS server

8) Install SQL Server Compact 3.5 SP1+ Server Tools Package on IIS server

9) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2.3.3 Server Compact Clients: from versions 3.0 or 3.1 to 3.5, SQL Server versions: from 2000 to 2005

1) Upgrade SQL Server Compact clients

2) Upgrade SQL Server

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server

4) Uninstall SQL Server 2000 IIS Components on IIS server (optional)

5) Remove the SQL Server Compact versions 3.0 or 3.1 Server Agent ISAPI Virtual Directories

6) Install SQL Server 2005 IIS Components on IIS server

7) Install SQL Server Compact 3.5 RTM+ Server Tools Package on IIS server

8) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.2.3.4 Server Compact Clients: from versions 3.0 or 3.1 to 3.5, SQL Server versions: from 2000 or 2005 to 2008

1) Upgrade SQL Server Compact clients

2) Upgrade SQL Server

3) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server

4) Uninstall SQL Server 2000/2005 IIS Components on IIS server (optional)

5) Remove the SQL Server Compact version 3.0/3.1 Server Agent ISAPI Virtual Directories

6) Install SQL Server 2008 IIS Components on IIS server

7) Install SQL Server Compact 3.5 SP1+ Server Tools Package on IIS server

8) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

2.3 Mixed Deployments

Mixed deployments might be due to choice or due to an incremental upgrade, etc. This section describes how to setup IIS server in mixed deployment scenarios and in what cases multiple IIS servers are required.

The scope of mixed subscribers in this section is limited to the SQL Server Compact subscribers of multiple versions. In other words, this section explains only mixed of versions of SQL Server Compact clients. This section does not explain the mixed deployment scenarios including different types of subscribers such as SQL Server Compact subscriber and SQL Express subscribers together.

2.3.1.1 SQL Server Compact Client versions: 2.0, 3.5; SQL Server versions: Any

This deployment scenario describes a deployment, which might include SQL Server Compact 2.0 or 3.5 subscribers and any version of SQL Server publishers.

SQL Server Compact 2.0 and 3.5 cannot be subscribers to the same publisher even with different publications. This combination is not supported. Either SQL Server Compact 2.0 subscribers must be upgraded to SQL Server Compact versions 3.0 or 3.1 or 3.5, or there must be different publishers for different SQL Server Compact clients in the deployments.

If there are different publishers; you should make sure to have different IIS servers configured.

For more information about how to setup two completely disjoint parallel deployments, please see New Deployment.

2.3.1.2 SQL Server Compact Client versions: 2.0, 3.0 or 3.1; SQL Server versions: Any

SQL Server Compact 2.0 cannot be a subscriber to SQL Server 2008; therefore this deployment cannot be a valid mixed deployment. For more information about this kind of mixed deployment, see SQL Server Compact 3.1 Connectivity Tools.

2.3.1.3 SQL Server Compact Client versions: Any; SQL Server versions: 2000, 2008

This deployment scenario describes a deployment, which might include SQL Server Compact 2.0 or 3.0 or 3.1 or 3.5 subscribers and SQL Server 2000 or 2008 publishers.

Important: SQL Server Compact 3.5 cannot be a subscriber to SQL Server 2000 publisher.

If there are different publishers and different sets of subscribers, you should make sure to have different IIS servers configured. In this case, you might need separate set of deployments, such as:

· Subscriber Set1 merge replicates through IIS Server1 with SQL Server1

· Subscriber Set2 merge replicates through IIS Server2 with SQL Server2

Note that this deployment scenario is not a mixed deployment but it is much more similar to the two completely disjoint parallel setups which can be configured as specified in section New Deployment above.

2.3.1.4 SQL Server Compact client versions: 3.0, 3.1, 3.5; SQL Server versions: 2005, 2008

In this deployment scenario, one IIS server can serve all the SQL Server Compact subscribers with or without multiple publishers in the deployment. Note that SQL Server Compact 3.5 IIS Components can connect to any SQL Server Compact version 3.x client component. Therefore, a single SQL Server Compact 3.5 Server Agent URL can be used by all SQL Server Compact version 3.x Clients.

Note that when using SQL Server 2008 as a Publisher, the SQL Server Compact 3.5 IIS components must be of version 3.5 SP1 or greater.

To setup this kind of mixed deployment, you should follow these steps:

1) Upgrade clients and servers (if necessary)

2) Uninstall SQL Server Compact 3.1 Server Tools Package on IIS server (if any)

3) Uninstall SQL Server Compact 2.0 Server Tools Package on IIS server (if any)

4) Uninstall SQL Server 2000 IIS Components on IIS server (optional)

5) Remove the SQL Server Compact 2.0 Server Agent ISAPI Virtual Directories

6) Remove the SQL Server Compact versions 3.0/3.1 Server Agent ISAPI Virtual Directories

7) Install/Retain SQL Server 2005 IIS Components on IIS server(if any publisher is SQL Server 2005)

8) Install/Retain SQL Server 2008 IIS Components on IIS server(if any publisher is SQL Server 2008)

9) Install SQL Server Compact 3.5 RTM+ Server Tools Package on IIS server(if all publishers are SQL Server 2005)

10) Install SQL Server Compact 3.5 SP1+ Server Tools Package on IIS server(if any publisher is SQL Server 2008)

11) Configure Web Synchronization with SQL Server Compact 3.5 Server Agent ISAPI

You might choose to configure multiple IIS servers for different set of publisher and subscriber combinations. If you do that, this case cannot be a mixed deployment anymore. It would be much similar to two completely disjoint parallel setups which can be configured as specified in section New Deployment above.

Thanks

SQL Server Compact 3.5 Downloads

SQLCEBLOG — Thu, 30 Aug 2007 13:39:00 GMT

Microsoft SQL Server Compact 3.5 released with Visual Studio 2008. The English release of SQL Server Compact 3.5 is available on the download center and the links are as given below:

1. SQL Server Compact 3.5 and Synchronization Services for ADO.Net v1.0 for Windows Desktop: Installs the files for SQL Server Compact 3.5 and Microsoft Synchronization Services for ADO.Net for Windows Desktop platform

2. SQL Server Compact 3.5 for Windows Mobile: The download contains the CAB files and DLL’s that are used to install SQL Server Compact 3.5 on the Windows Mobile Devices platform

3. SQL Server Compact 3.5 Server Tools: Installs the Server Tools on the IIS server enabling merge replication and remote data access (RDA) with SQL Server 2005 and later.

4. SQL Server Compact 3.5 Books Online and Samples: The download contains SQL Server Compact 3.5 Books Online, Online Read Me and Samples. SQL Server Compact 3.5 Books Online do not install with Visual Studio 2008. The Books Online are only available on the Web.

5. Synchronization Services for ADO.Net v1.0 Books Online: Synchronization Services provides the ability to synchronize data from disparate sources over two-tier, N-tier, and service-based architectures. The Books Online has more information about Synchronization Services. The forum for Synchronization Services provides technical Q&A about using Synchronization Services.

Visual Studio 2008 is the development environment for SQL Server Compact 3.5. Visual Studio 2008 installs SQL Server Compact 3.5 Design Tools, SQL Server Compact 3.5 for Windows Desktop and SQL Server Compact 3.5 for Windows Mobile. SQL Server Compact 3.5 Design Tools installs the SQL Server Compact 3.5 design-time components with Visual Studio 2008 and is not available as a separate Web download. The design-time components are the user interface, dialog boxes, and design-time environment, which are used to write applications for SQL Server Compact 3.5. 64bit versions of Windows are supported under WOW64 mode until a native 64bit release is available.

Support Options:
Your feedback is important to us.

Help improve SQL Server Compact by submitting and tracking bugs using Microsoft Connect website. Be sure to select SQL Server Compact as the version and provide detailed repro steps to help us identify the problem
Contact Microsoft Professional Support. For deeper support needs, purchase a Professional Support package and have experts available 24 hours a day, seven days a week, and 365 days a year
Find out what support options are available if you are located outside the United States or Canada at Worldwide Support Options
Search the Knowledge Base Articles. Get the answers you need about SQL Server Compact from the Microsoft Knowledge Base. This is the same database of technical articles used by Microsoft Support Professionals
To participate in the future SQL Server Compact Technology Adoption Program (TAP), please send us an email

SQL Server Compact 3.5 introduces the following features for software developers.

Installation and Database File Upgrade

Support for side-by-side installation together with the previous version (3.1) on desktop computers. If you try to open database files created by using earlier versions, SQL Server Compact 3.5 will give you a message that the file cannot be opened. To open it, the database file first must be upgraded by using the Upgrade to SQL Server Compact 3.5 Database dialog box in Visual Studio 2008. To access the Upgrade to SQL Server Compact 3.5 Database dialog box, click Data, click Add New Data Source, and then click Add Connection. When you try to open an earlier version of the database file, you receive a message. By selecting OK, the Upgrade to SQL Server Compact 3.5 Database dialog box appears. The file name extension of SQL Server Compact 3.5 is *.sdf, which is the same as that of the earlier versions (SQL Server Compact Edition, v. 3.1, and SQL Server 2005 Mobile Edition, v. 3.0). After a database file is upgraded to SQL Server Compact 3.5, you will no longer be able to open the database file by using earlier versions of SQL Server Compact. Database files created by the earlier versions of SQL Server Compact 3.5 can be programmatically upgraded by using the SqlCeEngine.Upgrade API. Refer to the documentation for more information.
To support older operating systems, with older encryption algorithms, and newer, more secure encryption, SQL Server Compact 3.5 supports backward-compatible encryption modes. The encryption modes available in the Upgrade to SQL Server Compact 3.5 Database dialog box are as described in the following list.

Platform Default: When you create or upgrade SQL Server Compact databases, Encryption mode will select the default encryption for the operating system. By creating a database on one of the newer platforms shown here, older platforms (such as Windows CE 4.2 or Windows Mobile 2003) will be unable to open encrypted SQL Server Compact files. The older platforms do not support the newer encryption algorithms.

Windows CE 5.0
Windows CE 6.0
Windows Mobile 5.0
Windows Mobile 6.0
Windows XP
Windows Server 2003
Windows Vista

For example, if the database is created on Windows XP, it will select encryption for Windows XP. The encrypted database created on Windows XP with the Platform Default option cannot be opened on Windows CE 4.2 or Windows Mobile 2003 for Pocket PC.

Engine Default: By default, the encryption mode for the SQL Server Compact 3.5 database file will not work on Windows CE 4.2 or Windows Mobile 2003 Software for Pocket PC. This encryption mode will work on all newer SQL Server Compact 3.5 supported platforms.

Windows CE 5.0
Windows CE 6.0
Windows Mobile 5.0
Windows Mobile 6.0
Windows XP
Windows Server 2003
Windows Vista

PPC2003 Compatibility: While less secure, this option can be used to support older and newer operating systems including:

Windows CE 4.2
Windows Mobile 2003 Software for Pocket PC
Windows CE 5.0
Windows CE 6.0
Windows Mobile 5.0
Windows Mobile 6.0
Windows XP
Windows Server 2003
Windows Vista

Tools Support

The Visual Basic Express Edition and Visual C# Express Edition of Visual Studio 2008 now fully support SQL Server Compact 3.5-based applications for desktop computers.
Enhanced SQL Server Compact 3.5 Table Designer in Visual Studio 2008 provides a user interface for creating primary key and foreign key relationships between tables.

Core Database Functionality

Implements the timestamp (rowversion) data type.
Support for Transact-SQL statements has been extended as follows:

Nested query in FROM clause
CROSS APPLY and OUTER APPLY
CAST and DECIMAL
TOP
SET IDENTITY INSERT

Data Synchronization

SQL Server Compact 3.5 now includes a new developer oriented, componentized synchronization model by using Synchronization Services for ADO.NET, available for desktop computers only.
Server Tools for configuring Merge Replication and RDA by using SQL Server Compact 3.5 can be downloaded from the Microsoft Download Center. Note that SQL Server Compact 3.5 Server Tools cannot be installed side-by-side with earlier versions of Server Tools on the computer that is acting as the IIS server. SQL Server Compact 3.5 Server Tools can replicate data between SQL Server Compact 3.5 and SQL Server 2005 and later versions. The Server tools can also support synchronization between SQL Server 2005 and SQL Server Compact 3.1. SQL Server Compact 3.5 Server Tools also supports data replication between SQL Server 2005 Compact Edition or SQL Server 2005 Mobile Edition and SQL Server 2005 and later versions.

Programmability

Supports local TransactionScope on desktop computers.
SQL Server Compact 3.5 supports LINQ to SQL. LINQ to SQL is a component of the LINQ project. It provides a run-time infrastructure for managing relational data as objects, without giving up the ability to query. It translates language-integrated queries into Transact-SQL for execution by SQL Server Compact 3.5, and then translates the tabular results back into the objects as defined by the application developer. There is no designer support for SQL Server Compact 3.5 in LINQ to SQL. The SqlMetal.exe utility must be used for SQL Server Compact 3.5. For more information, see the documentation.

Regards

Ambrish Mishra

Program Manager - SQL Server Compact

Microsoft SQL Server 2005 Compact Edition Access Database Synchronizer (ADS) RTW

SQLCEBLOG — Tue, 20 Feb 2007 00:26:00 GMT

Hi,

Today we are very pleased to announce the RTW release of Microsoft SQL Server 2005 Compact Edition Access Database Synchronizer (ADS) for which many of you been waiting eagerly.

Access Database Synchronizer provides a way to synchronize data between Microsoft Access database on a desktop and Microsoft SQL Server 2005 Compact Edition database on a device.

The salient features of this solution are summarized below

Ø Provides a synchronization solution between SQL Mobile/SSCE and MS Access. Data conversion is done while synchronizing the data.

Ø Synchronization happens when there is an active ActiveSync connection between the device and the desktop.

Ø There is no update to SQL Mobile/SSCE on the device. The solution consists of only of desktop side component which works with the existing client agent on the device.

Ø The solution is based on existing RDA replication model. Programming model is exactly the same as RDA today.

Ø Device applications written today do not need to be updated if the solution is upsized from access to SQL Server.

Ø There is no conflict detection/resolution.

The setup installs the desktop component required for synchronizing Microsoft Access database with SQL Server Compact Edition database on the device. It also includes a readme file which has the documentation for the solution and a sample application. The readme file can be downloaded separately. The sample application shows how the solution works and how to write applications for this solution. The components installed on the desktop can be used by third party applications to provide data synchronization between Microsoft Access database on the desktop and SQL Server Compact/SQL Mobile database on the device.

On a desktop, the following operating systems will be supported:

Ø Microsoft Windows XP Professional SP2

Ø Microsoft Windows XP Home Edition SP2

Ø Microsoft Windows XP Media Center Edition 2005 with Windows XP MCE 2005 Update Rollup 2installed.

Ø Microsoft Windows XP Tablet PC Edition SP2

Ø Microsoft Windows Vista (Only Windows Mobile 6.0 devices are supported)

On devices, the following operating systems will be supported:

Ø Windows Mobile 2003 Second Edition

Ø Windows CE 4.2

Ø Windows CE 5.0

Ø Windows Mobile 5.0

Ø Windows Mobile 6.0

The following versions of Microsoft Access will be supported:

Ø Microsoft Access 2000 SP3 (Microsoft Office 2000)

Ø Microsoft Access 2002 SP3 (Microsoft Office 2002)

Ø Microsoft Office Access 2003 SP2 (Microsoft Office 2003)

Ø Microsoft Office Access 2007

This solution will work with all installations for SQL Server Mobile Edition/SQL Server Compact Edition on devices. The sample application provided is supported only on Windows Mobile 5.0 Pocket PC edition.

For more details on ADS please see the readme

ADS Readme

Feedback

We look forward to you providing us feedback about this solution. You can provide us feedback at

SQL Server Mobile Edition/SQL Server Compact Edition MSDN Forum

And

SQL Server Compact Edition Blog

Manish Agnihotri, Program Manager, SQL Server 2005 Compact Edition

Please post all SQL Server 2005 Compact Edition queries at http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=152&SiteID=1

Microsoft SQL Server 2005 Compact Edition Access Database Synchronizer (ADS) CTP

SQLCEBLOG — Sat, 13 Jan 2007 13:12:00 GMT

Today we are very pleased to announce the CTP release of Microsoft SQL Server 2005 Compact Edition Access Database Synchronizer (ADS) for which many of you been waiting eagerly. To download the product you can visit the SQL Server Compact Edition product page or click on this link to reach Access Database Synchronizer download page directly.

Access Database Synchronizer provides a way to synchronize data between Microsoft Access database on a desktop and Microsoft SQL Server 2005 Compact Edition database on a device.

The salient features of this solution are summarized below

Ø Provides a synchronization solution between SQL Server Compact Edition and Microsoft Access. Data conversion should be done while synchronizing the data.

Ø Synchronization will happen if there is an active ActiveSync connection between the device and the desktop.

Ø There will be no update to SQL Server Compact Edition on the device. The solution consists of only of desktop side component which works with the existing client agent on the device.

Ø Based on existing RDA replication model. Replication setup and programming is exactly the same as RDA today

Ø Applications written today do not need to be updated if the solution is upsized from Microsoft Access to SQL Server

Ø No conflict detection/resolution is implemented.

The CTP setup installs the desktop component required for synchronizing Microsoft Access database with SQL Server Compact Edition database on the device. It also includes a read me file which has the documentation for the solution and a sample application. The sample application shows how the solution works and how to write applications for this solution. The components installed on the desktop can be used by third party applications to provide data synchronization between Microsoft Access database on the desktop and SQL Server Compact Edition database on the device.

Access Database Synchronizer Architecture

The operating systems supported for the CTP release are

Ø Microsoft Windows XP Professional SP2

Ø Microsoft Windows XP Home Edition SP2

Ø Microsoft Windows XP Media Center Edition 2002 SP2

Ø Microsoft Windows XP Media Center Edition 2004 SP2

Ø Microsoft Windows XP Tablet PC Edition SP2

Additionally we plan to support the following operating systems for RTW

Ø Microsoft Windows XP Media Center Edition 2005

Ø Microsoft Windows Vista

Following versions of Microsoft Access are supported for CTP release

Ø Microsoft Access 2000 SP3 (Microsoft Office 2000)

Ø Microsoft Access 2002 SP3 (Microsoft Office 2002)

Ø Microsoft Office Access 2003 SP2 (Microsoft Office 2003)

For RTW, we plan to support Microsoft Office 12 as well.

This solution will work with all installations for SQL Server Compact Edition on devices. The sample application provided is supported only on Windows Mobile 5.0 Pocket PC edition.

Note: Microsoft SQL Server 2005 Compact Edition Access Database Synchronizer (ADS) works with SQL Server 2005 Compact Edition (version 3.1) and with SQL Server 2005 Mobile Edition (version 3.0)

Feedback

We look forward to you providing us feedback about this solution so that we can make it better and as close to your requirements as possible

You can provide us feedback at

http://blogs.msdn.com/sqlservercompact

Know Issues

Please visit this section regulary to keep abreast with the known issues which we will post here regularly.

Manish Agnihotri

Program Manager

SQL Server 2005 Mobile Edition - Support for Windows CE 4.2

SQLCEBLOG — Sat, 13 Jan 2007 13:12:00 GMT

SQL Server 2005 Mobile Edition is now available for Windows CE 4.2 for following processors:

ARMv4, ARMv4i, MIPSII, MIPSII FP, MIPSIV, MIPSIV FP, SH3, SH4 and x86.

One can get SQL Mobile bits on Windows CE 4.2 for the above processors in following 2 ways:

Platform Builder route
Cabs deployment route

For #1, please install the Platform Builder 4.2 QFE KB923390 which will allow SQL Mobile component to appear in Platform Builder 4.2. Chose SQL Mobile as a catalog item in your workspace and do a build.

For #2, SQL Mobile cabs for all processors are located on the Hotfix site. Please contact Microsoft Customer Support Center to obtain the cabs for the specific processor type. At present, cabs are available via the Quick Fix Engineering (QFE) approach. A KB article is in the process of publication, KB924811

Please note that SQL Server 2005 Mobile Edition is the prior release version of SQL Server 2005 Compact Edition.

Rajesh Rana, Manger Test - SQL Server Mobile