Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The SQL Secure Data Collector Job Keys allows allow you to manage the flow of snapshot collection jobs.

Three new parameters have been introduced in Secure 4.0 to manage the flow of snapshot collection jobs. These parameters can be configured from the SQL Secure console under Tools > Configure Collector Job Keys

Image Removed

Collector jobs will now be created with an additional step in the job flow.  This step can be used Use this step to throttle the collector jobs so that they do not overload the SQL Server instance.Three new parameters have been introduced:

Configure the Data Collector Job Keys:

  1. In the menu options, click Tools > Configure Collector Job Keys.

Image Added

2. Set the key parameters: 

Maximum Job Run Count: -

...

Controls the maximum number of SQL Agent jobs that can run before SQL Secure

...

starts to throttle the execution of collector jobs. By default, this is set to 3.

SQL Secure doesn't include Non-SQL Secure jobs

...

when calculating the number of running jobs. 

Check Interval (sec):

...

 - Time in seconds

...

the collector job

...

waits before checking again to see if the number of running jobs is under the jobs throttle limit.

...

By default, this is set to 5 seconds.

Maximum Wait time (sec):

...

 - Time in seconds

...

the job

...

attempts to run before failing.

...

By default, this is set to 28800 seconds (8 hours).


Using the default valuesWith the keys described above, SQL Secure will perform performs the following checks process before running a SQL Secure collector job:1. Check

  • Checks to see if the Maximum Job Run Count has been hit.

...

  • If SQL Secure reaches the throttle limit

...

  • and a new collector

...

  • job is scheduled to start, the collector job

...

  • waits.

...

  • After

...

  • the number of seconds specified in the 'Check Interval' parameter, the job

...

  • checks how many SQL Server agent

...

  • jobs are running.

...

  • The collector job starts if the number of jobs has dipped below the Maximum Job Run Count

...

  • .  If not, then the job

...

  • continues waiting.

...

  • If a job has been waiting for

...

  • the Maximum Wait

...

  • Time,

...

  • the job

...

  • ends the process, and the collector job fails.


Scroll pdf ignore
Excerpt
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
|
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
|
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
|
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
|
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
|
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
|
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
|
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse