\index[general]{Installing and Configuring SQLite }
\index[general]{SQLite!Installing and Configuring }
-Please note that SQLite both versions 2 and 3 are not network enabled,
-which means that they must be linked into the Director rather than accessed
+Note: SQLite3 implementation remains in the source code, but SQLite3
+is no longer supported by the Bacula project. We recommend that you
+use either MySQL or PostgreSQL.
+
+Please note that SQLite3 is not network enabled,
+which means that it must be linked into the Director rather than accessed
by the network as MySQL and PostgreSQL are. This has two consequences:
\begin{enumerate}
\item SQLite cannot be used in the {\bf bweb} web GUI package.
\end{enumerate}
-Please note that the {\bf ./configure} used to build {\bf Bacula} will need to
-include {\bf \verb:--:with-sqlite} or {\bf \verb:--:with-sqlite3} depending
-one which version of SQLite you are using. You should not use the {\bf
-\verb:--:enable-batch-insert} configuration parameter for Bacula if you
-are using SQLite version 2 as it is probably not thread safe. If you
-are using SQLite version 3, you may use the {\bf \verb:--:enable-batch-insert}
-configuration option with Bacula, but when building SQLite3 you MUST
-configure it with {\bf \verb:--:enable-threadsafe} and
+Please note that the {\bf ./configure} used to build {\bf Bacula} will need
+to include {\bf \verb:--:with-sqlite3}. You should not use the {\bf When
+building SQLite3 you MUST configure it with {\bf \verb:--:enable-threadsafe} and
{\bf \verb:--:enable-cross-thread-connections}.
By default, SQLite3 is now run with {\bf PRAGMA synchronous=OFF} this
-increases the speed by more than 30 time, but it also increases the
+increases the speed by more than 30 time2, but it also increases the
possibility of a corrupted database if your server crashes (power failure
or kernel bug). If you want more security, you can change the PRAGMA
that is used in the file src/version.h.
\index[general]{Testing SQLite }
We have much less "production" experience using SQLite than using MySQL.
-SQLite has performed flawlessly for us in all our testing. However,
+SQLite has performed reasonably well for us in all our testing. However,
several users have reported corrupted databases while using SQLite. For
that reason, we do not recommend it for production use.