<?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 Migration of 2000 Ms-SQL-Server Tables to Cassandra in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277976#M53582</link>
    <description>Hi,&lt;BR /&gt;We have a requirement to migrate around 2000 tables from SQL server to Cassandra(Big Data)&amp;nbsp;Database.&lt;BR /&gt;The jobs are simple in which SQL server table will be mapped to a Cassandra table.&lt;BR /&gt;There is no complex logic. Its just copying&amp;nbsp;data from one table(in SQL SERVER)&amp;nbsp;to another table (in Cassandra)&lt;BR /&gt;SQL_SERVER_TABLE_1------------&amp;gt;Cassandra_Table_1 and so on..&lt;BR /&gt;So for 2000 tables in SQL Server we have to create 2000 jobs to copy data into Cassandra.&lt;BR /&gt;can you&amp;nbsp;please suggest some automation so that we can save time of creating 2000 jobs manually?&lt;BR /&gt;P.S: Note that in Cassandra a table is called a 'column family'. For the sake of clarity I have mentioned it as table.&lt;BR /&gt;Thanks&lt;BR /&gt;Tom</description>
    <pubDate>Wed, 17 Feb 2016 13:04:33 GMT</pubDate>
    <dc:creator>TomG1</dc:creator>
    <dc:date>2016-02-17T13:04:33Z</dc:date>
    <item>
      <title>Migration of 2000 Ms-SQL-Server Tables to Cassandra</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277976#M53582</link>
      <description>Hi,&lt;BR /&gt;We have a requirement to migrate around 2000 tables from SQL server to Cassandra(Big Data)&amp;nbsp;Database.&lt;BR /&gt;The jobs are simple in which SQL server table will be mapped to a Cassandra table.&lt;BR /&gt;There is no complex logic. Its just copying&amp;nbsp;data from one table(in SQL SERVER)&amp;nbsp;to another table (in Cassandra)&lt;BR /&gt;SQL_SERVER_TABLE_1------------&amp;gt;Cassandra_Table_1 and so on..&lt;BR /&gt;So for 2000 tables in SQL Server we have to create 2000 jobs to copy data into Cassandra.&lt;BR /&gt;can you&amp;nbsp;please suggest some automation so that we can save time of creating 2000 jobs manually?&lt;BR /&gt;P.S: Note that in Cassandra a table is called a 'column family'. For the sake of clarity I have mentioned it as table.&lt;BR /&gt;Thanks&lt;BR /&gt;Tom</description>
      <pubDate>Wed, 17 Feb 2016 13:04:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277976#M53582</guid>
      <dc:creator>TomG1</dc:creator>
      <dc:date>2016-02-17T13:04:33Z</dc:date>
    </item>
    <item>
      <title>Re: Migration of 2000 Ms-SQL-Server Tables to Cassandra</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277977#M53583</link>
      <description>Hi,&lt;BR /&gt;Are your 2000 tables same schema structure?&lt;BR /&gt;So far, tCassandraOutput don't support for "Dynamic Schema" feature.&lt;BR /&gt;Best regards&lt;BR /&gt;Sabrina</description>
      <pubDate>Thu, 18 Feb 2016 08:16:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277977#M53583</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-02-18T08:16:17Z</dc:date>
    </item>
    <item>
      <title>Re: Migration of 2000 Ms-SQL-Server Tables to Cassandra</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277978#M53584</link>
      <description>Hi xdshi, 
&lt;BR /&gt;We have a query regarding the above scenario which was raised by Tom. 
&lt;BR /&gt;Lets suppose we have Source with Schema1 and Target with Schema2. And target table structures are same as Source table structures. 
&lt;BR /&gt;But each tables are different from each other structurally. Our requirement is to load all the 2000 target tables with single or less number of jobs. 
&lt;BR /&gt;Please advise this can be done or not. 
&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 23 Feb 2016 11:06:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277978#M53584</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-02-23T11:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Migration of 2000 Ms-SQL-Server Tables to Cassandra</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277979#M53585</link>
      <description>Hi,&lt;BR /&gt;So far, talend big data components don't support for dynamic schema.&lt;BR /&gt;Best regards&lt;BR /&gt;Sabrina</description>
      <pubDate>Wed, 24 Feb 2016 08:20:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Migration-of-2000-Ms-SQL-Server-Tables-to-Cassandra/m-p/2277979#M53585</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-02-24T08:20:52Z</dc:date>
    </item>
  </channel>
</rss>

