QlikView Expressor: How Different Databases Handle Partitions

    A database's locking scheme affects how the database handles data written to it on multiple partitions. For example, IBM's DB2 frequently locks the entire table when faced with multiple writes. Write operations on Netezza, Informix, and Sybase databases cannot be partitioned when Mode is set to Update or Delete.

    The following table lists expected results for each of the databases expressor supports.

    DatabaseInsert ModeUpdate/Delete/Merge/Modes
    OracleNo problems expectedNo problems expected
    MS SQLNo problems expectedNo problems expected
    TeradataNo problems expectedNo problems expected
    PostgresNo problems expectedNo problems expected
    MySQL (Community and EnterpriseNo problems expectedNo problems expected
    DB2Locking scheme prevents multiple writes in most casesLocking scheme prevents multiple writes in most cases
    SybaseNo problems expectedLocking scheme prevents multiple writes in most cases
    NetezzaNo problems expectedLocking scheme prevents multiple writes in most cases
    InformixNo problems expectedLocking scheme prevents multiple writes in most cases