Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Qvd's from different sources

Hi,

I have 3 qvd's namely dim_account, dim_state and fact_lines.

account qvd is coming from sql server and rest of qvds are coming from oracle data base.

I have imported into QVW file made relationship between fact_lines and as well dim_account with correct pk and fk.

But if i pull any dimension column from account and expressions from fact, i haven't seen any data.

If i do list box for dim_account coulms there is data. is there any way to figure out this issue.

Pls help me on this issue

Regards,

Kumar

21 Replies
Anonymous
Not applicable
Author

Thanks Sudeep.

Can you answer me on this one.

dim_account is coming from SQl server

and fact_lines is coming from Oracle

We joined with account_key from dim and with fact table column of fact_act_key.

will it pull data, if wejoin like this.

Regards,

Kumar

sudeepkm
Specialist III
Specialist III

QlikView supports heterogeneous data load in same QVW so no problem in loading data from two sources.

the best way to do is to have individual QVD Gen qvws to create QVD based of the source system tables.

I think you are already doing it.

Next thing is preparing the data model in QlikView for which you need to identify the association key.

In your case the account_key is the key field. Please make sure the field name is same in both the tables.

You can join or you can leave it as it is. as per your tale names it seems like a star schema (dim and fact) and QlikView supports the Star Schema model very well.

Anonymous
Not applicable
Author

Qvd are coming from individual QVW's only. But  fact table the key field is different from dim table. Is it mandatory to be the both key fields name same.

sudeepkm
Specialist III
Specialist III

QlikView associates two or more tables based on Field name. So as long as the Field names are exactly same the association will work. If you have more than one fields with same name across different tables then you will face synthetic keys which you can avoid by using proper data model techniques.

Anonymous
Not applicable
Author

Hi Petter,

One is datetime and another table as timestamp without timezone.

Anonymous
Not applicable
Author

What you said is correct.

dim_account:

Load account key as fact_key

name,

act_no

Fact_lines:

Load fact_lines,

lines_status

.

.

Like this I joined.

My joining is correct or not. Can you guide me here.

Anonymous
Not applicable
Author

Hi Kumar,

Please try as below:

dim_account:

Load account key as fact_key

name,

act_no

Fact_lines:

Load fact_lines as fact_key,(if Fact_lines and Fact_key fields are common ids.)

lines_status

Anonymous
Not applicable
Author

No, Neetha,

It is not working

sudeepkm
Specialist III
Specialist III

what is the key field in Fact table that matches (you want to associate) with the key field in Dim table.

Anonymous
Not applicable
Author

Check for Key field in fact table which match to the Key field in Dimension table and rename to the same name.

if no common field,please post sample data, will be able to help.