Dual Datasources (Performance) Framework Manager

[drepso]

Hi

I have a FM model that currently uses two databases, therefore I have two datasource connections.

It was suggested to me that for performance reasons, only one datasource connection should be used.

Therefore the result would be a FM package using only one datasource connection.  Referencing tables from existing database, and views in the same database newly created from the second database.  Therefore all query items are in the same database.

Just want to know what is the 'general best practice' when using dual datasources.  Do you create views and use single data source, or manage with two.

Understand this may be a loaded question as both databases may have a lot of tables.

Also if any tables change, views will need to be changed too.  However, I am very interested in any increased performance from using single datasource.

Is this a valid option?

Thanks in advance

[blom0344]

I'd say it depends.. If both databases are on the same server, then performance is likely better than with the Cognos server having to join datasets. If the Cognos server has a heavy workload (handling many requests), then the same goes.
However, if the databases are on different servers and the Cognos machine is idle most of the time , then difference may be not that great..

There is so many components that play a role, the only way to answer your question is by testing one option against the other.

[The number of tables you mention is a matter of maintenance, not a performance issue]

[drepso]

Thanks for the advice.
Cheers