Announcing SQL Server Everywhere Edition

Today we are announcing SQL Server Everywhere Edition, a light weight database designed for client applications that run from desktops to mobile devices. Pl see the section 'Dynamic Applications' in the Microsoft's Data Platform Vision and Roadmap from Paul Flessner, Sr VP, Microsoft.

Microsoft’s Data Platform Vision and Roadmap: Your Data, Any Place, Any TimeMicrosoft’s Data Platform Vision and Roadmap: Your Data, Any Place, Any Time

http://www.microsoft.com/sql/letter.mspx

The new product is based on the familiar SQL Server Mobile Edition.

-Durga Gudipati

Program Manager, SQL Server Everywhere Edition

We are in the very begining of migration to 3rd party solution for storing user documents. We currently use SQLCE2.0 and we were terribly disapointed that MS decided not to license its interoperability of SQLCE3.0 databases across all platforms.

I need to know the licensing policy of the new product before May 16th. Is it going to be royalty-based or similar to SQL Mobile (i.e. virtually free)?

|||

Can you please provide more information than this letter

|||

some more info but not much

http://blogs.msdn.com/search/SearchResults.aspx?q=SQL+Server+Everywhere+Edition&o=Relevance

|||

SQL Everywhere (SQL Ev) will be free on desktops, laptops/tablets and mobile devices running MS OS.

The first CTP will be in summer and release will be by end of the year.

Once released, SQL Everywhere replaces SQL Mobile.

-DurgaG

Analysis Services 2005 Cubes

Hi,

I had designed the DW database like

1. For each report one fact and some dimensions are created

2. Now i want to create a cube. while creating a cube i got some doubts. i want to know that what is the better way to create a cube

2.1 Whether i have to use one cube for one report

or

2.2 Whether i have to create only one cube and i have to create different measures

Doubts:

1. If i go to option 2.1 then it takes more memory? (because each cube stores the data in structres)

2. if i go to option 2.2 then it hits performance? (because several users access several reports using the same cube)

Can you please help me in this.

Thanks

Dinesh

If you have common structures between your reports you will probably get much better performance and memory useage from haveing multiple measures in a single cube rather than a cube per report. The indexes and caching could all be shared between the measures increasing the performance.|||Thanks.