2018-09-04 (first published: 2018-08-23)
317 reads
2018-09-04 (first published: 2018-08-23)
317 reads
2018-07-24
876 reads
2018-06-25
901 reads
2018-02-22
804 reads
2018-01-12
898 reads
2017-07-18
996 reads
Have you ever started a database backup or a restore process that runs a long time then wanted to know when it will complete? Knowing when a database backup or restore operation will complete provides you valuable information, especially when you need to perform follow-on tasks that are waiting for the backup or restore process to complete.
2017-05-12
4,017 reads
Microsoft has introduced new extended events in SQL server 2016 which will give us detailed information about restore and backup process.
2016-12-26
2,024 reads
2016-10-19
1,183 reads
Greg Larson explains that SQL Server provides a couple of different ways to delete backup and restore history. If you want to remove backup and restore information for all databases based on a date you can use the sp_delete_backuphistory system stored procedure. Or you can use the system stored procedure named sp_delete_database_backuphistory if you want to remove all backup and restore history for a specific database.
2016-10-04
5,098 reads
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') GOWhat is the identity value for the new row inserted by the insert statement above? See possible answers