Analysis Service on 2005

I'm trying to create a Cube on analysis services, but do not see any
realtions in the diagram between my selected tables. The tables use indexes
rather than primary keys. Do you have any suggestions about how I can specify
the relations from Analysis Services.
Thanksdo you talk about the DSV (data source view) schema?
the system can detect relationships based on column names, you have an
option which allow you to change the way visual studio will detect the
relationship between the tables.
but this works BEFORE you add tables in the DSV
after this you have to manually create the links in the DSV. (its a simple
drag&drop)
"dbach" <dbach@.discussions.microsoft.com> wrote in message
news:E0F20189-17FC-443D-8348-2CC63172F0FD@.microsoft.com...
> I'm trying to create a Cube on analysis services, but do not see any
> realtions in the diagram between my selected tables. The tables use
> indexes
> rather than primary keys. Do you have any suggestions about how I can
> specify
> the relations from Analysis Services.
> Thanks

An update query

Hi,
I run a same update query in our two servers, which have the same
configuration and same database and indexes, one of them is returning the
result in 4 seconds, and the other one in 7 minutes. the only difference
between them is that the fast server has 512 MB and the other one has 256 MB
RAM. Why is it that much slow.
Thanks in advance,
Mathew
hi Mathew,
Mathew wrote:
> Hi,
> I run a same update query in our two servers, which have the same
> configuration and same database and indexes, one of them is returning
> the result in 4 seconds, and the other one in 7 minutes. the only
> difference between them is that the fast server has 512 MB and the
> other one has 256 MB RAM. Why is it that much slow.
> Thanks in advance,
actually the 2 servers are not the same... probably they do not have the
same data too, and/or the same disk subsystem... perhaps the second is more
fragmented too, both at physical OS file status and at internal logical page
status..
and having the half of RAM does not help for sure.., this mean MSDE has
fewer available resources, that the runnig applications have more
contentions for resources with the SQL Services...
more paging at OS level will be needed by all applications... the whole
system can be involved...
BTW, the 2 results are very different indeed... but try cleaning up your
server... defrag it, both at OS level and database level..
try comparing the statistics output as well as the used plans...
lot of variables are involved...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply