By default, WebInspect 7.7 utilizes MS SQL Server 2005 Express to
house the scan information locally. With Express, you have a single
named instance (SQLEXPRESS), and each scan gets its own MDF file (4 GB
limit) to house the scan data. Given that this is your scenario, and
that you are not storing the scans in the MS SQL Server 2005 option,
the items below will be your options.
1. Export each scan individually, and then Import it to the new WebInspect.
Open
the scan on-screen, click on the File menu > Export > Scan >
enable the Include Logs box and/or the desired scrubbing regexes
(maybe) > done. The output will be a single *.SCAN file.
Post the SCAN files to the network, or otherwise move them to the new machine, and then use File > Import on each one.
Tedious, yet simplistic.
2. Move the raw scan data wholesale. The directories
below are defaults, you might have alternative ones defined under the
Edit menu > Application Settings > Directories.
The Scan data is housed here: C:\Documents and
Settings\%USERNAME%\Local Settings\Application Data\SPI
Dynamics\WebInspect\7.0\ScanData\
The linked Scan Log data is housed here: C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\SPI Dynamics\WebInspect\7.0\Logs\
Move
the contents of both folders to the new machine. Go into the
\ScanData\ folder to rename or delete the file, "Scans.XML". This file
catalogs the scans present. Open WebInspect, and the Scans.XML file
will be recreated, causing the added scan data to become visible in the
Manage Existing Scans tool.
Note: Besides your scan data, you may want to
move all sorts of customized data files. Check under the Edit menu
> Application Settings > Directories to understand where you will
want to look for such items. I find it tedious to browse to all of
these various Docs and Settings folders in a hurry, so I generally
recreate the necessary sub-folders under a new directory like
"C:\WebInsepct data\". This may be your opportunity to customize your
own file storage!