DQM

[dssd]

Does DQM work with Relational style reporting.....and i am not talking about DMR

[MFGF]

Yes - it works with both relational and dimensional style reporting. With relational style reporting you still benefit from shared caching of data.

Cheers!

MF.

[MMcBride]

Based on m limited personal experiance this is an issue of "Can" vs "Should"

I do not recommend DQM for Relational Reporting, admittedly I have not tried 10.2.1 FP1 as of yet but we have had problems with Database Objects not refreshing in DQM models (someone adds a column after the first model)

We have also had issues where when you attempt to bring in a new table the model will not let you it tells you the item is not up to date, but when you attempt to update the item it tells you the item is not up to date and cannot.

Pardon the broad generalizations - I know there are fixes out there for these issues, however we have 4 different Modellers in my company spread acrossed America and trying to update someone elses model is hard enough without the tool tossing out random errors where the only fool proof solution has been to start over and rebuild the model from scratch.


We use DQM only for DMR right now on 10.1.1 FP2
Perhaps that will change when we get to 10.2.1

[bdbits]

I wonder if this is not somewhat dependent on data sources. We just went live with our first model built with DQM from the beginning, using SQL Server 2008 in our case. We have both DMR and a relational packages. While we have had issues that ended up requiring a couple of hot fixes, we did not have the refresh issues you have MMcBride.

Caveat: I was not the modeler this time and she is out today, but I am pretty sure I would have heard about these kinds of problems.

Still, it is troubling that after all this time, there are still problems like you are experiencing. Our server admin would like to move us to DQM (at least at publishing time) so he can run all 64-bit, and I wonder if that is a good idea. Food for thought, I guess.

[MMcBride]

I should toss out a caveat here as well...

When I say we tried full DQM models - it was full DQM.
THere are two times you can specify DQM.

1 - When you create a new model - select DQM
2 - When you publish a package - select DQM

When we attempted to create full DQM models from the get go we had nothing but problems - it could be the source we are on DB2 10, it could be the DB2 Client on Windows 2008 isn't configured to handle JDBC calls efficiently (Our Cognos environment is in AIX) - so it could be alot of different things...

When we build a CQM Model and then publish packages in DQM mode we haven't had any problems, but we normally only use DQM to support DMR in this mode.

There are a lot of different factors that go into my opinion - because that is all it is, my opinion based on what I have seen at one company... So please take it with a grain of salt :)

Option 1 - massive problems, I should also point out at one point we had 5 seperate tickets open with IBM on this which lead to many different APAR's being submitted and a few "enhancement requests"
Option 2 - No problems but we are being very timid in our deployment

[bdbits]

It was your option 1 that was used by the project we just recently deployed. I do not doubt your problems, just saying we did not see as many in our configuration. It is good for all of us to share what we have seen, so we can avoid problems when a similar configuration is being used.

Interesting that option 2 works ok for you so far. We've not done that yet. We will be experimenting with DQM-at-publish-time in the next few months, in anticipation of gradually migrating all of our packages to 64-bit unless it does not work for some reason.