>>I'm scoping out a potential ASP.NET 2.0 project. The database it will attach to currently lives in an MSDE2K instance. However, it could potentially be moved/migrated to a SQL Server Express (2005) instance.
>>
>>Are there any significant advantages to doing so? :
>>
>>1. Does SSX "integrate better" with ASP.NET 2.0, making development easier?
>>2. Does SSX have any performance advantages (e.g. higher # of connections/concurrent queries without performance throttling etc.)?
>>
>>Basically, are there enough compelling reasons to use SSX with ASP.NET 2.0 to offset the effort required to move an existing database to it? TIA.
>
>BTW it's SSE.
>1) Yes.
>2) Yes.
>Basically yes:)
>Effort? Maybe a five minutes click this and that effort.
>
>Now some advantages from my POV:
>-Programmability with C#. CLR is there:)
>-Increased db limit (2 to 4Gb)
>-1Gb memory and 1 CPU limit
>-Concurrent connection limit (I'm sure once it was there in docs when in beta) 25. But since then no connection limit info I can see anywhere. Sounds like now no limit (query governor died, long live new governor:)
>-New datatypes + enhanced limits of existing ones
>-Partioning on tables, pivoting, ranking, apply ... many more new features
>-Ability to be used as single user instance (like a local db)
>...

SSE sounds like a winner. Thanks, Cetin.