<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Informatica Connector. Why not read from database table? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347377#M705465</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mathilde,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a QVX file can be loaded much faster into QlikView than records from a database table. Mostly databases are on a separate box so you're facing a network bottle-neck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, if you have to load a lot of records, lets say more than a million, QVX is an option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We will probably use the Informatica connector also for the reason that the target (QVX file) could be provided earlier for the QlikView load because database write performance is also a bottle-neck in the whole ETL-process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Ralf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 May 2012 12:08:05 GMT</pubDate>
    <dc:creator>rbecher</dc:creator>
    <dc:date>2012-05-11T12:08:05Z</dc:date>
    <item>
      <title>Informatica Connector. Why not read from database table?</title>
      <link>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347376#M705464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm searching for arguments for implementing the Qlikview Informatica Connector. What are the advantages of creating Qlikview targets in Informatica versus making Qlikview reading from database table with an ODBC connection. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have practical experience?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have a usercase on the Informatica Connector?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mathilde Andersen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 May 2012 11:55:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347376#M705464</guid>
      <dc:creator />
      <dc:date>2012-05-11T11:55:02Z</dc:date>
    </item>
    <item>
      <title>Informatica Connector. Why not read from database table?</title>
      <link>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347377#M705465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mathilde,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a QVX file can be loaded much faster into QlikView than records from a database table. Mostly databases are on a separate box so you're facing a network bottle-neck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, if you have to load a lot of records, lets say more than a million, QVX is an option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We will probably use the Informatica connector also for the reason that the target (QVX file) could be provided earlier for the QlikView load because database write performance is also a bottle-neck in the whole ETL-process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Ralf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 May 2012 12:08:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347377#M705465</guid>
      <dc:creator>rbecher</dc:creator>
      <dc:date>2012-05-11T12:08:05Z</dc:date>
    </item>
    <item>
      <title>Informatica Connector. Why not read from database table?</title>
      <link>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347378#M705466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ralf.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you are saying is that Informatica will spend less time writing a QVX than Qlikview is able to read a database table?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would you prefer to have database, Informatica and QlikView on the same box?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Mathilde&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 May 2012 12:43:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347378#M705466</guid>
      <dc:creator />
      <dc:date>2012-05-11T12:43:29Z</dc:date>
    </item>
    <item>
      <title>Informatica Connector. Why not read from database table?</title>
      <link>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347379#M705467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, it depends. In my experience it could be that creating a QVX file with Informatica and loading this into QlikView is much faster than writing all records into a table (where you probably have data types, constraints like not null and PK etc.) and loading from a table via Select. But, it's depending from so many parameters. The suggestion is to measure the two different approaches.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to prevent a network bottle-neck we suggest to run PowerCenter on the database instance. But for memory and performance reason, the QlikView server should always run on a separate machine!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Ralf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 May 2012 18:18:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Informatica-Connector-Why-not-read-from-database-table/m-p/347379#M705467</guid>
      <dc:creator>rbecher</dc:creator>
      <dc:date>2012-05-13T18:18:33Z</dc:date>
    </item>
  </channel>
</rss>

