topic best practice.. advise in QlikView

best practice.. advise

Sun, 14 Aug 2011 23:25:42 GMT

Hi guys,

its been a while since I got time to have a play with QlikView and I have given myself a bit of a big project.

We use CA Clarity, and I was hoping to make a comprehensive dashboard that is capable of showing a whole raft of Clarity data.

I was just wondering, before I get started, if any of you guys have experience of using QlikView with Clarity? (I have created many small QV apps on Clarity, but nothing this big)

for any of these sorts of projects, is it best to read the schema in, table by table and have QlikView perform the joining?

Or is it best to write SQL statements to join sets of tables?

Or is that just preference?

I was also wondering, when one might consider using QVD's

what is the benefit and what are some of the uses of storing data in this way to read (other than quick loading times in a subsequent QVW)

Thanks in advance for any guidance you may offer.

Matt

best practice.. advise

Tue, 05 Jun 2012 12:47:41 GMT

Have you been able to find a solution for reading Clarity data?

Re: best practice.. advise

Mon, 08 Apr 2013 20:58:04 GMT

Hi Matt,

Did you ever get your solution to Clarity data? I'd like to know how it turned out.

Re: best practice.. advise

Thu, 26 Sep 2013 20:21:47 GMT

Matt, COMPASS for PPM, developed by Axis Group, is built on Qlikview and designed for CA Clarity PPM.

There is a CA Clarity harvester supporting all versions of CA Clarity. Feel free to reach out to me if you would like more information or to view a web demo.

Best Regards!

Richard Rodriguez

Solution Strategist

Axis Group, LLC.

Re: best practice.. advise

Thu, 03 Oct 2013 11:24:04 GMT

Hi Richard,

thanks for checking and for reaching out to me recently with news of your new version of your wonderful COMPASS for PPM solution.

We have built various qvw's in-house to satisfy our requirements as our use of Clarity expands.

I'm just trying to drive more and more of our users to it - but some performance issues with our users in Australia (I am in London) have given them a bad 'taste' of qlikview.

Many thanks,

Matt