Ginger Daniel


SQLServerCentral Article

SQL Log File Too Big

Is your SQL database log file too big? Maybe it is. But maybe it’s not. When log files keep growing and appear to be too big some might suggest switching to Simple recovery, shrinking the log file, and switching back to Full recovery. While this will work to shrink the file and free up disk […]

5 (2)

You rated this post out of 5. Change rating

2022-02-16

24,249 reads

SQLServerCentral Article

Steps for Installing AlwaysOn Availability Groups - SQL 2019

With SQL Server 2012 Microsoft introduced the AlwaysOn Availability Group feature, and since then many changes and improvements have been made.  This article is an update to another article, and will cover the prerequisites and steps for installing AlwaysOn in your SQL Server 2019 environment. Prerequisites Before implementing your AlwaysOn Availability Group (AG), make sure […]

4.5 (2)

You rated this post out of 5. Change rating

2020-12-07

116,725 reads

Blogs

Friday Flyway Tips–Quick Command Line Access

By

One of the things I had to do recently in a demo was access...

A New Word: Aesthosis

By

aesthosis– n. the state of feeling trapped inside your own subjective tastes – not...

A First Look at Redgate’s Subsetter

By

I have been a proponent of subsetting databases in dev/test for a long time....

Read the latest Blogs

Forums

Frustrated trying to get Cross DB Access by Signing SP with Certificate

By Ken McKelvey

Maybe it is lack of caffeine, but I cannot see why the following test...

SSIS Execute Package Fail in SSMS but Agent Job Succeeds

By jerryszz

Hello, I created a SSIS package to transfer data from an XML file to...

Cyber Insurance for War

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Cyber Insurance for War

Visit the forum

Question of the Day

Writing to Clones

I run this code on SQL Server 2019:

DBCC CLONEDATABASE(imdb, imdb_dev)
I then change to the cloned database, imdb_dev, and run some queries. I then run this code while testing:
INSERT dbo.Title (TitleID, Title, DateReleased) VALUES (3234, 'Maestro', '2023')
GO
What happens?

See possible answers