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 3 / 6)
It seems the the SpaceObServer Agent, which is a separate process that is running as a system service, has problems accessing the database. Could you please check the Event Log, especially "System" and "Application" for entries that could be related to this issue?
Yes, youcan scan complete hard disks like "C:\".
Yes, you always need an initialscan, even when using NTFS Change Journals.It 's hard to say how muchthe performance impact will be. This depends on the changes done on the observedserver. The most performance will be hold by the database server.It is only recommended touse the NTFS Change Journals, when you need always up to date size information.Normally the update scan isfaster than the initial scan, but this also depends on the number of changes onthe observed file system share.
You can navigate the allways up-to-date online manual at:
The SpaceObServer File Search take its values form the stored information inside the database. This way it is posible to apply many kinds of file "filters" on demand, without any needed rescan.
Unfortunately,the Netware Client for Windows provides no information about compression rateor file ownership to the regular Windows API. Some Samba versions do the samein Unix environments. So developers for Netware or Samba have to add a specialsupport functionality. We will provide this functionality in a later version ofSpaceObServer. Allthe other functions are available on Netware drives.
This option will beavailable with SpaceObServer V3.0 or later.
There are several possibilitiesto enhance the scan performance StoringScan results performs best, if you use a SQL server database, esp. an MS SQLserver database. MS Access should always be second choice when you are in forfastest performance.Localscans are way faster than scans over a network. We advise to installSpaceObServer on every client and to scan locally. You can remote controlSpaceObServer and do your data mining with theSpaceObServer-Client-Application.Thebottle neck of the whole system is the SQL server, so we recommend to use apowerful computer as server computer. 2-3 GB RAM and a fast processor ismandatory for a heavy loaded database server. Althoughit is possible to tweak the database performance by adjusting certain indicesand stats, we can not recommend it, because the database is optimized forsupporting all functions of SpaceObserver. Tweaking the database would(possibly) result in faster scans, but at the costs of a decreased efficiencyin recalling and administration. Comparedto TreeSize, SpaceObServer scans seem to be inferior in terms of scan speed.But SpaceObServer can access archived file system information much faster andoffers a wider range of filtering options for a more detailed file search. Allover that, you can do all this remotely from another computer. Themain question is : What program suits your needs most? A small help in findingan answer could be this summarising table http://www.jam-software.de/treesize/tsizeVsSOS.shtml
That’s possible withSpaceObServer version 3 and later. There are a number of settings as well asthe possibility for automated scanning and reporting controlled by scripts. Forfurther information, please refer to the SpaceObServer manual.
The Details view doesindeed provide a possibility to export to Excel. You will find it in thecontext menu after right-clicking on the result list and choosing SpaceObServer / Export to Excel.
If the MSDE is installedand running, you just have to set up the MSDE as database connection forSpaceObServer by selecting "MS SQL Server" under Views / Options / Database.
You may selecta column under View / Options / Columns after you chose an export medium fromthe topmost drop-down box of the form.