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,376 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,439 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,339 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,959 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
Welcome back, my fellow sleuths, to my mystery-inspired blog series! I’m having a ton...
By Steve Jones
This was one of the original values: The facing page has this text: No...
By Chris Yates
For decades, enterprises have thought about data like plumbers think about water: you build...
Comments posted to this topic are about the item Create an HTML Report on...
My wife apparently ask her phone a question and below is what she sent...
Comments posted to this topic are about the item I Love Editorials
What happens when I run this code:
DECLARE @s VARCHAR(1000) = 'apple, pear, peach' SELECT * FROM STRING_SPLIT(@s, ', ')See possible answers