>>>From a contrarian POV, on top of the benefits of only having to chuck a coiuple of DLLs into the deployment:
>>>
>>>You can use the Compact edition with the ADO.NET support for EF and Linq (native providers not OLDEB)
>>>You can use SSMS to create/manage CE databases.
>>>IIRC replicating to a main SQL server is supported?
>>>
>>>Admitted downsides:
>>>4GB database limit
>>>No Stored Procs.
>>>No nested transactions ?
>>>
>>>But unlikely that any of the latter would be a show-stopper for Mark ?
>>>
>>I found last night this reference that may be very helpful
>>http://msdn.microsoft.com/en-us/library/bb896140.aspx
>>
>>It shows what is supported / not supported in SQL Server CE vs. regular SQL Server
>
>
>This is more recent http://msdn.microsoft.com/en-us/library/bb896140(v=SQL.110).aspx
>
>Changed - minor difference at first sight
>
>- Aliasing of database object names with 'AS'.

Looks like this page has several errors. Say, why does it say that spatial indexes are supported in SQL 2005?

Or what does it mean here



Data types introduced in SQL Server 2008: Ordpath, sparse columns.


Not supported


Supported


Supported




Data types introduced in SQL Server 2008: Date, DateTime2, DateTimeOffset, FileStream, Geography, Geometry, HierarchyID, Time.


Supported


Supported


Supported

---------------
How can SQL Server 2005 support things introduced in SQL Server 2008?

This page is really misleading. I'll try to report it.