Table of Contents
Advertisement
Overview of Historical Server data files
Permissions on files
General file format
90
•
Data file – each view in a recording session is represented by a data file.
The data file holds all of the samples collected for the view during the
session.
•
Script file – when you define a recording session using the
hs_create_recording_session
specify creation of a SQL script file. The script file defines a Adaptive
Server table for each view in the recording session.
You can use the bulk copy (
tables. If you are a UNIX user, you can put subsets of the fields into separate
Adaptive Server tables if you first invoke the
columns from the file.
All of the historical monitoring data files for a given recording session are
stored in the same directory. This directory is, by default, the directory
specified by the
parameter to the Historical Server start-up command. You
-D
can override this default for a session when you create the session.
The user who starts Historical Server is the owner of the files that Historical
Server creates. The owner has read and write permission on the historical
monitoring files. If the data contained in an historical data file or error message
file is public rather than private, all users and groups have read permission.
All files use newline characters as end-of-record markers. The fields in each
file are variable-length and are separated by commas. All data is stored in
ASCII format, which is compatible with the Sybase bulk copy (
command, the script_type parameter can
) utility to populate existing Adaptive Server
bcp
cut
utility to strip the desired
) utility.
bcp
Historical Server
Advertisement
Table of Contents
