To set Job Manager options
Use this option... |
To... |
Default |
---|---|---|
Scheduler Page |
Set the following options. |
— |
Show server time |
Display the local time and the time difference between the desktop and the server at the top of the Calendar tab for each server. |
Selected |
Show recurring executions as one item |
Simplify the display by showing jobs that run multiple times as one job. |
Selected |
Show jobs that run continuously during the day on top of the schedule |
Display the continuously running jobs at the top of the schedule. |
— |
Task List Page |
Set the following options. |
— |
Show steps |
Display each job step on the Job List tab in an expanding row in the list or in a separate pane at the bottom of the window. |
Under each row of a job |
Show history |
Display job history on the Job List tab in a separate pane at the bottom of the window. On Demand—Display history only after clicking Show History. (Selected.) If cleared, history displays automatically when you select a job. |
Cleared |
Advanced |
Click Advanced to set the following options. |
— |
Maximum number of threads |
Specify the maximum number of total concurrent threads to use on target instances to run the jobs. |
3 |
Maximum appointments |
Specify the maximum number of appointments that can display on the Calendar tab. If the number of appointments exceeds this value, appointments may display incorrectly. |
25 |
Show disabled jobs |
Display the jobs that have been disabled. |
Selected |
Refresh job status after start/stop |
Refresh the job status automatically after the job is either started or stopped. |
Selected |
Auto refresh windows tasks every: |
Specify the auto refresh rate in seconds for windows tasks. |
— |
Tip: Click Advanced | Known Applications to add new or change existing masks and icons. A mask is a pattern used to group
To set the Log Reader options
Review the following for additional information:
Use this option... |
To... |
Default |
---|---|---|
Check log file changes every |
Check the log file for changes every so many seconds. |
Selected |
Show uncommitted transactions |
List all the transactions that are not committed. |
Selected |
Reconstruct DDL commands |
Select this option to display both DML and DDL commands |
Selected |
Export all details of the log |
Export all details of the log file. TIP: Select this option to get a full report. |
Not Selected |
Online log reading timeout |
Set the amount of time the log is read before a timeout is reached. |
300 seconds |
Maximum BLOB size |
Set the maximum Binary Large Object (Blob) Data size. |
8000 bytes |
Reconstruction |
Select one or both of the following:
|
Selected |
Search Depth |
Select whether to read the entire log file or only a set number of records in the log file. The options are:
|
100000 |
LiteSpeed requires the following privileges and grants:
Account | Requirement |
---|---|
User account that performs the LiteSpeed installation |
Windows administrator rights and DBA privileges required to
|
User account that runs the LiteSpeed UI Console |
Power User privileges (or some equivalent). NOTE: When executing a Double Click Restore, Windows Vista, Windows Server 2008, and higher require that the Windows user account is an administrator. |
SQL Server service account |
Sysadmin server role privileges required to
TIP: The SQL service account needs at least read\write access to the following directory and all its contents: NOTE: SQL Server Configuration Manager should always be used when changing SQL Server service accounts. |
SQL Agent service account (or a proxy account) | |
Windows or SQL Server accounts specified during instance configuration (Start | All Programs | Quest Software | LiteSpeed for SQL Server | Instance Configuration) |
If you select SQL Server authentication, the SQL Server account must have sysadmin server role privileges, while the Activity Manager service account must have the Log on as a service permission. If you select the Windows authentication method for both the local and central repository, then the Activity Manager service account specified on the Service Account page must have the sysadmin privileges and the Log on as a service permission. NOTE: If the central repository is located on another server, the LiteSpeed Activity Manager service account must have domain rights for two-way communication between the local and central repositories. |
Windows or SQL Server account (Application Button | Repository Registration...) For more information, see About Collecting Statistics in Repositories. |
Db_owner of the central repository (required to retrieve data from the central repository) |
Windows or SQL Server account (Application Button | SQL Server Registration...) |
Sysadmin server role privileges required to
|
TSM with LiteSpeed |
If using TSM, its recommended that the following line be added to the dsm.opt file used by LiteSpeed.
|
There are two options for replicating statistics to the central repository. The first option replicates the LiteSpeed activity. The second option only replicates job status, maintenance plans and log shipping information.
If you did not select to populate the central repository automatically or via a scheduled job during Instance Configuration, you can manually force a replication at any time by calling the ActivityManager.exe file from the command line or using the extended stored procedures.
NOTE: The xp_replicate_activity_statistics command is designed for sync changes between the local and central repositories. LiteSpeed does not contain information about the native backup history because it is a SQL Server native tool. You must use the [LiteSpeedLocal]..[LiteSpeed_ImportNativeHistory] procedure to import the native backup history first into the local repository.
To replicate database and LiteSpeed activity information
On the local repository server, do one of the following:
- Execute dbo.xp_replicate_activity_statistics against the master database.
- From the command line, change the directory until you are in the directory containing the LiteSpeed command-line utilities (Usually, C:\Program Files\Quest Software\LiteSpeed\SQL Server\Engine) and run ActivityManager.exe.
To replicate job, maintenance plans and log shipping information
On the local repository server, do one of the following:
- Execute dbo.xp_replicate_job_statistics against the master database.
- From the command line, change the directory until you are in the directory containing the LiteSpeed command-line utilities (Usually, C:\Program Files\Quest Software\LiteSpeed\SQL Server\Engine) and run ActivityManager.exe -GatherJobStats.
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center