Script files as input to Historical Server
46
Historical Server
Errors detected by Client-Library, Adaptive Server, and Monitor Server
use their own error numbering and severity-level schemes.
Script files as input to Historical Server
A convenient way to provide input to Historical Server is to enter the
commands in a text file and use that file as input. The Historical Server
input file is not an
isql
file, and does not necessarily conform to
isql
conventions. For example, Historical Server does not have a comments
feature.
Appendix D, “Examples of Recording Session Views” provides examples
of views that you might use as a start for your input files. These views also
appear in the views file that was installed in the sample/histserver
subdirectory in the installation directory. However, that the file includes
explanatory text that you must remove before using the file as input to
Historical Server.
Connecting to Historical Server
This section contains the following topics:
•
•
•
Required permissions for Historical Server activities
•
Assumptions before connection
Before you can connect to Historical Server:
•
The Adaptive Server whose performance data you want to collect
must be running.
Summary of Contents for 12.5.1
Page 1: ...User s Guide Historical Server 12 5 1...
Page 14: ...xiv Historical Server...
Page 46: ...Configuring multiple instances of Historical Server 32 Historical Server...
Page 56: ...Starting and stopping Historical Server on Windows NT 42 Historical Server...
Page 102: ...hs_terminate_recording 88 Historical Server...