258 reputation
149
bio website twitter.com/davedowns_uk
location Chelmsford, United Kingdom
age 32
visits member for 5 years, 7 months
seen Nov 29 at 22:39

I'm a C#/SQL software developer.


Nov
25
awarded  Caucus
May
21
awarded  Caucus
Jan
30
awarded  Good Question
Oct
17
awarded  Famous Question
Oct
8
awarded  Yearling
Mar
13
awarded  Notable Question
Dec
8
awarded  Nice Question
Aug
10
awarded  Popular Question
Jul
15
asked CodeCollaborator svn access
Jul
14
awarded  Autobiographer
Jun
26
awarded  Beta
May
29
awarded  Scholar
May
29
awarded  Supporter
May
29
accepted How do I reduce transaction log backup size after a full backup?
May
27
awarded  Student
May
27
awarded  Editor
May
27
revised How do I reduce transaction log backup size after a full backup?
added 59 characters in body
May
27
comment How do I reduce transaction log backup size after a full backup?
I suppose I could just do a straight TRUNCATE LOG on the end of the full backup, but that doesn't exactly seem like the best method, I was hoping for some alternatives... What would be the benefits of doing daily full backups rather than diffs? That just seems to use more space for relatively little benefit. I also can't switch to simple recovery as I need the level of granularity the hourly log backups give. Finally, I'm unsure how moving the optimisations to a script would help, surely I'd still have the same problem just less frequently?
May
27
asked How do I reduce transaction log backup size after a full backup?