You can see the criteria necessary for this to work here. All native Cognos Analytics features utilize DQM only – CQM queries execute in simulated DQM as mentioned above. The terms ‘DQM’, ‘query service’ and ‘XQE’ all essentially refer to this java process. It is a 64-bit java query engine that runs as one or many java.exe process on the Cognos application server and is managed by the query service.

Dynamic Query Mode and the Query Serviceĭynamic Query Mode is the query mode introduced in Cognos 10.1. This almost always works but of course fails whenever you need it most…ĬQM works just fine and moving to DQM is not urgent, however I strongly advise you to do all new Framework Manager modeling in DQM (or even better, build data modules) and start seriously considering what a migration might look like. Furthermore, Cognos 11 features either don’t work with CQM (data modules) or must simulate DQM when using CQM-based models (dashboards). CQM does have a query cache but it runs on a per session, per user basis and in my experience causes more problems than it’s worth. Query speed is hampered by the limitations of 32-bit processes, particularly as it relates to RAM utilization. The majority of FM models I encounter were built in CQM and thus the majority of queries processed by Cognos are CQM.

CQM was the default query mode for new models created in Framework Manager up to Cognos 10.2.x, after which Dynamic Query Mode became the default. It is a 32-bit C++ query engine that runs on the Cognos application server as part of the BIBusTKServerMain process. There are many query engines hidden beneath the hood of your 2020 model Cognos Compatible Query ModeĬompatible Query Mode is the query mode introduced in ReportNet (AKA, my junior year of college…).

Buckle up folks, this is going to get wild. My goal for this article is the run back the clock, peel back the onion and give you a historical, technical and practical understanding of the 3 Cognos query modes. With the addition of data sets running on the compute service (aka ‘Flint’) things are even more complicated. While a lot has changed since 2015 understanding the difference between Compatible Query Mode and Dynamic Query Mode is still crucial. This is actually a sequel one of the very first blog posts I ever wrote for blueview.

What does cqm stand for