Editorial - WMV

Technical Article

Be Prepared

  • Article

Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.

You rated this post out of 5. Change rating

2010-01-04

2,109 reads

Blogs

A New Word: the Wends

By

the wends– n. the frustration that you’re not enjoying an experience as much as...

7 Best Online Advanced SQL Training Courses to Learn in 2024 and Beyond

By

The world runs on data, and SQL is the key to unlocking its secrets....

Manually Updating Redgate Monitor/SQL Monitor Patch Info

By

This post looks at updating the patch information for SQL Monitor/Redgate Monitor without using...

Read the latest Blogs

Forums

There's No Free Lunch with Open-source Software

By Ryan Booz

Comments posted to this topic are about the item There's No Free Lunch with...

Permissions required for SSIS

By ramana3327

To manage ssis project development’s & deployment from visual studio is SSISadmin role is...

Upgrading SSRS 2016 to SSRS 2019 in place

By koln

Server A has SSRS 2016 on it and I would now like to upgrade...

Visit the forum

Question of the Day

Default Objects in Clones

On SQL Server 2022, I do this:

USE model
GO
CREATE TABLE dbo.DBALog
(logdate DATETIME2(3), logmsg VARCHAR(2000))
GO
I then create a new database:
CREATE DATABASE INVENTORY
GO
I install a new database application in here with multiple tables, views, etc. I do not run any queries. I then decide to run this code:
DBCC CLONEDATABASE(INVENTORY, Inventory_clone);
GO
What happens?

See possible answers