I know I am late on this but that gives me the opportunity to just grab your knowledge without having to go thru it myself ;)
I am trying to use DQM for a DMR and the first step is to install some JDBC files , the guide says that the JRE files from the
database have to be copied to the installation folder. The DB is SQL Server 2012.
Can anybody say which files have to be copied to which folder?
Cognos is here:
C:\Program Files\ibm\cognos\c10_64
It's a 64 bit install.
I found this:
http://www.microsoft.com/en-us/download/details.aspx?id=11774
Quote from: cognostechie on 18 Aug 2014 04:39:37 PM
I know I am late on this but that gives me the opportunity to just grab your knowledge without having to go thru it myself ;)
I am trying to use DQM for a DMR and the first step is to install some JDBC files , the guide says that the JRE files from the
database have to be copied to the installation folder. The DB is SQL Server 2012.
Can anybody say which files have to be copied to which folder?
Cognos is here:
C:\Program Files\ibm\cognos\c10_64
It's a 64 bit install.
I found this:
http://www.microsoft.com/en-us/download/details.aspx?id=11774
Hi,
For SQL Server you probably just need to copy one file - sqljdbc4.jar. Pop it in two places:
\Program Files\IBM\cognos\c10_64\webapps\p2pd\WEB-INF\lib
and
\Program Files\IBM\cognos\c10_64\v5dataserver\lib
If you want to use an external namespace for db signon or the Cognos service credentials, you also need a second file in those locations - sqljdbc_auth.dll. If you're manually specifying the signon in the data source definition then you don't need this file.
This is all nicely detailed in the Dynamic Query Cookbook - it's worth a read if you're going to be using DQM :)
http://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/page529.html
Cheers!
MF.
Thank you so much MF ! You are always helpful ! I am reading the cookbook right now but it does not have any recipes for
cooking anything, it rather says everything about DQM :)
So it is working now and I created a new datasource using JDBC connection, then created a new FM Model and published a package. In the beginning screens while creating the FM Model, there was a checkbox for Dynamic Query Mode which I checked on and it did not ask me at the time of publishing the package so I presume that should be ok.
Now this is what I noticed. The report using the DQM package takes about 20 seconds (Excel output) the first time it is run. Second time I run it, it comes out instantly (using cache?). Another report with the same columns (everything same) using the earlier package (non DQM) runs every time I click on it and takes about 25 seconds (because the output is set to Excel so it runs every time).
Is this what should be expected?
By the way, when I do NOT run the report (using DQM package) for about 10 minutes and then run it again, it again takes 20 seconds.
Quote from: cognostechie on 20 Aug 2014 06:09:05 PM
So it is working now and I created a new datasource using JDBC connection, then created a new FM Model and published a package. In the beginning screens while creating the FM Model, there was a checkbox for Dynamic Query Mode which I checked on and it did not ask me at the time of publishing the package so I presume that should be ok.
Now this is what I noticed. The report using the DQM package takes about 20 seconds (Excel output) the first time it is run. Second time I run it, it comes out instantly (using cache?). Another report with the same columns (everything same) using the earlier package (non DQM) runs every time I click on it and takes about 25 seconds (because the output is set to Excel so it runs every time).
Is this what should be expected?
Hi,
When you create an FM model, you get prompted at the beginning of the process to ask if your model is going to use Dynamic Query Mode. If you choose this, the model is permanently DQM with no option to publish CQM packages. If you deselect the DQM option when creating the model, you get the chance to turn DQM on and off when publishing packages, so it can give you more flexibility.
I'm guessing the initial run of your report is populating the cache, then subsequent runs can simply grab the data from the result set cache, so you get instantaneous response.
One way to see exactly what is happening is to fire up Dynamic Query Analyzer and see the generated queries, how they are being planned, and when the database is being accessed vs the cache.
Have fun!!
MF.