FAQ > Database

Q:	Which types of databases can be used with SpaceObServer?

A:	Currently the following database systems are supported: MS SQL Server 2000-2008R2, Oracle 9-11, My SQL 5, IBM DB2, Firebird 2 and MS Access. You can also use the free Express versions of the commercial database systems.

Q:	Where can I get a SQL Server database?

If you want to use the SQL Server database for data storage, your computer has to be connected to a server, where a SQL Server database is running, or a SQL Server database is running on your local machine. Also, you need a valid account (username and password) for the database access. There are several free Express Editions of popular SQL servers that are supported by SpaceObServer (MS SQL Server Express, Oracle XE, IBM DB2 Express,...). You can download Microsoft SQL Server 2008 R2 Express for free, from within the "Database" tab of the Options dialog.

Q:	Are there any size limits for the database?

If you use a real SQL Server database there is no size limitation by default. MS Access database files always have a size limit of 2 GB and a single table is only allowed to hold 1 GB of the total 2 GB. Most of the free available "Express" versions of the SQL servers are limited in:
The max. used disk space (e.g.: A Microsoft SQL Server 2008 R2 Express database can be no larger than 10 GB, without Transaction log files)
The number of used CPU cores (Microsoft SQL Server 2008 R2 Express: 1 core)
The max. used cache (SQL Server 2008 R2 Express: 1 GB RAM)
If you are planning to scan large amounts of disk space with SpaceObServer, you should always prefer using a real SQL Server database.
Please note that we offer SpaceObServer in a bundle with "Microsoft SQL Server Standard 2008 R2, incl. 1 CAL, Runtime License (perpetual license)" (See: prices).

Q:	How much disk space does the database need?

The space used by the database depends on the number of files, the number of folders and the change rate of your files. Generally the database needs approx. 35 MB per 100.000 files. This is just a rule of thumb and is only valid if the database has been compressed recently (See: "My database allocates a lot..."). When you enable the MD5 checksums for your scans, the database size will increase about 1.5 MB per 100,000 files.

Q:	My database allocates a lot of disk space. Is there a way to reduce the allocated space?

When using SpaceObServer with an MS SQL Server database, the recovery model of the database is set to "Simple" by default. This option prevents the transaction log of the database from growing too fast. The “Auto Shrink” option of this database is also set, which frequently causes an automatic shrink of the data and transaction log files. If you, however, encounter that your database has grown too much, you can do manual shrinks from within your SQL Management Studio on the database (context menu > Tasks > Shrink > Database), or explicit just on the log- or data files (context menu > Tasks > Shrink > Files).

Q:	Is it possible to purge old data from the SpaceObServer database automatically?

In the "Configure Scans" dialog (Scan > Configure Scans) on the tab "Scan Options" you can decrease the number of days to archive data for. This will decrease the needed database size when the first scan is older than the configured archive interval. By default this value is configured to store size data for 365 days. Note that when you decrease this value, the "History" will only be able to show size development for the configured interval.

Q:	Can I use multiple instances of SpaceObServer with the same database?

Yes, this is possible. Just configure the same connection for each instance of SpaceObServer. All scans will be listed in each SpaceObServer user interface and you can generate reports and configure scans from each instance. However by default there will only be one "SpaceObServer Agent"executing scans for a certain root directory. This is the machine where you first add this directory to scan. You can configure the scanning machine(s) from within the "Configure Scans" dialog (See: "Observing Server").

Q:	Is there any way to control the level of sub directories SpaceObServer stores in the database?

SpaceObServer is not able to restrict the level of file system information that is stored in the database. The scan has to traverse the complete file system tree to sum up the directory sizes. We have to store information of all files to implement many important features in SpaceObServer like the oldest, biggest, temporary and duplicate file search and also statistics about file owner and file extensions.

Q: I would like to use SpaceObServer with a MS SQL Server database. How can I create a user account with sufficient access permissions on my database?

A: Open the "Microsoft SQL Server Management Studio" and create a new login at "Security > Logins" (right click > "New Login"). You can now decide to choose "SQL Server authentication" (recommended) or "Windows authentication" on the page "General" of the shown dialog:
1. "SQL Server Authentication": Enter a new "Login name" and a secure "Password" for the new account. Also deactivate the option "Enforce password expiration".
2. "Windows Authentication": Enter an existing user account from your "Active Directory" as "Login name". You can use the button "Search" beside the edit field.
In both cases: Choose your SpaceObServer Database as "Default database". On the page "User Mapping": Check-mark the SpaceObServer database and add the database role "db_owner".
Note: To allow the access via "SQL Server authentication" you need to choose "SQL Server and Windows Authentication mode" as "Server authentication" on the "Security" page of your SQL Server properties (right click on the SQL server > "Properties").

Q: I tried to connect SpaceObServer to a remote MS SQL Server database, but the SQL Server seems to be unreachable. What can I do?

A: Please check the following settings of your MS SQL Server to ensure that remote connections are allowed:
1. Open the "SQL Server Configuration Manager" ("Programs > Microsoft SQL Server > Configuration Tools"), select "SQL Server Network Configuration" and ensure that the protocol "TCP/IP" is activated.
2. Check your Windows Firewall to ensure that the port used by the SQL Server for TCP/IP is not blocked.
3. Open the "SQL Server Configuration Manager", select "SQL Server Services" and ensure that the "SQL Server Browser" is started and the "start mode" is set to "Automatic".
4. Open the "SQL Server Management Studio" ("Programs > Microsoft SQL Server"), connect to your SQL Server, select "Properties" in the context menu of your SQL Server instance, select the page "Connections" and ensure on that the option "Allow remote connections to this server" is activated.
5. Restart your SQL Server in case you had to change any of its configurations (Step 1. or 4.).

Q:	I'm running into problems when I try to connect to an Oracle database. What can I do?

To use SpaceObServer with a non-local Oracle database you need to install an Oracle Client Software with ADO (ActiveX Data Objects) support on your machine. Also ensure that an up-to-date MDAC (Microsoft Data Access Components) version is correctly installed (See: MDAC - Download and Repair). MDAC is provided by your Windows system, by default.

Q:	I can not connect SpaceObServer to my Oracle database from my 64 Bit system. What can I do?

SpaceObServer is a 32 Bit application, but compatible with 64 Bit systems. On 64 Bit systems the default SpaceObServer installation path is located at "C:\Program Files (x86)\". It is a known issue of Oracle connection providers that no connection can be done by an application located in a directory containing the pattern "(x86)" (Oracle note 334528.1). This results in an error "ORA-06413: connection not open" when connecting to an Oracle server. To resolve this issue you should install SpaceObServer to another location on your file system, e.g.: "C:\Program File x86\".

Q:	I want to use SpaceObServer with an Oracle database but I can not start any scan. What can I do?

Before you start any scan you have to ensure that the Oracle account you use for the database connection has the privilege to create trigger and stored procedures. SpaceObServer tries to create these database objects and uses them within the scans. If they do not exist you will get error messages like "ORA-01400: cannot insert NULL into <table_name>".

Q: My Firebird database file seems to be broken. What can I do?

A: Please refer to this side http://www.firebirdfaq.org/faq226/