Future and Scope of Qlik View

  • Hi All,

    My company want to me work on Qlik View but actual i would like to know scope/future of Qlik View Tool.

    Currently i am working as .net developer in current organization.

    Please suggest me. Should i move from development to Qlik View Tool.

    I would like to request please provide own cell number for more clarification. This is urgent for me.

    Because my company given me only 2 days(Till Friday) for decision.

    So, I am humble request you kindly contact with me.

    Regards,

    Sachin.

    9891573054

  • Can't you contact a sales rep of QlickView to ask those type of questions?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • What I know is from evaluating various BI packages, including a deep look & trial of Qlik View. Qlik View has ups & downs, and you need to decide if it works for you. In the end we decided we had too much data (8TB) for Qlik View to be an option (see the Downs section about memory-resident).

    Ups:

    1. Very nice from a user perspective, easy to use, easy to understand.

    2. Have a lot of examples to learn from

    3. Very fast (a big part of this is from being memory-resident, see the Downs section for more on this)

    Downs:

    1. I don't know about your market, but there isn't a lot of Qlik View installations around me and I'm in a pretty good tech market. I wouldn't build a career on it since there's not many places I can go. This could be viewed as an up since the talent pool is limited and you'd be in demand. It's your decision ultimately, but I personally wouldn't go exclusively into Qlik View, other skills age & fade away and it's tough to find your next job.

    (Talk to a Qlik View sales rep to find how many installations are in your market, you may even have a local user group.)

    2. It's completely memory resident (one of the reasons it's fast), so for large datasets you need very big servers. Growing your data means adding RAM, and that's an expensive way to do BI. The product does compress the data so 1GB of your data is much less than that after import to Qlik View, but whether you have enough data to need expensive servers is something only your organization would know.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply