mpe_requests
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m47s
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m47s
This commit is contained in:
parent
f488a5319c
commit
50185fb534
@ -27,6 +27,9 @@ By default, a maximum of 100 observations can be edited in the browser at one ti
|
|||||||
* Number (and size) of columns
|
* Number (and size) of columns
|
||||||
* Speed of client machine (laptop/desktop)
|
* Speed of client machine (laptop/desktop)
|
||||||
|
|
||||||
|
### DC_REQUEST_LOGS
|
||||||
|
On SASjs Server and SAS9 Server types, at the end of each DC SAS request, a record is added to the [MPE_REQUESTS](/tables/mpe_requests) table. In some situations this can cause table locks. To prevent this issue from occuring, the `DC_REQUEST_LOGS` option can be set to `NO` (Default is `YES`).
|
||||||
|
|
||||||
### DC_RESTRICT_EDITRECORD
|
### DC_RESTRICT_EDITRECORD
|
||||||
Setting YES will prevent the EDIT RECORD dialog appearing in the EDIT screen by removing the "Edit Row" option in the right click menu, and the "ADD RECORD" button in the bottom left.
|
Setting YES will prevent the EDIT RECORD dialog appearing in the EDIT screen by removing the "Edit Row" option in the right click menu, and the "ADD RECORD" button in the bottom left.
|
||||||
|
|
||||||
|
23
docs/tables/mpe_requests.md
Normal file
23
docs/tables/mpe_requests.md
Normal file
@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
layout: article
|
||||||
|
title: MPE_REQUESTS
|
||||||
|
description: The MPE_REQUESTS table contains an entry with details for every backend request (user, timestamp, job name)
|
||||||
|
og_image: /img/mpe_requests.png
|
||||||
|
---
|
||||||
|
|
||||||
|
# MPE_REQUESTS
|
||||||
|
The MPE_REQUESTS table contains an entry with details for every backend request. This is applied in the [mpeterm.sas](https://code.datacontroller.io/mpeterm_8sas.html) macro.
|
||||||
|
|
||||||
|
In some scenarios this can cause table locks. To avoid this, you can set the [dc_request_logs](/dcc-options/#dc_request_logs) option to NO.
|
||||||
|
|
||||||
|
![](/img/mpe_requests.png)
|
||||||
|
|
||||||
|
## Columns
|
||||||
|
|
||||||
|
There is explicitly **no primary key** on this (transaction) table for the purpose of speedy updates
|
||||||
|
|
||||||
|
- `REQUEST_DTTM num`: Timestamp of the request
|
||||||
|
- `REQUEST_USER char(64)`: The user making the request
|
||||||
|
- `REQUEST_SERVICE char(64)`: The STP/Job being executed (under $apploc/services)
|
||||||
|
- `REQUEST_PARAMS char(128)`: Empty for now
|
||||||
|
|
@ -24,6 +24,7 @@ nav:
|
|||||||
- MPE_DATASTATUS_LIBS: tables/mpe_datastatus_libs.md
|
- MPE_DATASTATUS_LIBS: tables/mpe_datastatus_libs.md
|
||||||
- MPE_DATASTATUS_TABS: tables/mpe_datastatus_tabs.md
|
- MPE_DATASTATUS_TABS: tables/mpe_datastatus_tabs.md
|
||||||
- MPE_LOCKANYTABLE: tables/mpe_lockanytable.md
|
- MPE_LOCKANYTABLE: tables/mpe_lockanytable.md
|
||||||
|
- MPE_REQUESTS: tables/mpe_requests.md
|
||||||
- MPE_REVIEW: tables/mpe_review.md
|
- MPE_REVIEW: tables/mpe_review.md
|
||||||
- MPE_SUBMIT: tables/mpe_submit.md
|
- MPE_SUBMIT: tables/mpe_submit.md
|
||||||
- MPE_SECURITY: tables/mpe_security.md
|
- MPE_SECURITY: tables/mpe_security.md
|
||||||
|
Loading…
Reference in New Issue
Block a user