Autocommit

The Autocommit VLDB property determines whether a commit statement is automatically issued after each SQL statement for a database connection. You have the following options:

• ON: A commit is automatically issued after each SQL statement by the database connection: By default, a commit is issued automatically after each SQL statement. This allows you to query a database without having to manually issue commit statements and other required transaction control commands.
• OFF: No commit is automatically issued after each SQL statement by the database connection: Commit statements are not issued automatically after each SQL statement.

Multiple SQL statements are required for various reporting and analysis features in MicroStrategy. When multiple SQL statements are used, each can be viewed as a separate transaction. If your database is being updated by a separate transaction, ETL process, or other update, this can cause data inconsistency with each SQL statement, since each SQL statement is returned as a separate transaction. Disabling automatic commit statements includes all SQL statements as a single transaction, which can be used in conjunction with other database techniques to ensure data consistency when reporting and analyzing a database that is being updated. For example, if reporting on an Oracle database you can use this in conjunction with defining the isolation level of the SQL statements.

Be aware that if you disable automatic commit statements for each SQL statement, these transaction control commands must be included for the report. If you are using Freeform SQL or creating your own SQL statement for use in MicroStrategy, these can be included directly in those SQL statements. For reports that use SQL that is automatically generated by MicroStrategy, you can use the Pre/Post Statement VLDB properties (see Customizing SQL Statements: Pre/Post Statements) to provide the required transaction control commands.

Levels at Which You Can Set This

Project and report