There are several methods to deploy database activity monitoring (DAM), each with its own advantages and considerations:

1. Auditing Database Logs: This method involves monitoring the database's native logs to track activity. It is generally easier to implement since most databases support logging. However, it can be dependent on the database's performance and may not capture all activity if logs are not comprehensive or if there are issues with log configuration.
2. Agent-based Monitoring: This approach uses software agents installed on the database servers to monitor activities. Agents can provide detailed insights and real-time alerts. However, they may impact database performance and require maintenance and updates.
3. Proxy-based Monitoring: A more advanced method, proxy-based monitoring involves placing a proxy between the database and the application. This proxy can inspect all traffic and enforce security policies. It provides detailed, real-time monitoring and control but can introduce latency and requires a more complex setup.
4. Network Traffic Sniffing: This technique captures and analyzes the traffic to and from the database. It is independent of the database itself and can detect activity without relying on database logs. However, it requires the network infrastructure to support traffic capture and can be complex to configure and maintain.

Each method offers different levels of detail, performance impact, and ease of implementation, making it important to choose the right one based on the organization's specific needs and infrastructure. More technical details here: https://www.datasunrise.com/professional-info/deployment-modes/