Creating views

Hi all,

Bit of a SQL server newbie here, I have two tables; Fish (containing Name and ID) and Fishing (containing just a concatonatted FishingID), but to relate the tables i would have to join (reference) the fields in the Fish table ie: fishname and FishID to match the other tables FishingID.

Every time i concanonate the fishname and FishID in the criteria the view doesent run but if i actually write an example FishingID in the criteria the view runs.

How do i refernce the fields in the criteria section?

JnrYou'll get an answer much quicker if you post the DDL of your tables, ssome sample data and the expected results...

Also what about the SELECT Statement you created...

My telepathic usb port is clogged...|||What is the concatennated ID for?

Something sounds FishyID to me.|||My telepathic usb port is clogged...That is a very good thing!

-PatP|||That is a very good thing!

-PatP

Why is that...I was hoping to use it to do all my typing for instead...|||You and a telepathic anything sounds like a class 3 SLG (spontaneous lawsuit generator) to me. Between the various forms of harassment, the politicially incorrect thoughts being broadcast, and the ensuing chaos from just having your head opened up to the casual passer-by... Egad!

-PatP

Creating Parent Child Hierarchies

Hi
I have the following in my cube
Location Dimension containing LocationID and LocationName attributes.
Customer Dimension containing CustomerID,CustomerName....,LocationID
The LocationID in the Location Dimension and Customer Dimension are related to each other.
I want to create a hierarchy with the LocationName in the First Level and the CustomerName in the second level. How to I accomplish this? As i said I already have a relationship defined between the two tables.

Thanks and Regards
Guruprasad Karnik

This is not a recursive hierarchy from what you are describing.

You can find a recursive hierarchy in the employee table in the Adventure works sample data base that is a part of the SQL server 2005 installation. You use parent-child hierarchies with this type of primary key-foreign key relationship in the same table.

If you download the performance guide for SSAS2005 (see the first post in this forum) and have a look at page 82 and further(Referenced relationsships), you will find a lot of helpful information.

HTH

Thomas Ivarsson