One Cube or Many ?

Hi People,

I try to figure out the best way for cubes design...

whether it's to build one big cube for the entire organization or one cube for each business area...

Is there any article (or any other source of information) for the subject ?

Thanks!

Perhaps you should try to read this...

http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/olapdbpssas2005.mspx#ELGAC

|||

Microsoft advice you to aviod to many fact tables /measure groups in one cube. You can read more in the performance guide pointed to at the top of this message group.

Another problem is that security can be harder to manage with one big cube, because of the number of roles.

Building one cube for each business area sounds like a good idea.

HTH

Thomas Ivasson

|||

O.K

Thank's a lot.

sql

ON/OFF-LINE WEB DATABASE

Hi,

I have just started learning Visual Web Developer (Express) and SQL Server (Express) but have not been able to figure how to solve this problem: my organization uses a local network for the staff and intends to collect data through the internet, but we lose our connection to the internet for several hours in a day. What considerations should we bear in mind as we design the web application and database? For example, is it wise to reside the database in the web application? How do we synchronize the database whenever we come on-line?

You can configure your SQL Server 2005 Express for replication. Check out this MSDN documentation for reference