Web file manager Free Installation assistance Manual Home page

HTTP Commander DataBase configuration.


Staring from version 8 HTTP Commander supports both of SQLite and MS SQL databases.
For SQLite there is nothing to do and install, everything already included into distibution package and works out of the box. After initial installation HTTP Commander works with SQLite db by default. In order to switch to MS SQL databse you have to ensure that everything is ready.
Requirements for MS SQL db support
  1. HTTP Commander version 8 and later.
  2. MS SQL server - Installation and configuration instructions avaiable here.
We assume that Web server, WebFarm and MS Sql server already installed and function correctly.

Steps to configure HTTP Commander to use MS SQL server data storage.

For a long time SQLite db has been used in the HTTP Commander to store following types of data:
And it was a bottle-neck for installing HTTP Commander in a Load Balancer: when several servers tries to write information into the same SQLite db, it often results to an error because of a blocked db file and as a result missed data.
For single server configurations there are no issue with the SQLLite DB, except the work speed on a large DB.

Here are steps to switch from SQLite to MS SQL db:
You can switch between DB types at any time, as well as change connection string. If you decide to keep the same DB type, but want to use new DB name (location in case of SQLite) , steps will be the same including ability to import data into the new DB.

DbConnectionString - For SQLite DB type values of this setting may contain %DATAFOLDERPATH% placeholder. This paceholder is replaced with the value of the DataFolderPath setting. And by default the value of the DbConnectionString for SQLLite is %DATAFOLDERPATH%\data.db. It allows to store SQLLite data file in the same place as other app data.