Press Release


External Article

Job overran Custom Metric

This SQL Monitor custom metric tells you if a specific SQL Server Agent job that runs at the same time every day has overrun. The metric is useful when a job can have negative effects on other processes if it overruns.

2013-05-10

2,892 reads

Technical Article

Registration is open for SQL Relay

SQL Relay is an annual community-run series of SQL Server training events across the UK. SQL Relay will run 8, 1-day conferences over the course of 2 weeks starting June 17th. Speakers from Microsoft, global IT companies, and a host of MVPs, are covering topics on DBA, business intelligence, and development.

You rated this post out of 5. Change rating

2013-04-26

3,302 reads

Technical Article

SQL Server Central Webinar Series #23: Safeguard your data offsite with SQL Backup Pro

You may already have a great backup and recovery plan. However, if something were to happen to your databases and you needed to restore from your backups, you’d want to be in control, with the ability to access a copy of those backups quickly, restoring them with minimal downtime and minimal fuss.

In this session Grant Fritchey, SQL Server MVP, will discuss the key reasons why you need to have offsite backups, and the advantages of hosted storage. He’ll address some of the fears surrounding cloud backups, and show how offsite backup is made quick and easy with the new ‘backup to hosted storage’ features in SQL Backup Pro 7.3.

You rated this post out of 5. Change rating

2013-04-23 (first published: )

2,913 reads

External Article

Do you regularly run queries and scripts in SSMS?

SQL Server Management Studio is where most SQL scripts and queries are run, and although it does a decent job, it doesn't provide much help storing, sharing and managing the scripts particularly in the context of a team. Red Gate is considering building functionality into SSMS to help its users consume and share queries and scripts. Please help us by completing this short survey to help us define the requirements.

2013-04-12

3,832 reads

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

Tooling for Success: The Best FinOps Tools and Technologies

By

As a DevOps person, I know that to make FinOps successful, you need more...

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

“We love to debate minutiae”

By

I am guilty as charged. The quote was in reference to how people argue...

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top II

SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

Question of the Day

Restoring On Top II

I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:

-- run yesterday
CREATE DATABASE DNRTest2
GO
USE DNRTest2
GO
CREATE TABLE NewTable (id INT)
GO
Today, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today
USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens?

See possible answers