How to monitor your SQL Server instances and databases

Monitoring SQL Server instances and databases provides information necessary to diagnose and troubleshoot SQL Server performance issues, as well as to fine tune SQL Server performance. Optimal performance is not easy to define and set, as there is usually a trade-off between multiple software and hardware factors. It also depends on your environment, business requirements, and company policy.

SQL Server auditing – how to get notified about an event

The reasons for auditing events on SQL Server instances and their objects are various. Some of the most common are to provide accurate records, ensure a protected and safe environment, provide quality control, or to meet certain compliance regulation (e.g. Basel II, HIPAA, PCI, FERPA, GLBA, and SOX) requirements. The auditing process should provide information on specific event types that contains the time, user, object that’s affected by the event, and other relevant data that can help in reconstructing the event.

Transfer SQL logins for users with a large number of SQL-authenticated logins

SQL Server logins are the credentials that enable users to connect to the Database Engine instance. SQL logins are distinguished based on the type of authentication method: Windows-authenticated, SQL Server–authenticated, Certificate, and Asymmetric key. One SQL login can be mapped to only one user in each database.

SQL database refactoring – Finding external references by analyzing object dependencies

SQL Database refactoring becomes more complicated according to the degree of coupling in the database architecture; the more coupled things are coupled the greater the potential impact of any change. The simplest way to describe the concept of coupling is that if changing one module in one module of code or a program requires changes in another part of the same or external application, then coupling exists