Press Release


External Article

New Custom Metric: Long Running Job

SQL Monitor’s Job duration unusual alert is a powerful tool for keeping track of most jobs in your SQL Server environment. It works by comparing the running time of any job instance against the median for that job, and identifying when a variation in the job duration could hint at a performance problem. However, if your environment contains big jobs whose durations vary by several orders of magnitudes, it can be tricky to specify what kind of variation is expected and what would be unusual. For these cases, it is possible to go beyond the functionality of the built-in alert with a custom metric.

2013-04-05

2,857 reads

Blogs

Post-quantum key exchange – Insurance policy for your packets

By

AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...

Plan your 2026

By

If you don't have a plan, you'll accomplish it. That's not a good thing.

Another Change

By

Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...

Read the latest Blogs

Forums

Fantasy Football 2026

By Steve Jones - SSC Editor

The thread for the league in 2026. Players from last year have priority.

Certificates expired - Can't restore after creating new certificate

By WebTechie

The previous DBA created a certificate which expired 12/31/2025. I came in hoping to...

advice on diving into devops for managing BI projects

By stan

hi , i know this is a sql server forum but i think my...

Visit the forum

Question of the Day

Which Table I

I have this code in SQL Server 2022:

CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
    SELECT  ProductName
    FROM product;
END;
GO
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned?

See possible answers