Cardinalities Taking So much time to detect

[Former Member]

Hi Experts,

Cardinality is taking so much time to detect in the Universe 3.1 using the data base Sql server 2008.

Earlier when i created Universe used connection to  the Server (X and Y database). Know changed the server connection to A and database B this could be the reason.Can any one provide me the help on this issue. 

Server Name : SQL Server 2008

Connection Name :OLEDB

Server :XYZ

Database Name :ABC

has been changed to

Server :123

Database Name: DEF

Thanks for your help.

Thanks & Regards,

Gowtham.

[former_member678295]

execute the tool generated query in the back end.

if there is any same issue then something wrong with DB.

[Former Member]

Simple answer would be just understand the relationship between both tables and also try to gather functional knowledge from Business.

You don't need to use detect automatic functionality to be used in this case.

[Former Member]

There might be a case that in new database table has many rows.

Only because of that BO will take more time to calculate cardinality.

[Former Member]

Thanks for your reply Swapnil.

But the new database is having the same tables in-fact I am not getting the SQL Latin Collate error

Thanks & Regards,

Gowtham.

[former_member4998]

HI

Cardinality is a property of a join that describes how many rows in one table match rows in another table.  But if taking more time suspect that new DB may have more no of data compare to old DB.

Please find the below link for more info

http://scn.sap.com/docs/DOC-55523

[Former Member]

Thanks Sreenivasulu.

Is there any resolution which I can optimize that.

Regards,

Narendhra

[Former Member]

Hi,

At the Time of Detecting Cardinalities Filter the Database Tables for limited records.

like Filter your Fact Table for Last 2 Months or and 4-5 main Locations .