Quickstart > Recommend Settings

•

Use a MS SQL Server database for data storage. SpaceObServer deploys 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 2008 R2 Express version (See: MS SQL Server Express).

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

•

Instead of using the "Windows Integrated Security" you should use a specific database user account for database connection (See Options - Database). Otherwise you could run into problems with the database connection of the SpaceObServer system service "SpaceObServer Agent". That is why you should obtain a user account for the service login within the SpaceObServer installation (See SpaceObServer Agent).

•

Install SpaceObServer directly on the server you want to scan. If you want to access scanned information from additional workstations you can use the SpaceObServer Remote Client.
Advantages:
1. You can use the "NTFS Change Journals" to keep NTFS local drives up to date (See Configure Scans Dialog). 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.