Administration

SQLServerCentral Article

Alternatives to SQL Backups

  • Article

All of do us regular backups. Ok, all of us SHOULD do regular backups. In this article Andy comments on why having a backup plan isn't enough and why you should look at some other options for when you need to fix data errors. This really speaks to the goal of minimizing down time using low tech, readily available solutions. If you're not interested yet, we'll add this - one of the alternatives he suggests is Microsoft Access!

You rated this post out of 5. Change rating

2002-10-28

8,434 reads

SQLServerCentral Article

Nightly Failed Jobs Report

  • Article

Do you get tired of reviewing each SQL Agent notifications nightly to determine which SQL Agent jobs failed? Is there a significant number of SQL Agent job notifications that it takes a while to review each? Here is an alternative that allows you to have a single email report of all job failures.

(4)

You rated this post out of 5. Change rating

2002-09-17

11,741 reads

Blogs

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

Read the latest Blogs

Forums

Having Issue deploying a report to an on prem server from PowerBI desktop

By daniel.manke

Using PowerBI Version1.25.9508.3237(January 2026). Installed Microsoft Power BI Desktop (Optimized for Power BI Report...

SQL 2019 instance with AG, across 2 Windows 2016 OS servers - OSin-place upgrade

By millardus

Hi all Can I get some perspective from the community please on performing in-place...

How Long is a Long I/O?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Long is a Long...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers