our organization is evaluating the possibility of replacing Oracle Business Intelligence with IBM Cognos Business Intelligence.
My question is, does a tool exist that can assist us with migrating from Oracle BI to Cognos BI or are we required to create our environment from scratch?
Thank you!
The IBM Cognos Framework Manager tool may allow you to import your Oracle designer dat file.
Import tool: Oracle Oracle Designer 1.3.2, 2.1.2, 6.0, 6i to 10g (http://www.oracle.com/technology/products/designer/index.html)
Import interface: [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model) via DAT File from Oracle Designer Import bridge: 'OracleDesigner' 9.1.0 - 2017-04-03 17:26:09
This bridge imports an E/R Model, or a Server Model from an Oracle Designer .DAT file.
Please refer to the bridge File parameter for details on how to generate the .DAT file.
Any given .DAT file may contain:
* an E/R Model (with entities),
* a Server Model (with tables),
* many Database Implementation Models (with table implementations).
Ironside may also offer services around this as discussed in the Migrate from Oracle to CA case study: https://www.ironsidegroup.com/case-study/migrate-oracle-discoverer-cognos-analytics/
Related
I am a little confused by the JOOQ product compatibility with AWS RDS Aurora MySQL.
Perhaps this purely a licence restriction rather than technical one.
This page https://www.jooq.org/legal/licensing#databases shows RDS Aurora support in Professional Edition & Enterprise Edition. The "License Terms" section on https://www.jooq.org/download/ show that the open source version does not allow for commercial databases and only allows for open source ones.
My question is:
Can anyone confirm that this is actually a licence usage terms restriction, rather than a technical one with the open source code, e.g. it's not that when using the professional edition one actually would run a different flavour of JOOQ, e.g. a different binary with more features?
Purely for bonus points & general interest:
We can see in this commit https://github.com/jOOQ/jOOQ/commit/863ade3b3c7a004d477d54193ac5104435b9835b and in this github issue https://github.com/jOOQ/jOOQ/issues/5196 dating back to 2018 support was added to the open source project.
Given AWS generally refer to the Aurora product as being compatible with mysql 5.7, why would JOOQ need to do anything at all to "support" this, shouldn't it "just" look like using MySQL 5.7 from the perspective of a client application? https://aws.amazon.com/rds/aurora/faqs/ Perhaps the critical word below is "most".
most of the code, applications, drivers and tools you already use today with your MySQL databases can be used with Aurora with little or no change. The Amazon Aurora database engine is designed to be wire-compatible with MySQL 5.6 and 5.7 using the InnoDB storage engine.
Lukas from the jOOQ team here.
The "License Terms" section on https://www.jooq.org/download/ show that the open source version does not allow for commercial databases and only allows for open source ones.
Perhaps that section title "License Terms" is misleading for this particular purpose (which we'll review). There's no way for the jOOQ Open Source Edition to not allow you to use the jOOQ Open Source Edition with any database product of your choice. The ASL 2.0, which is the license governing the jOOQ Open Source Edition, does not allow for any such "amendments" or restrictions on top of the ASL 2.0 - otherwise it would no longer be the ASL 2.0 license.
What this website section means is that the jOOQ Open Source Edition does not technically support any other databases than the ones listed there, nor do we offer any support for such an integration as a vendor, but if you can get it to work (through patching, integration testing, etc.) you're free to do so.
Can anyone confirm that this is actually a licence usage terms restriction, rather than a technical one with the open source code, e.g. it's not that when using the professional edition one actually would run a different flavour of JOOQ, e.g. a different binary with more features?
There is no "license usage term restriction" whatsoever in the jOOQ Open Source Edition, apart from the ASL 2.0
Given AWS generally refer to the Aurora product as being compatible with mysql 5.7, why would JOOQ need to do anything at all to "support" this, shouldn't it "just" look like using MySQL 5.7 from the perspective of a client application?
We as a vendor will give you warranties and commercial support, as well as maintenance on your Aurora MySQL integration when you use jOOQ's Aurora MySQL support.
In case you do run into one of those cases where Aurora MySQL doesn't work exactly like vanilla MySQL, we'll fix (or may already have fixed) the issue for Aurora MySQL only, not affecting other MySQL users.
We have sensitive data in our database and I wanted to look into Oracle auditing capabilities. Our install is Embedded since it came with the application we have. Any feedback is appreaciated.
Can we develop drill down reports in IBM Cognos other than by DMR(Dimensional Modeled Relation) technique? My reports are running slow when I drill down to lower level using a DRM package while my reports runs fine when I run the report directly on the lower level using a non-DRM package.
Without using a cube source such as Transformer or TM1, no.
If that option is unavailable to you - are you running your reports against a large fact table? If so, consider creating these reports against summary/aggregate SQL tables which contain a minimum of data.
What the differences between "Cognos TM1" and "Cognos 10 BI"?
Which one is consider as BI Tools by IBM?
There are huge differences between "Cognos TM1" & "Cognos 10 BI"!
Cognos TM1 is a (OLAP) multidimensional database which can be queried from Excel and the Web through "TM1 Web", "TM1 Executive Viewer" and "Cognos 10 BI". Within this database, you'll be able to create almost anykind of OLAP / Decisional application.
Cognos 10 BI is a web based reporting application. Users, depending on their rights (licence) will be able to run reports, schedule reports and/or create ad hoc analysis against relational and/or multidimensional databases. In order to do so, a logical layer has to be built using "Framework Manager". This logical layer is used to hide database complexity and to provide to the end users relevant information.
In simplest terms:
TM1 is a database engine and a collection of applications for accessing and managing its databases.
Cognos BI is a collection of web applications that provide pretty interfaces for viewing and doing stuff with data.
More often than not, Cognos BI uses TM1 databases as its data source, but it does not have to. If Cognos BI is using TM1, most of the same user functions that are possible in TM1 applications are also available through Cognos BI, except they are available in a more user-friendly manner. Cognos BI also adds functionality not in TM1 applications to allow additional data management. IBM's marketing is confusing, but generally Cognos BI and Cognos TM1 collectively are considered to be the BI Tools package that they offer.
Now to be a little more technical about TM1, it is not just a plain old database. As others here have mentioned, it is a multidimensional OLAP database. It is able to handle numeric and string data, but it does not have a concept of NULL values. Numeric data can be summarized using consolidated elements. It has attributes to store metadata in. It has a built-in rules engine to handle business logic and custom calculations. It has processes for ETL and database maintenance tasks. It has chores for scheduling processes at various intervals. It links to Excel workbooks. Lastly, in addition to these features and more that are provided out of the box, TM1 exposes an API for programming against using 3GLs such as C++, C#, Java, and even VBA.
The key difference is Cognos TM1 is meant to work with excel easily wheras Cognos 10 BI is mainly browser based.
Have a look here for gory details.
http://www.tm1forum.com/viewtopic.php?f=5&t=1442
Cognos TM1 is also referred to by IBM as Financial Performance Management FPM. It's an in-memory MOLAP cube application with real-time rules calculation. As it provides end-user writeback it's often used by the Office of Finance for budgeting and modelling - therefore the MS Excel interface is frequently used. However it also comes with a zero footprint web "front end" as well as Cognos Insight, which permits distributed or disconnected access to the TM1 cubes (located server side).
TM1 may be integrated into Cognos BI, so that Cognos BI reports from TM1 cubes; or TM1 may be accessed from a portlet within a Cognos BI dashboard.
difference between cognos10 and cognos tm1 :-BI is the reporting tool and cognos tm1 is analysis and reporting tool , in tm1 bulid the CUBES and BI generatead the reports
I've just been doing some research into sql data services, and found out that the current ACE model is being phased out for a newer relational model. It seemed all the samples in the March 2009 CTP were based on the ACE model (like the StorageClient project). I'm wondering if these are still relevant- they seem to all be based on the ACE approach, but I'm not sure if it's just a REST interface onto the relation back end.
Correction... the samples in the Windows Azure SDK don't use SQL Data Services at all. They're running against Windows Azure table storage (which is not changing models and remains based on ADO.NET Data Services). So the samples you're looking at are entirely valid.
Not really. The new direction SDS has taken means that the ACE model will be dropped. They will support a REST interface and you can use ADO.Net Data Services to communicate with it.
You've problably read this, but here's the post in which they announced the changes