New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admin information via select [CORE774] #1156
Comments
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @pcisarassignee: Dmitry Yemanov [ dimitr ] => |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
Modified by: @pcisarFix Version: 2.1 Beta 1 [ 10141 ] SF_ID: 1339626 => Fix Version: 2.1.0 [ 10041 ] => |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 10798 ] => Firebird [ 15219 ] |
Modified by: @dyemanovWiki Page: https://wiki.firebirdsql.org/wiki/index.php?page=Monitoring+tables |
Submitted by: Valdir Marcos (valdir_marcos)
Votes: 5
SFID: 1339626#
Submitted By: valdir_marcos
Using FB 1.5.2, via Delphi or C/C++ programming, I just
can retrieve from the server:
- name of users conected;
- DBFileName opended in my conection;
- Fetches
- CurrentMemory (in bytes) used by FB
Could I suggest here (or should I address it where to?)
in FB 2.0 or 3.0 about this subject?
The information available could be:
- the DBFileNames opened;
- memory (in MB) used by each FDB;
- fetches used by each FDB;
- locks [Is it possible to show who user(s) is locking
which table(s)/record(s)?] used by each FDB;
- users (name, IP, memory used, fetches, id of the
transactions being used, locks) in each FDB;
- log of when the FB server were started/stoped;
- log of commands sent to the server, like SQL monitors
collect;
Could we get this information via select against
special system tables?
Obtaining this information from select would be much
more ease than by developing programs via API.
Best regards,
Valdir Marcos
The text was updated successfully, but these errors were encountered: