A major outage from Atlassian because of a bad script has Steve thinking about the challenges of recovering from mistakes. When we are making changes to portions of our data and we need to plan for mistakes to occur and ensure we can restore the data.
2022-04-22
184 reads
Continuous backup in Cosmos DB doesn't quite work as Steve would expect. He has a few comments on why it is important you know how your backup and restore system works.
2022-02-21
425 reads
2022-02-18
426 reads
2021-11-12
463 reads
2021-11-05
498 reads
2021-10-18
377 reads
Sometimes just running a backup isn't enough, especially in this era of ransomware. Steve has a few thoughts on backup strategies and recovery skills.
2021-08-09
429 reads
2021-02-08
461 reads
Without a good backup and recovery strategy in place, a DBA should make sure their resume is always up to date. In this article, Greg Larsen discusses what should be considered when developing a backup plan.
2020-12-17
One of the most important responsibilities for a DBA is to ensure that a database can be restored in case of corruption, a dropped table, or another disaster. In this article, Greg Larsen explains the different types of backups available with SQL Server.
2020-12-01
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
Comments posted to this topic are about the item Building AI Governance and Policies-...
Why is sql doing a full scan VS seeking on the index? I've included...
We have a report that has multiple tables that list the top 15 performers...
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
CityID,
StartDate,
EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers