Hello and welcome to our Knowledge Base. Our experts provide answers to the most frequently asked questions of our customers. Start your information search here to find your answer quickly and easily.
Please enter your query or select one of the above categories.
All entries (Page 6 / 6)
It is possible to compress the allocated space of the database, in MS Access as well as in MS SQL Server. In MS Access you can compress and repair a selected database file using Tools / Database Service Programs / Compress and Repair Database. You can reduce the allocated space of an MS SQL Server database with the SQL-Statement "DBCC SHRINKDATABASE()". SpaceObServer executes this automatically in regular intervals. You can also customize the maximal size of the Transaction Log file of your MS SQL Server database with the Enterprise Manager. Open the 'Properties ' dialog (right click on the database) and select the 'Transaction Log ' tab. Note: If you 'Restrict file growth ' of the Transaction Log do not use the 'Full Recovery Mode ' ( 'Options ' tab / Recovery Model) for this database. In this mode you can not perform any modifying operations on the database if the maximal size of the Transaction Log is reached.
Are you perhaps using a different user account for running the SpaceObServer system service? Does the used account has access rights on this network drive? The account "System" for example does not have access to network drives.
No, SpaceObServer executes scans sequential.
We tested both ways, to scan parallel and to scan sequential and the result was a better performance if the scans were executed sequential. This is because of transaction based lock situations in the database.
SpaceObServer is able to scan server shares remotely via UNC convention or mapped drives.