Use This Script to restore Multiple Log backups from a Log Device file. The script will restore all the logs on the device and will leave the databse ready to use after finish. Before running this script you must verify if the database is in No recovery mode or read only state
2005-05-09 (first published: 2005-04-25)
436 reads
If you attach a DB on an SQL Server different from the SQL Server where the DB was initially created, you will usually come up with a situation where a login will be a DB user however, you cannot see this through the login properties screen. That happens because the name of the login exists […]
2005-04-21 (first published: 2005-04-02)
1,410 reads
If you backup your databases to a disk file, you should make sure that these disk files are then being archived to tape. Without this, your ability to recover the database is compromised in the event of a disaster. This script will examine the "archive" flag on all of the backup files to make sure […]
2006-01-22 (first published: 2005-03-25)
301 reads
This is an update/improved version of my script that I'm pleased to see is rated in the top 10! It will script off all of your objects in your database and if they differ from the scripted version in your VSS db, automatically check it in. If the object does not exist in VSS, this […]
2006-03-30 (first published: 2005-03-04)
742 reads
The script runs using vbscript code. It requires the user to enter parameters and run the script. The script uses both trusted and standard connection. The script also generate a log file each time it runs. Copy the code below and save it with .vbs extension.
2005-02-21 (first published: 2005-01-31)
291 reads
This script creates a stored proc that was intended to run from a trigger on the master..sysdatabases for each database creation. Alas. It will create three jobs for each database you apply it to. First, it'll create a job to run a full backup each Sun, at 5am (see below). Those backups will be retained […]
2004-12-16 (first published: 2004-11-11)
376 reads
backup log with truncate only doesn't shrink the file. Actually truncating log needs transaction to truncate. A simple way to reduce the log file size to 1KB.
2004-11-16 (first published: 2004-11-03)
548 reads
SQL Server has a rock solid backup routine that works every time. However the schemes used to implement backups with maintenance plans, Enterprise Manager, etc., are not a smooth or as flexible as what most people require. Author Eli Lieba brings us his strategy and code for ensuring that each database is backed up how he needs it to be, whether a full or differential backup.
2004-10-19
11,329 reads
Easy and Fast way to check Backup details. One line query to check backup status for all the databases. No need to go to each database or schedule job. Even you can use this query in customized application to get all the details on a single screen.
2004-11-25 (first published: 2004-10-14)
734 reads
Allows specification of a database whose properties are to be listed. Allows showing properties by category (Null, false, or true).
2004-11-08 (first published: 2004-08-07)
920 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')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers