"So why the @#$% doesn’t it do that?"

4.00K viewsQuantrix Feedback

“DataNAV functionality allows you to easily drag and drop database columns as dimensions and/or data items. “

““”DataNAV uses the power of the database to execute aggregation queries and allows you to quickly get the results you need.”“

““”DataNAV is useful for doing ad-hoc queries on data sets of any size.””
“”DataNAV immediately constructs the relevant SQL commands, extracts the data, aggregates it and displays it in the matrix: you see the structure filled with data from the database or data store immediately.””

I’m connecting to a large Oracle database for GL transactions. There’s nothing easy, quickly, or immediately about the process. Every single modifcation of the matrix puts Quantrix in non-responsive mode for about 10 to 15 minutes. Just changing the update setting from ‘Automatically’ to ‘Manual’ has put Quantrix out of commission for going on an hour now.

So how do I get Quantrix to work as advertised?”


Hi John,

I totally understand your feeling and experience.

I think the DataNav is good to summarize lots of thing and link up everything together ; however, it would make your cpu headache when it comes with too many thing in the category.

For big category items, , I noticed that using Datalink for 2D matrix is a lot faster.

However, DataNav is really a good way to summarize something instead of keep using select / using as functions.



I was using a single processor workstation before and CPU utilization during DataNAV design usually caused 100% CPU utilization under Windows 7 64-bit, and Quantrix was basically unusable. I upgraded my Quantrix workstation to a three CPU machine and the process became at least usable. Set up of the DataNAV query usually resulted in five to ten minute pauses after adding fields to the model, or doing anything with them really (moving them, collapsing them, deleting them). First, I turned off automatic updating. That took hours. Then I began to set up highly restrictive qualifiers (just one accounting period instead of the scores, just one company instead of the hundreds, just one account instead of the hundreds), and Quantrix finally became more workable after each qualifier. So it is working now with highly restrictive qualifiers.

What would be nice is if users had an option to cancel runaway SQL queries. There was sometimes a cancel button presented during some operations, but it still took ten or more minutes to work. It should be as immediate as possible. Also, there is no instruction about how to handle setting up DataNAV with enormous databases. It would have saved me a whole days work if there were. I can see these problems making one believe the program is completely buggy and then giving up on Quantrix, because I was about to. Finally, the suggested base system requirements are completely inadequate for use against a large Oracle database.

Latest Questions

Qloud Losing Formatting 4 Answers | 0 Votes
Meditation on timelines 3 Answers | 0 Votes