Sybase 12.5.1, Руководство пользователя

Страница: 62 / 210

Connecting to Historical Server
48
Historical Server
A single Historical Server can connect to and collect data from multiple
Adaptive Server/Monitor Server pairs. For example, from the same
Historical Server connection, you could create two recording sessions, one
gathering performance data for an Adaptive Server named server1 using a
Monitor Server named server1_MON, and the other gathering data for an
Adaptive Server named server2 using a Monitor Server named
server2_MON. If you do not have a login account that is valid in both
Adaptive Server instances, you would need to create these recording
sessions in different connections to Historical Server, using different login
accounts. The data files from the two recording sessions, however, could
reside in the same directory.
The
hs_create_recording_session
command specifies the Monitor Server
you want to connect to, which indirectly implies the Adaptive Server you
want performance information about.
Create recording sessions. Valid login and password in the Adaptive
Server being monitored.
Execute permission on the
mon_rpc_connect
stored procedure in the
Adaptive Server being monitored. This
permission is required to connect to
Monitor Server.
Create playback sessions using
public recording session files (from
recording sessions whose
protection_level parameter is
public).
Use
hs_list
command on public
recording session files.
Valid login and password in the Adaptive
Server being monitored.
Create playback sessions using
private recording session files
(from recording sessions whose
protection_level parameter is
private).
Use the hs_list command on private
recording session files.
The same login that created the private
sessions, or superuser. In the latter case,
the superuser account must be a valid
login in the Adaptive Server being
monitored.
Activity
Permissions required to perform
the activity