| Overview | Architecture | Download | Register | FAQ | Support |
Yes Directory Sizer is Unicode throughout except for the
IIS pages. If
your IIS server runs on Windows 2000, you can simply edit
include/dszConnection.asp and add a line after <% saying
session.codepage = 65001and so long as you are using Internet Explorer 5 or higher, you should be able to see folder names as they were created by the author whether written in Cyrillic, Thai or English...
Only Microsoft SQL Server 7, SQL Server 2000, and MSDE. MSDE is a light version of SQL Server 7 which is provided free of charge with Directory Sizer if required.
You need to move the database, and the Directory Sizer Central service from the database machine to the new machine, and you need to reset the SQL logins. For instructions on how to do all this see How to move the database to a new machine
Yes, Directory Sizer can size folder trees up to a maximum path from the drive root of around 32000 characters.
The Directory Sizer service collects information at times you specify, rather than whenever you want to see the results of your size, so this is not usually a major concern.
Some examples:
Yes, Directory Sizer 2 works very well on a WAN. The Directory Sizer Central service initiates a scan on a remote machine with an RPC call. The Directory Sizer Scanner service on the remote machine sizes the machine. Later Directory Sizer Central picks up the results in a manner similar to copying a text file across, and then loads the information to the Directory Sizer Database.
Clearly the Directory Sizer Central service and the database server should not be separated by a WAN. In fact they should preferrably run on the same machine.
Not many. Most administration is done through the Admin web interface.
Here is a list of Directory Sizer registry settings.
Security conscious sites may wish to read this Discussion on Directory Sizer security.
Yes. After installing the new version, download and run dirsizeu.exe. There is no problem running both versions concurrently, and the migration lets you set bounds for the data you want to migrate, so running both together won't cause future problems either.
There will however be a noticeable difference between data collected by the old version and that collected by the new version: the new version collects number of files, and reported vs allocated size. Despite collecting more information, the size of the version 2 database will be roughly half that of your current 1.3 database!
Nothing. Your existing registration key works for version 2.x