How to create an auditing profile to track “users” in a custom system using a single SQL Server login

Applies to
ApexSQL Trigger

Summary
his article explains how you can determine exactly which user made a change on an audited database, even if all the users of the system access to SQL server via only one SQL user account. An example would be a web application that connects to the SQL Server via a connection string using a single SQL Server user. The system has its own custom system to manage users by user name and password. The modification, described in this article, will reconcile the custom “users” with the actual changes made to data in SQL Server

Critical steps users should perform immediately after they think a disaster has occurred

Even though it seems as the most practical and simple solution, restoring the database after the disaster can be a two-fold step-back. One, it will most likely recover the data and restore the database to the state/time when the backup was created, but all database changes after the backup will be completely lost. And two, restoring the database will prevent recovery processes with third party tools, since the original MDF and LDF files and the information within will be lost once the restore process finishes. In this article, we’ll discuss adequate steps required to be prepared for a successful recovery using 3rd party SQL Server database recovery tools

Monitoring AlwaysOn Availability Groups

Applies to
ApexSQL Monitor

Summary
This article explains explain how to use ApexSQL Monitor AlwaysOn monitoring which will provide quick insight into the state of an AlwaysOn high availability environment. The graphically presentation of the high availability AlwaysOn environment allows users to visually ascertain the status of the Windows Server Failover Cluster nodes as well as the status of SQL Server AlwaysOn replicas. This visualization also allows for identifying health issues thanks to visualized data flow and color highlighting of the statuses and issues