Hitachi Vantara Pentaho Community Forums
Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Drop index

  1. #1

    Default Drop index

    Hi, i wrote an "Execute SQL script" in this way:

    "DROP INDEX IX_TMP_SOGGETTI_1 ON TMP_SOGGETTI1;"

    This script is correct for "SQL Server" but not "Oracle" (only "DROP INDEX IX_TMP_SOGGETTI_1;").

    Can you help me?


    Thanks in advance,
    Roberto

  2. #2
    Join Date
    May 2006
    Posts
    4,882

    Default

    So what is there to help?

    You know they're different, and you know the diferences?

    Regards,
    Sven

  3. #3

    Default How can I do?

    I should write the script so that is good for both connections.
    How can I do? There is an object that can delete an index?

    Thanks in advance,
    Roberto

  4. #4
    Join Date
    May 2006
    Posts
    4,882

    Default

    There's no step/job entry yet to do that (yet)

    In practice it's pretty unusual that you switch databases.

    Regards,
    Sven

  5. #5

    Default

    If you have different database engines then you need different connection data, too... if you use JNDI then you could, of course, use one PDI transformation to connect to different DBs depending on the system you are running it on, but yes, that should be uncommon.

    If it is indeed the case then you could use some step to find out any system-specific information (IP address via Get System Information or maybe some SQL query) and then use a filter to send your stream either to the Oracle specific side or to the other-db-specific side...

    Cheers,

    Axel

  6. #6

    Default Why unusual?

    Quote Originally Posted by sboden View Post
    In practice it's pretty unusual that you switch databases.
    Why unusual?

    The ETL must only create a data warehouse SQL Server or Oracle on the basis of a parameter input.

  7. #7

    Default

    Mmmm... why do you need your DW on two different platforms? Anyways, if you have a parameter then you can use it to filter... so you can have two different SQL steps for your two different databases.

    Cheers,

    Axel

  8. #8
    Join Date
    May 2006
    Posts
    4,882

    Default

    For the unusual part... most setups work with 1 kind of database. It happens rarely that people want to run the same ETL on different kind of databases. And there are some restrictions in place in PDI to make it pretty hard to do this ("unintentional" by the way).

    If you would want to use it to use different kind of database between development and production, that's just plain silly.

    Regards,
    Sven

  9. #9

    Default :-|

    The ETL is to succeed in building a DWH regardless of platform (1 ETL for multiple platforms).

    Bye,
    Roberto

  10. #10

    Default Thanks

    Quote Originally Posted by sboden View Post
    If you would want to use it to use different kind of database between development and production, that's just plain silly.
    It is not silly, is a commercial need. For the types of data we used the meta data types and we set the connection parameters.

    Thanks,
    Roberto

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.