Online Safety Community

Table combining and concatenation

Concatenate appends the rows of one table to another. Concatenate never merges any rows. The number of rows in a concatenated table is always the sum of the rows of the two input tables. CONCATENATE prefix adds rows to a previously loaded table. The Qlikview script functions JOIN and CONCATENATE can sometimes be used to tackle the same problem, but there are certain differences between them.

In this post, we have emphasized the importance of developing the data model in the star schema format (if possible) and avoiding synthetic tables and circular references. Instead of using link tables, using keytables, and learning some other renaming strategies discussed  in this book, one of the best ways to avoid these issues is to combine tables where it makes sense.

As a note of clarification, the word concatenate in qlik view-speak describes adding the table’s rows onto another table. A qlik view join, however, is best described as appending a table’s column onto another table. Most of the time, developers will need to tell qlik view explicit when to concatenate and join.

Because qlikview is associative, there are times when the software automatically concatenates data fields from two or more separately loaded tables. This automatic concatenation happens when the number and names of the table column are exactly the same. Qlik view will automatically concatenate one statement with another, as the following statements illustrate:


Load product-name, product-ID,

Category from toys. Csv;


Load product-ID, product-name,

Category from electronics.csv;

These two statements are essentially treated as one since both the tables have identical columns (data fields) and number of columns are generally three. All the toy and electronic products are combined into one table-the first listed table. The electronics table will not appear in the data model.

If you want to prevent this automatic concatenation, you must rename fields or use the no concatenate statement. This will prevent the automatic concatenation of the tables even if they have identical names and number of data fields. The following code is an example of the no concatenate statement:


Load product-ID, product-name,

Category from TOYS.csv;

No concatenate load product-ID,

Product-name, category

Form electronics.csv

In most cases, qlik view developers will need to lay out instructions for qlik view to follow concatenation performance. Qlik view calls this forced concatenation, and it is necessary when the tables that have to be combined do not have the same number or names of columns.

A forced concatenation is done using the concatenate prefix (before load) in the script. This will concatenate the table following the concatenate statement to the table created immediately before this statement. Here’s an example of a forced concatenation:


Load product-ID, product-name,

Category from TOYS.csv;

Concatenate load product-ID,

Category from electronics. Csv;

Because we did not specify the table name to concatenate it to in the concatenate statement (concatenate table name is the best practice), the statement appends the rows from electronics . Csv onto the last table created (TOYS). The resulting internal TOYS table has the product-ID, product-name, and category fields. The number of records in the resulting table is the sum of the number of records in TOYS.csv and electronics.csv. The value of product-name in the records coming from electronics.csv is null.

Views: 156

Reply to This

Take our poll!

Take our poll!

Latest Activity

Rachel Min posted a blog post
Profile IconJeff Pacheco, KATE KWAME, Rob Minjock and 2 more joined Online Safety Community
John Robinson posted a blog post

Learn any professional courses for $10 only

Want to enhance your regulatory compliance career by learning a new course? All that it costs is $10. Yes, GlobalCompliancePanel, a provider of professional trainings, is offering hundreds of high value regulatory compliance courses for a mere $10 each.…See More
Adam Fleaming posted a blog post

The GDPR differs Significantly from EC Data Protection Directive 95/ 46

The General Data Protection Regulation (GDPR), which has been codified as Regulation (EU) 2016/679, is a very powerful law regarding the protection of data of the half billion people who live in the European Union (EU). Having come into effect as a result of the European Commission having adapted the proposal for its creation on January 25, 2012; it will replace Directive…See More


Safety - A Prerequisite 11 Replies

Whether working at home or outside, to observe safety should be our pre-requisite. The employer before anything must be sure of the safety of its employees especially the ones working in mines or any…Continue

Tags: products, safety

Started by Enna Henry. Last reply by Tara safe on Wednesday.

Lean Six Sigma Black Belt Training in New York City

Welcome to MSys Training! We thank you for visiting MSys LSSBB training page. Attend our 4 days Lean Six Sigma Black Belt (LSSBB) training program with 100% pass rate, high quality course material,…Continue

Tags: sigma, six

Started by rodriguezcecelia Aug 11.

ITIL Certification Training - MSysTraining

The ITIL® Foundation is an entry level qualification in Information Technology industry. It gives participants information about the key elements, terminologies and concepts used in the ITIL Service…Continue

Tags: itil

Started by rodriguezcecelia Aug 8.

Snowflake and Star Schema in Qlikview

In big name schema all of the facts are stored in one important table and the usage of number one key and overseas key courting different measurement tables are related with the fact desk.SNOWFLAKE…Continue

Tags: processing, transactional, qlikview

Started by Soujanya Naganuri Jul 25.

What is Class Structure in Pega?

Class contains the rule by way of which objects behave. outline rules such as houses, sports, flows, html paperwork, etc. to be had to different subordinate classes. lessons are organized into a…Continue

Started by Soujanya Naganuri Jul 17.



© 2017   Created by Safety Community.   Powered by

Badges  |  Report an Issue  |  Terms of Service