Re: Using a heirarchy bridge table

#1

Thanks again.

--
----------------------------------------------------------------------------
Louis Davidson - drsql (AT) hotmail (DOT) com
SQL Server MVP

Compass Technology Management - www.compass.net
Pro SQL Server 2000 Database Design -
http://www.apress.com/book/bookDisplay.html?bID=266
Blog - http://spaces.msn.com/members/drsql/
Note: Please reply to the newsgroups only unless you are interested in
consulting services. All other replies may be ignored

"Deepak Puri" <deepak_puri (AT) progressive (DOT) com> wrote

Quote:

Sure, that sounds like a plan - as you noted, only cube processing
performance should be adversely affected (though if your users do
drillthrough to detail, that could slow down as well). Large
parent-child dimensions can get sluggish (independent of the fact view),
but it didn't sound like this one was huge.

Longer term with SQL Server 2005, you can study the new dimension
options - I haven't used them in a real project yet, but perhaps others
in the group have some ideas?

- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Using a heirarchy bridge table

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap

Re: Using a heirarchy bridge table - 02-16-2005 , 08:29 AM