Audit_User_DDL

sql-developer-installation-on-windows-amp-linux

In this post, I’ll explain another simple script that kills long running sessions connecting from specific programs e.g. SQL Developer
The script can be tuned to target any specific programs, but I’m mainly defaulting the script to target SQL Developer, as it’s widely used by the developers, moreover, it doesn’t maintain disconnecting the running session properly when the user close the session’s window, keeping the “supposed to be closed” session query running in the database!

It’s crucial for any DBA to get to know about long running queries that can impact the performance of his/her database environment.
Badly coded reports along with developers’ bad habit of using “select *” to navigate data on big tables enforce the DBA to have a kind of an early warning tool to get him aware of such performance threats before it exaggerates.

Do you want to receive an email summarizing the health status of your databases running on the same server without the need to login in each DB in your environment? dbdailychk.sh script is your friend. It performs the following health checks each time it runs against all up & running instance on the server and sends you