If true, once created, journal will run all SQL scripts stored under Initializers collection prior to starting executing any requests. In most implementation this is used to initialize necessary tables.

Settings specific to CircuitBreaker, which is used internally for executing request batches.

Connection string to a SQL database.

Maximum time given for executed DbCommand to complete.

Isolation level of transactions used during query execution.

Maximum size of single batch of operations to be executed over a single DbConnection.

Maximum size of requests stored in journal buffer. Once buffer will be surpassed, it will start to apply OnBufferOverflow(IJournalMessage) method to incoming requests.

Maximum number of batch operations allowed to be executed at the same time. Each batch operation must acquire a DbConnection, so this setting can be effectively used to limit the usage of ADO.NET connection pool by current journal.

Database specific naming conventions (table and column names) used to construct valid SQL statements.

Settings specific to replay filter rules used when replaying events from database back to the persistent actors.