dimension design

I have a fact table and dimension. a view is taken as base table for Dimension which will Productkey,LevelId. One product may exist in multiple levels. so we have multiple records for a single product.

And in fact table we have productkey as foriegnKey. When i relate fact n dim to create a cube, cube considering one record for each product key in fact table. its automatically avoiding other records. can we any way stop this happening? OR is this default behavior?

Thanks in adv

Do you have a self-join in your product dimensions table between productid and parentproductid? This sounds to me as if you have a parent-child dimension/structure. In the dimension wizard you will see, in one of the final steps, a question/page where you can tell if you have a parent child structure.

You will also check if you are not having a many-to-many relation between the fact table and the product dimension table.

The third point is that you can add the level to the productid and make a unique technical key for each kombination of product and level. This will have to be matched with the records in the fact table.

HTH

Thomas Ivarsson

|||

Thanks for the response.

3rd point is not possible to implement..let me check with first point.

so does it ignore multiple records for same productKey?

|||

Hello again. In the AdventureWorks sample database you have table, Production.BillOfMaterials that you can have a look at. In the Adventure Works DW sample database you have the account dimension with a more simple parent child relation.

I am not sure what you mean by "ignore multiple records for the same productkey.

With parent-child dimensions you can have data/facts in the fact table that is not only from the leaf level but also from higher levels.

HTH

Thomas Ivarsson

|||

In this case its not possible to implement Parent-Child dimension. and there is also situation that one child product can have multiple products as parents. Its some thing like many-many in Parent-child.

|||

Looks like you have to use many-to-many dimensions then.

Here is a link to some help: (http://www.sqlbi.eu/Default.aspx?tabid=80)

HTH

Thomas Ivarsson

|||

Before coming to forum for the solution, i had tried m2m dimension. When i took the view as dimension where one product can exist in multiple lelvels. table will look some thing like this

leafPKey 5233 5233

L1PKey 9 10

L2PKey 31 15

L3PKey 632 632

L4PKey 2572 2572

L5PKey 5233 5233

When this table is related to fact table only one 5233 is considered. 5233 is only visible under l1pkey= 10.

is this default behavior, or can i get both the ids by changing some thing?

when a single record is only considered m2m relation is existing.

Thanks in adv

sql

Different versions of SSMS?

Hi.
Does it exist different versions of SSMS?
I'm now working with SSMS Express and SQL Server 2005 Express. How can I
make a scheduled backup from SSMS?
___________________________
Best regards - Anders
Sql Server Express does not include a SQL Agent, so you will have to
use an external solution for scheduling your backups. My suggestion
would be to run a script with SQLCMD on a scheduled basis (e.g. with
the at command).
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Or use below two:
http://sqldbatips.com/showarticle.asp?ID=27
http://sqldbatips.com/showarticle.asp?ID=29
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1180341388.388646.126450@.u30g2000hsc.googlegr oups.com...
> Sql Server Express does not include a SQL Agent, so you will have to
> use an external solution for scheduling your backups. My suggestion
> would be to run a script with SQLCMD on a scheduled basis (e.g. with
> the at command).
> Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>

Different domains

Hi, I have two SQL servers in different domains(A and B), I cant use
the Enterprise Manager to register eachother...they show me "Sever doesnt exist" but when I use ping I can show them...
Please help me....What can I do?
cedutang.check out this link (http://www.dbforums.com/t968239.html) and see if it helps

Differences in these errors

I understand timeouts and SQL Server does not exist error messages, but I am
not too sure under what conditions do the following 2 messages occur and the
difference. We dont see it often, but at times our applications spits out
these messages and would like to know where to start investigating and what
they mean. Can you help me narrow it down?
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). ~08S01
(11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
Check your network documentation.
[Microsoft][ODBC SQL Server Driver]Communication link failure
ThanksMy guess is that they both lead to the same thing (an intermittent problem
with your network), and they are just raised at different points (e.g. the
first may be when it can't connect, and the second may be when it has
connected but then gets cut off).
"Hassan" <hassan@.hotmail.com> wrote in message
news:uHDddtZ6HHA.5360@.TK2MSFTNGP03.phx.gbl...
>I understand timeouts and SQL Server does not exist error messages, but I
>am not too sure under what conditions do the following 2 messages occur and
>the difference. We dont see it often, but at times our applications spits
>out these messages and would like to know where to start investigating and
>what they mean. Can you help me narrow it down?
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> ~08S01 (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
> error. Check your network documentation.
> [Microsoft][ODBC SQL Server Driver]Communication link failure
> Thanks
>|||So is it safe to conclude that its definitely network bound and not some SQL
Server error that inteprets it as those error messages ?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OgmhrwZ6HHA.4436@.TK2MSFTNGP03.phx.gbl...
> My guess is that they both lead to the same thing (an intermittent problem
> with your network), and they are just raised at different points (e.g. the
> first may be when it can't connect, and the second may be when it has
> connected but then gets cut off).
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:uHDddtZ6HHA.5360@.TK2MSFTNGP03.phx.gbl...
>>I understand timeouts and SQL Server does not exist error messages, but I
>>am not too sure under what conditions do the following 2 messages occur
>>and the difference. We dont see it often, but at times our applications
>>spits out these messages and would like to know where to start
>>investigating and what they mean. Can you help me narrow it down?
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
>> ~08S01 (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
>> error. Check your network documentation.
>> [Microsoft][ODBC SQL Server Driver]Communication link failure
>> Thanks
>|||> So is it safe to conclude that its definitely network bound and not some
> SQL Server error that inteprets it as those error messages ?
Why would you assume that it's NOT a network problem? Do you think SQL
Server is trying to trick you, maybe it's embarrassed about some bug that
hasn't been fixed?|||Yes.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eyCqJJb6HHA.5160@.TK2MSFTNGP05.phx.gbl...
>> So is it safe to conclude that its definitely network bound and not some
>> SQL Server error that inteprets it as those error messages ?
> Why would you assume that it's NOT a network problem? Do you think SQL
> Server is trying to trick you, maybe it's embarrassed about some bug that
> hasn't been fixed?
>|||Ok. <shrug>
"Hassan" <hassan@.hotmail.com> wrote in message
news:us4$8pr6HHA.2752@.TK2MSFTNGP06.phx.gbl...
> Yes.
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:eyCqJJb6HHA.5160@.TK2MSFTNGP05.phx.gbl...
>> So is it safe to conclude that its definitely network bound and not some
>> SQL Server error that inteprets it as those error messages ?
>> Why would you assume that it's NOT a network problem? Do you think SQL
>> Server is trying to trick you, maybe it's embarrassed about some bug that
>> hasn't been fixed?
>|||We have been getting the same issue and have ruled out the network as the
cause. This appears to have caused by additional load on the server as we
recently moved some databases on it. We are going to allocate more memory to
SQL and move some of the databases off the server. Hopefully this will
resolve the issue.
"Hassan" wrote:
> So is it safe to conclude that its definitely network bound and not some SQL
> Server error that inteprets it as those error messages ?
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:OgmhrwZ6HHA.4436@.TK2MSFTNGP03.phx.gbl...
> > My guess is that they both lead to the same thing (an intermittent problem
> > with your network), and they are just raised at different points (e.g. the
> > first may be when it can't connect, and the second may be when it has
> > connected but then gets cut off).
> >
> >
> >
> > "Hassan" <hassan@.hotmail.com> wrote in message
> > news:uHDddtZ6HHA.5360@.TK2MSFTNGP03.phx.gbl...
> >>I understand timeouts and SQL Server does not exist error messages, but I
> >>am not too sure under what conditions do the following 2 messages occur
> >>and the difference. We dont see it often, but at times our applications
> >>spits out these messages and would like to know where to start
> >>investigating and what they mean. Can you help me narrow it down?
> >>
> >> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> >> ~08S01 (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
> >> error. Check your network documentation.
> >>
> >> [Microsoft][ODBC SQL Server Driver]Communication link failure
> >>
> >> Thanks
> >>
> >
> >
>
>|||Moving a high load database off the server and rebooting it has resolved the
issue.
"Hassan" wrote:
> I understand timeouts and SQL Server does not exist error messages, but I am
> not too sure under what conditions do the following 2 messages occur and the
> difference. We dont see it often, but at times our applications spits out
> these messages and would like to know where to start investigating and what
> they mean. Can you help me narrow it down?
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). ~08S01
> (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> Check your network documentation.
> [Microsoft][ODBC SQL Server Driver]Communication link failure
> Thanks
>
>