Site Server Express - The Database
Both Usage Import and Report Writer connect to a database. The path to this database is always displayed at the bottom of the main panel of the component, as shown in the following figure. When either the Usage Import or Report Writer starts, it tries to reconnect to the last database it used. If the program can't connect to that database because the database has been moved, deleted, or renamed, it prompts you to select a new database.
Usage Import can connect to the same database at the same time, but you should not use them simultaneously.
Creating a Database
A complete Site Server Express Analysis installation includes at least one database. This database can be used to archive and analyze log file data from all sites, so you can aggregate data across all of those sites and analyze trends. However, there are two reasons why you might want to create multiple databases:
Performance Smaller databases can be analyzed faster. If two sites don't ever need to be aggregated, consider keeping their data in separate databases.
Security By keeping data in separate databases, you can control who has access to what data.
Note Merging of databases is not currently supported. You can incorporate earlier versions of Usage Import (Market Focus 1.0 and 2.0) into a database by configuring the Log data source in the Server Manager. (See "The Server Manager" in Chapter 5.)
Microsoft Access-Compatible Versions
The installation program creates a database named ANALYST.MDB in your installation directory. This file is your default database, and both the Usage Import and the Report Writer use this database unless you specify otherwise.
The installation program also creates a file, TEMPLATE.ZIP, in your installation directory. This file is a compressed archive of ANALYST.MDB. If you need to create a new database, simply decompress this archive to a new directory.
Note This archive doesn't have Internet sites configured, and it contains no log file data.
You can rename or move the original ANALYST.MDB. If you do so, then Usage Import and Report Writer don't know where it is, so you'll need to select a new database file when the file browser prompts you. You are given one opportunity to select a valid database. After one failed connect attempt, the program quits.
Checking Database Content
Both Usage Import and Report Writer contain a Database Content window. You can view the contents of the current database by selecting Content on the Database menu. The Database Content window, shown in the following figure, includes six columns of information related to the current database.
In order for the Database Content window to display meaningful information, you must have configured at least one log data source, server, and site with the Server Manager. (See "The Server Manager" in chapter 5.) If no site has been configured, the Database Content window will be empty.
Log data source This column shows all configured sources for log files, which must be named and defined separately, according to the kind of file the source generates.
Server The Server column lists all servers (Web, FTP, Gopher, and Real Audio) for each Log data source, according to the name assigned them with the Server Manager.
Site This column lists all sites currently configured in the database. Each Internet site is identified by the Internet site title you enter with the Server Manager.
SiteId Each site is assigned a unique SiteID. This SiteID is assigned for your convenience in setting up filter criteria in Usage Import and Report Writer. (For example, you can use SiteID=1 instead of Site="marketing web site" as a filter.
First request and Last request The two rightmost columns include the dates of the first request imported for this site and the last request import for this site. These columns are helpful for quickly determining what time periods are stored in the database.
Note To sort the table by any of the elements, double-click the column header.
When you choose Change on the Database menu, the program prompts you to select a new database. If the component is able to open the new database, then the current database is reset for the new selection. If the component is unable to connect to the new database, you remain connected to the original database. If you have upgraded your software since the database was first saved, you are prompted to upgrade the database as well. Since this process is irreversible, you should save a backup copy if you anticipate continuing to run the earlier version of the software.