Quickstart > Recommend Settings

•We recommend using a MS SQL Server database for data storage. SpaceObServer shows its best scanning and reporting performance in combination with a MS SQL Server database.
If you do not have a licensed copy of MS SQL Server, you can download the free SQL Server Express version (see: MS SQL Server Express).

•The database is the bottleneck of the scanning and reporting performance, therefore the SQL Server should be located on a well-equipped machine (min. 2 GB RAM; dual or quad core).
Note: The SQL Server does not have to be located on the machine SpaceObServer is running on.

•Instead of using the "Windows Integrated Security" you should use a dedicated database user account for the database connection (See Options - Database). Otherwise you could run into problems with the database connection of the SpaceObServer scan service "SpaceObServer scan service". That is why you should obtain a user account for the service login within the SpaceObServer installation (See SpaceObServer scan service). If that user account does not have the necessary access rights to the database, no scans can be performed. A guide to create a database user account can be found here.

•You should consider installing SpaceObServer locally on the server you want to scan. If you want to access the scanned information from additional workstations you can use the "SpaceObServer Remote Client".
Advantages of local installation:
1. You can use the "NTFS Change Journals" to keep NTFS local drives up to date (See Configure Scans). We recommend a combination of NTFS Change Journals and a scheduled weekly scan to keep your scanned drives up to date.
2. Local scans normally run faster than network scans.