
  File     : sstools readme.txt
  Updated  : 7/19/2004

  NEW 7/19/2004

  A new extended version of the ssphysical utility has been added.
  The new utility is named ssxphysical.

  Byte sizes are now shown for projects and files.
  Shared files are identified.
  The daily and cumulative totals now include byte sizes.

  ssaudit.bat has been revided to call xphysical_day_gen.bat.
  xphysical_day_gen.bat is a new batch file which calls the extended utility.

  Users upgrading should :

  1. Backup the old ssaudit.bat
  2. Unpack from this distribution into\Utilities
     ssaudit.bat, xphysical_gen_day.bat, ssxphysical.exe
  3. Check the web site for documentation on the old and new utilties.

  -------------------------------------------------------------------

  Our best efforts have been made to ensure that the tools and
  batch files are as accurate and complete as possible, but
  the usual disclaimer of fitness for purpose applies.

  1. It is suggested that you create this directory to hold the tools:
     c:\Program Files\Microsoft Visual Studio\Common\Vss\Utilities.

  2. All batch files should be opened, and tested before being used
     in production.

     The parameters required by the batch files are documented
     at the head of each batch file.

  3. You will need the latest version of analyze.

     If you upgraded to Microsoft Visual Studio Service Pack 5 (or later),
     you should already have an improved version of analyze.exe
     ( 6.0a Build 8987 at the time of writing ) in the
     c:\Program Files\Microsoft Visual Studio\Common\Vss\Win32
     directory.

     Open a command window in that directory and type 'analyze /?'
     to get a window which will confirm the version and build.

     If not you will need to download an older version of 'analyze'
     ( Version 6.00 Build 8169 ) from Microsoft, and place it in the
     Utilities directory.

     analyze6.exe is a self extracting module that can be downloaded from :
     http://msdn.microsoft.com/ssafe/downloads/download.asp?ID=002

     It is not known why Microsoft have not updated their download page
     with the latest version.

     Although you can use older build with the 'ssaudit' and 'ssrepair'
     batch files you are strongly recommended to upgrade to the latest build.

     You are strongly recommended not to run 'analyze' from the win32
     directory, but to run it from the working 'Utilities' directory.

     Either copy analyze from your win32 directory to the Utilities
     directory, or place the analyze extracted from the download in the
     Utilities directory.  You will also need to copy the supporting dll's
     from the Win32 to the 'Utilities' directory.

     A link on the download page contains a description of the switches
     accepted by 'analyze'. You should read this carefully.

     NEVER RUN ANALZE IN NON-DIAGNOSTIC MODE WITHOUT FIRST ENSURING THAT
     NO USER SESSIONS ARE ACTIVE. FAILURE TO OBSERVE THIS PRECAUTION
     CAN CAUSE DATABASE CORRUPTION.

     Search the eZDS site for further information on 'analyze'

  4. A scheduler to run 'audit.bat automatically overnight is desirable.

     Any scheduler may be used.

     We have found 'ezscheduler' to be simple and reliable. It is also free.

     It may be downloaded from :
     http://www.americansys.com/ezscheduler.htm

  5. A utility to mail reports to the configuration engineer
     The batch files use Jarle Aase's 'wMailTo' utility, available
     as a free download from jgaa.com. Install this in accordance with
     the configuration instructions from the jgaa.com site.
     If you wish to use another mail utility you will need to modify
     the batch files.

  6. The 'ssaudit.bat file runs 'analyze' in diagnostic mode and is safe
     to run with users concurrently accessing the database.
     'Analyse' does considerable IO as it examines the entire database.
     In order to provide the users with maximum performance it is usual
     to run the audit batth file under a scheduler on the night shift.

     The 'repair.bat' file runs 'analyze in repair mode and contains
     code to isolate your database from user access before doing so.

     'ssrepair.bat' calls 'genstats.bat' to create audit snapshots of the
     database state before and after the repair.

     'shutdown.bat' and 'startup.bat' are convenience tools for the
     administrator to enable the database to be taken off, and put back
     on line. They may be used for any operation where a quite database
     is required.

     For convenience you will probably want to set up small driver
     batch files to contain your specific parameters e.g :

     run_audit.bat containing, for example,
     call ssaudit D "D:\vss\data"
                  C "C:\program files\Microsoft visual studio\common\vss\data"
                  myemailid mycompany.com 200

