It is easy to get database monitoring wrong. There are several common-sense rules that can make all the difference between a monitoring system that works for you and helps to avoid database problems, and one that just creates a distraction. Adam Machanic spells out the rules, based on his considerable experience with database monitoring.
2013-05-13
8,102 reads
SQL Monitor comes with plenty of metrics, but there are always going to be things that you want to measure that can't be done 'out of the box'. Taking database mirroring as an example, Grant shows that custom metrics can be used to monitor and alert whatever aspect of SQL Server or database that you need.
2013-04-24
2,948 reads
dbWarden is a comprehensive monitoring and alerting solution for SQL Server 2005 or newer. It features an emailed Health Report and includes email and text notifications with customizable metrics for alerts such as Blocking, Long Running Queries and SQL Jobs, CPU %, Log file and TempDB growth.
2013-04-12
25,087 reads
There can be more to managing a SQL Server instance than just examining the performance metrics. There are times when understanding how your system is performing for the application is important.
2013-04-11
1,432 reads
Why would you ever need to automatically monitor the SQL Servers in your care? What is the business value of doing so? What are the important features that a DBA should look for in a performance-monitoring tool? Rodney Landrum gives answers based on long experience.
2012-06-19
3,685 reads
Learn how you can get alerts when you centralize the Event log. This is part 2 of the previous article "How to centralize your SQL Server Event Logs."
2014-05-09 (first published: 2012-05-24)
7,394 reads
In SQL Server, replication is a widely adopted technology for the purpose of real-time data replication between SQL servers. It serves the purpose of keeping data consistent between multiple end points. So the last thing we want to hear from clients is that data is no longer in synch, and as DBA, we don't want to be the last person to realize replication is out of order or broken. Here are some steps you can take to monitor SQL Server replication.
2011-10-26
3,444 reads
It is never a good idea to let your users be the ones to tell you of database server outages. It is far better to be able to spot potential problems by being alerted for the most relevant conditions on your servers at the best threshold. This will take time and patience, but the reward will be an alerting system which allows you to deal more effectively with issues before they involve system down-time.
2011-09-01
3,959 reads
This script quick tip for those who will accurately monitor sessions on SQL Server.
2011-08-16 (first published: 2011-08-02)
1,658 reads
Using linked connections you can collect system information on your Oracle server from SQL server.
2011-06-06
3,459 reads
Here’s a way to centralize management, rotate secrets conveniently without downtime, automate synchronization and...
This may or may not be helpful in the long term, but since I’m...
By Steve Jones
“I’m sick of hearing about Red Gate.” The first article in the book has...
Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...
I have read that the collation at the instance level cannot be changed. I...
hi our on prem STD implementation of SSAS currently occupies about 3.6 gig of...
In SQL Server 2022, I run this code:
CREATE SEQUENCE myseqtest START WITH 1 INCREMENT BY 1; GO CREATE TABLE NewMonthSales (SaleID INT , SecondID int , saleyear INT , salemonth TINYINT , currSales NUMERIC(10, 2)); GO INSERT dbo.NewMonthSales (SaleID, SecondID, saleyear, salemonth, currSales) SELECT NEXT VALUE FOR myseqtest , NEXT VALUE FOR myseqtest , ms.saleyear , ms.salemonth , ms.currMonthSales FROM dbo.MonthSales AS ms; GO SELECT * FROM dbo.NewMonthSales AS nmsAssume the dbo.MonthSales table exists. If I run this, what happens? See possible answers