Creating a copy/view/alias table to Point One Report too.

[lecarlos]

Newbie to Framework Manager,

I currently have a report that is using 2005 SQL database/datasource connection and I have migrated some of the tables to Oracle except for maybe two in this one report.  I was asked if I could create a view in framework manager to point this report to so that it would stay on SQL2005 until the rest of the tables has been moved over to Oracle.  Is there anyone that could provide step-by-step instructions on how this can be done in framework manage.  Would have to make a view of this table and point it back to SQL2005 and leave the current table pointed to Oracle.

This was originally in SQL 2005 and I migrated it Oracle.  But now there is one column that I'm having an issue with and the DBA suggested that I create a view or alias to put this one report back to the SQL 2005 tables and leave the currently table mapped to Oracle.  This way I can update Framework Manager with the Oracle updates. Does this make sense?

We are using Cognos 10.2.1, and SQL 2005.  Please let me know if I need to provide additional information on this request.

Thanks,
lecarlos

[bus_pass_man]

1.  Import the view.
2.  Select the query subject which is the source of the stuff in the report
3.  Choose remap to new source from the context menu.
4.  Replace the old object references with ones from the view.

[bdbits]

Since you already have the SQL Server 2005 data source defined in Cognos, you could add it to your FM project, create query subjects for the SQL Server 2005 table(s) with appropriate joins, and incorporate the tables into your business layer query subjects. The big caveat is this will force local processing on the Cognos server to join the data. If the tables are large, or the report runs frequently, this could have performance implications on the Cognos server.

Alternatively, you can create a link to SQL Server from Oracle, then reference the SQL Server table(s) in your query subject. This may have been what the DBA was thinking of with his suggestion. There are always some limitations using database links, but it will probably work for you. The SQL in your database layer can simply reference the linked table, and the rest of the FM model will think of it as an Oracle table. This also puts the load for joining the data on the Oracle server. If it is what your DBA suggested, they can hardly complain about that. :)