Please explain the SeeMoreData Query Governor?
People often execute queries against live OLTP systems. When these queries are either poorly written for performance, or the user is analyzing vast quantities of data in real-time against a live OLTP system, this can have the effect slowing overall response for mission-critical applications. SeeMoreData has been written to accommodate for that, and gives the Administrator the right to determine at a system-wide level and with individual user overrides, how long queries can run for at various times of the dat, and the governor can be set. The governor has two thresholds, the warning threshold and the timeout threshold. Say the Administrator decided that anyone running a query in production between the hours 9 a.m. and 4 p.m. will be given a warning message after 10 seconds, giving the user the option to kill the query. However after 30 seconds, the timeout threshold is reached. This means that anyone running a query that takes more than 30 seconds will have the query automatically termi
Related Questions
- Can you please explain the implementation of query language and OLAP technology in data warehouse and data mining?
- Can you please explain the implementation of query language and OLAP technology in data warehouse and data mining?
- Explain how data is physically secured. Is the data center locked-down to authorized individuals?
- Explain how data is physically secured. Is the data center locked-down to authorized individuals?
- Explain the default transaction attribute for an EJB?
- Please explain the SeeMoreData Query Governor?
