Explore topic-wise InterviewSolutions in .

We can use macros for various purposes LIKE for reloading the APPLICATION and to create OBJECT.

We can use macros for various purposes like for reloading the application and to create object.

Gauge CHART and list BOX have only EXPRESSION and no DIMENSION.

Gauge chart and list box have only expression and no dimension.

We can USE only TWO DIMENSION.

We can use only two dimension.

A straight table is MUCH BETTER at the time of SORTING as COMPARED to the pivot table as we can sort it ACCORDING to any column as per our choice. But it is not good for grouping purpose.

A straight table is much better at the time of sorting as compared to the pivot table as we can sort it according to any column as per our choice. But it is not good for grouping purpose.

BAR GRAPH we will USE.

BAR Graph we will use.

Pivot Table: A pivot table is better at the time of grouping. We can also show pivot table LIKE a cross table which is a BENEFICIAL feature. But there is one disadvantage of it which is if we have to sort a pivot table than we have to sort it first according to the first DIMENSION then to the next.

Pivot Table: A pivot table is better at the time of grouping. We can also show pivot table like a cross table which is a beneficial feature. But there is one disadvantage of it which is if we have to sort a pivot table than we have to sort it first according to the first dimension then to the next.

With the help of MINI Chart we can SET TYPE of MODES instead of VALUES in table mode. 

With the help of Mini Chart we can set type of modes instead of values in table mode. 

In Trellis chart we can create array of chart BASED on first DIMENSION. Bitmap chart are ALSO MADE of trellis DISPLAY.

In Trellis chart we can create array of chart based on first dimension. Bitmap chart are also made of trellis display.

It is used for set of GROUPS. MOSTLY used in aggregated function like SUM (YEAR), etc.

It is used for set of groups. Mostly used in aggregated function like sum (year), etc.

We GENERALLY uses BAR chart, line chart, COMBO chart, scatter chart, GRID chart, ETC.

We generally uses bar chart, line chart, combo chart, scatter chart, grid chart, etc.

No, it depends on the data structure and the type of data. The more rows of data and the wider each record is in terms of number of fields the more RAM is needed. If a field contains many different distinct values more RAM is required than if the number of distinct values is LOW. Certain CHARTS may demand a large PORTION of RAM while being calculated.

No, it depends on the data structure and the type of data. The more rows of data and the wider each record is in terms of number of fields the more RAM is needed. If a field contains many different distinct values more RAM is required than if the number of distinct values is low. Certain charts may demand a large portion of RAM while being calculated.

There are several good home PAGES on the INTERNET about WINDOWS installer.

There are several good home pages on the Internet about Windows installer.

No, the overwriting of files is handled by the WINDOWS installer SERVICE itself which USES the Windows File Protection RULES.

No, the overwriting of files is handled by the Windows installer service itself which uses the Windows File Protection rules.

The LATEST VERSION can be FOUND on MICROSOFT’s HOME page.

The latest version can be found on Microsoft’s home page.

In the “Windowssystem32” folder find the file CALLED “msi.dll”, open PROPERTIES and GO to the “version” PAGE.

In the “Windowssystem32” folder find the file called “msi.dll”, open properties and go to the “version” page.

The Windows installer and msi packages guarantees that the program is installed in a way that does not create CONFLICTS with other PROGRAMS or with Windows. It also facilitates correct uninstall, should you want to remove QlikView at a LATER point in time. Windows Installer and msi packages is the installation method RECOMMENDED by Microsoft and is required for all certification of software products with Windows.

The Windows installer and msi packages guarantees that the program is installed in a way that does not create conflicts with other programs or with Windows. It also facilitates correct uninstall, should you want to remove QlikView at a later point in time. Windows Installer and msi packages is the installation method recommended by Microsoft and is required for all certification of software products with Windows.

The QlikView INSTALLATION PACKAGE uses Windows installer technique and you MUST have VERSION 2.0 or higher running on your system. If the package isn’t DEPLOYED by a system administrator with a deployment tool, the account that is to run the installation must have administrator privileges.

The QlikView installation package uses Windows installer technique and you must have version 2.0 or higher running on your system. If the package isn’t deployed by a system administrator with a deployment tool, the account that is to run the installation must have administrator privileges.

The use CASES for QVX are still being DISCOVERED, and I’m sure we’ll see some interesting uses. The scenario I CURRENTLY understand is to provide data to Qlikview when there is no ODBC provider.

The use cases for QVX are still being discovered, and I’m sure we’ll see some interesting uses. The scenario I currently understand is to provide data to Qlikview when there is no ODBC provider.

QVD is a proprietary file format provided by QlikView for STORAGE. Only QlikView software can read and WRITE to QVD files.

The QVX is in an open format performance file for storage of QlikView DATA. A customer or THIRD party can create QVX files on any platform, without needing Qlikview software.

QVD files will typically LOAD faster than a QVX file.

QVD is a proprietary file format provided by QlikView for storage. Only QlikView software can read and write to QVD files.

The QVX is in an open format performance file for storage of QlikView data. A customer or third party can create QVX files on any platform, without needing Qlikview software.

QVD files will typically load faster than a QVX file.

No OPTIMIZED LOAD only APPLIES to QVD.

No optimized load only applies to QVD.

I recommend PUTTING the QVD generators in a separate "LOADERS" folder. Make this a mounted folder in QVS and SCHEDULE reloads as needed. Use NTFS permissions to hide the folder from standard AP USERS A number of questions were asked about the QVX FORMAT. I haven’t had much experience with QVX yet. Rob Patterson has indicated he will schedule a QlikLearn webinar specifically on the topic of QVX.

I recommend putting the QVD generators in a separate "Loaders" folder. Make this a mounted folder in QVS and schedule reloads as needed. Use NTFS permissions to hide the folder from standard AP users A number of questions were asked about the QVX format. I haven’t had much experience with QVX yet. Rob Patterson has indicated he will schedule a QlikLearn webinar specifically on the topic of QVX.

The BUFFER prefix does not provide incremental load when LOADING from a DBMS. SUBSEQUENT reloads will load from the buffered file system QVD, but NEW rows will not be fetched from the database.

When used with a load from txt files, BUFFER will provide automatic incremental load. Subsequent reloads will ADD new DATA from the file to the buffered QVD.

The BUFFER prefix does not provide incremental load when loading from a DBMS. Subsequent reloads will load from the buffered file system QVD, but new rows will not be fetched from the database.

When used with a load from txt files, BUFFER will provide automatic incremental load. Subsequent reloads will add new data from the file to the buffered QVD.

QVDs may be refreshed frequently. EXACTLY how frequently depends on your data VOLUMES and architecture. REFRESHING every 30 minutes is COMMON, and I have seen intervals of 5 minutes. Frequent refresh of large volumes usually requires INCREMENTAL load, which is covered in the Reference Guide and the Forums.

QVDs may be refreshed frequently. Exactly how frequently depends on your data volumes and architecture. Refreshing every 30 minutes is common, and I have seen intervals of 5 minutes. Frequent refresh of large volumes usually requires incremental load, which is covered in the Reference Guide and the Forums.

Using QVDS could speed up your overall process by ALLOWING multiple reloads to load from the qvd instead of GOING to the database over the slow WAN link. The QVD should live at the client end of the link – where the qvw is RELOADING.

Using QVDs could speed up your overall process by allowing multiple reloads to load from the qvd instead of going to the database over the slow WAN link. The QVD should live at the client end of the link – where the qvw is reloading.

Nothing but Qlikview can read from QVDs, so no, DB2 cannot read directly from a QVD.

In the same script that creates the QVD with the store statement: STORE mytable INTO mytable.qvd (qvd);

You can also create a CSV copy for other consumers:

The csv file can be read by any number of programs, including an ODBC text driver or a bulk database loader. You can use QV to do the ETL and then push csv files back into a DATA Warehouse, using SOMETHING LIKE SQL Server DTS or other data pump.

Nothing but Qlikview can read from QVDs, so no, DB2 cannot read directly from a QVD.

In the same script that creates the QVD with the store statement: STORE mytable INTO mytable.qvd (qvd);

You can also create a CSV copy for other consumers:

The csv file can be read by any number of programs, including an ODBC text driver or a bulk database loader. You can use QV to do the ETL and then push csv files back into a Data Warehouse, using something like SQL Server DTS or other data pump.

Optimized vs non-optimized load has two IMPACTS: Load duration and Server RAM usage. If your application is relatively small or you do not have concerns about the impact, don’t spend time trying to maintain an optimized load. Some of the SCRIPT techniques used to maintain optimized can make your script harder to follow.

If, for a given DOCUMENT, you have concerns about load duration or RAM usage, then making the effort to maintain an optimized load would be worthwhile.

Optimized vs non-optimized load has two impacts: Load duration and Server RAM usage. If your application is relatively small or you do not have concerns about the impact, don’t spend time trying to maintain an optimized load. Some of the script techniques used to maintain optimized can make your script harder to follow.

If, for a given document, you have concerns about load duration or RAM usage, then making the effort to maintain an optimized load would be worthwhile.

QVDs are created by SCRIPT in a QVW EXECUTED by the reload process. Schedule the reload as you would the reload of a user FACING qvw, using the QLIKVIEW Enterprise Management Console (QEMC) or a batch file.

QVDs are created by script in a QVW executed by the reload process. Schedule the reload as you would the reload of a user facing qvw, using the Qlikview Enterprise Management Console (QEMC) or a batch file.

You can generate QVDs from each model and then LOAD all the QVDs to form the larger model. You can generate all QVDs from a qvw with a SIMPLE loop. You can add this code to each of your model qvws.

You can generate QVDs from each model and then load all the QVDs to form the larger model. You can generate all QVDs from a qvw with a simple loop. You can add this code to each of your model qvws.

GOOD question. We use WHERE 1=1 to force the un-OPTIMIZED load required by MAPPING LOAD. I’m hopeful that if Qlikview were changed to CONSIDER 1=1 as an optimized load, they will also recognize that MAPPING LOAD should be non-optimized.

Good question. We use WHERE 1=1 to force the un-optimized load required by MAPPING LOAD. I’m hopeful that if Qlikview were changed to consider 1=1 as an optimized load, they will also recognize that MAPPING LOAD should be non-optimized.

MAPPING tables may be loaded from a QVD, but it must be an un-optimized load (this is SOMETIMES called “unwrapping”).

MyMap:

MAPPING LOAD F1, F2 FROM sometable.qvd (qvd);

The above mapping table will be created but it will appear to be EMPTY when USED in MAP USING or Apply Map(). No error, just no resulting mapping. One workaround is to create a condition that will cause an un-optimized load. We want all the rows, so we create an always-true condition that will return all rows.

MyMap:

MAPPING tables may be loaded from a QVD, but it must be an un-optimized load (this is sometimes called “unwrapping”).

MyMap:

MAPPING LOAD F1, F2 FROM sometable.qvd (qvd);

The above mapping table will be created but it will appear to be empty when used in MAP USING or Apply Map(). No error, just no resulting mapping. One workaround is to create a condition that will cause an un-optimized load. We want all the rows, so we create an always-true condition that will return all rows.

MyMap:

Sorting (ORDER BY) is only POSSIBLE with Resident (already in memory) FILES. Sorting is not possible when READING from files.

Sorting (ORDER BY) is only possible with Resident (already in memory) files. Sorting is not possible when reading from files.

As of QV10SR2, the XML header in a QVD file CONTAINS the NAME of the QVW that CREATED the QVD as WELL as file sources and database connections/SQL statements.

As of QV10SR2, the XML header in a QVD file contains the name of the QVW that created the QVD as well as file sources and database connections/SQL statements.

QVD FILES are stored uncompressed. A QVD contains the physical representation of an in-memory Qlikview Table. This “RAM IMAGE” format is what allows an optimized QVD load to be so quick. The physical blocks of disk are READ directly into RAM, “ready to go”. Because QVD is the RAM image, there is no compression.

QVD files are stored uncompressed. A QVD contains the physical representation of an in-memory Qlikview Table. This “RAM image” format is what allows an optimized QVD load to be so quick. The physical blocks of disk are read directly into RAM, “ready to go”. Because QVD is the RAM image, there is no compression.

QVD FILES are STORED in the FILE SYSTEM.

QVD files are stored in the file system.

Scatter Chart : The scatter chart plots data points representing combinations of expressions, iterated over one or several dimensions. Both axes are CONTINUOUS, representing one expression each.

Grid Chart :The grid chart is a variant of the scatter chart that plots dimension values on the axes and uses an expression to determine the PLOT SYMBOL. It can also SHOW a third dimension in the form of SMALL pie charts as plot symbols.

Scatter Chart : The scatter chart plots data points representing combinations of expressions, iterated over one or several dimensions. Both axes are continuous, representing one expression each.

Grid Chart :The grid chart is a variant of the scatter chart that plots dimension values on the axes and uses an expression to determine the plot symbol. It can also show a third dimension in the form of small pie charts as plot symbols.

CONTAINS all UI ATTRIBUTES in a SINGLE file, when new objects are created they can PICK up from the theme.

Contains all UI attributes in a single file, when new objects are created they can pick up from the theme.

Transforms columns into rows by DIMENSIONS (eg. in Excel where have cols for description then ONE col PER month).

Transforms columns into rows by dimensions (eg. in Excel where have cols for description then one col per month).

HOLDS an OPINION on BASIC DATA PRESENTATION.

Holds an opinion on basic data presentation.

Pivot DATA is grouped. Partial SUMS can be shown in pivot tables, but not STRAIGHT.

Pivot data is grouped. Partial sums can be shown in pivot tables, but not straight.

Count DISTINCT / if then else / where field is null / SORTING TEXT / Now() FUNCTION.

Count distinct / if then else / where field is null / sorting text / Now() function.

DOCUMENT / USER / PERSONAL SERVER / SHARED Server.

Document / User / Personal Server / Shared Server.

Can KEEP re-useable CODE SNIPPETS; calculate VALUES for global use, maintaining state of objects.

Can keep re-useable code snippets; calculate values for global use, maintaining state of objects.

Similar to calculation condition but the OBJECT is removed from the screen RATHER than displaying a message.

Similar to calculation condition but the object is removed from the screen rather than displaying a message.

STOPS a potentially costly CALCULATION / display taking PLACE by checking a more EFFICIENT expression first.

Stops a potentially costly calculation / display taking place by checking a more efficient expression first.

Merge tables to reduce joins at RUN TIME - CREATE a FLATTER structure at LOAD time.

Merge tables to reduce joins at run time - create a flatter structure at load time.

Drop REDUNDANT ITEMS, REMOVE granularity (eg. drop time from date time FIELDS), split fields (eg. post CODES)

Drop redundant items, remove granularity (eg. drop time from date time fields), split fields (eg. post codes)

USED for mapping data from ONE source onto ANOTHER at load time, very FLEXIBLE in how it does this.

Used for mapping data from one source onto another at load time, very flexible in how it does this.

When retrieving from QVD OPTIMIZED mode is up to 100x QUICKER - only WORKS if you FOLLOW a set of RULES

When retrieving from QVD optimized mode is up to 100x quicker - only works if you follow a set of rules

It's a DATA REPOSITORY file, can aid a robust / QUICK reload strategy, ESSENTIAL for incremental loads of data

It's a data repository file, can aid a robust / quick reload strategy, essential for incremental loads of data

Garbage - columns and rows REMOVED (conditionally)Fill - REPLACE cell values (conditions and strategy)Rotate / CONTEXT / Column / UNWRAP

Garbage - columns and rows removed (conditionally)Fill - replace cell values (conditions and strategy)Rotate / Context / Column / Unwrap