2008-04-17
3,778 reads
2008-04-17
3,778 reads
On my database server I have my databases set to the full recovery model, but the transaction logs get quite big, so I am issuing a BACKUP LOG with NO_LOG. I am not exactly sure if this causes any issues, but I know that I am able to free up space in my transaction log and shrink the file. Is this the correct way to handle this situation?
2008-04-10
4,312 reads
This query gives you an idea of the growth of your database over time.
2013-11-01 (first published: 2008-03-10)
14,375 reads
These scripts were generated to standardize our SQL backup environments, and to remove backups from Maintenance Plans.
2011-12-22 (first published: 2008-01-29)
3,438 reads
Rodney Landrum presents a creative solution for dynamic reporting across all of his SQL Servers, based on use of Red Gate's SQL Backup and SQL Multi Script.
2008-01-22
3,336 reads
Procedure changes all databases' recovery mode to simple and shrinks them all (or at least it tries to).
2012-03-07 (first published: 2008-01-14)
3,906 reads
2012-08-03 (first published: 2008-01-09)
2,318 reads
2008-01-29 (first published: 2007-11-23)
1,958 reads
2011-09-09 (first published: 2007-11-19)
8,927 reads
From one of the SQL Server 2005 storage engine lead developers comes this look at the impact of using the NO_LOG and TRUNCATE_ONLY options.
2007-10-24
3,313 reads
SQL Server 2025 introduces native support for vector data types and external AI models....
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...
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
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...
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