The August edition of TechNet Magazine is available on the web now and has the latest installment of my regular SQL Q&A column.
This month's topics are:
Check it out at http://technet.microsoft.com/en-us/magazine/dd776512.aspx.
iAI is obviously the hot new thing and prognostications for the future range from the unicorns-and-rainbows life of idleness for us all to the post-apocalyptic
(This was the editorial for my 300th SQLskills Insider newsletter last week, that I’ve been producing since March 2011! See bottom of browser window to
I’m excited to be presenting at the Pass Summit in November! My pre-con workshop is my absolute favorite to teach Performance Tuning with Waits and
Summer Sale time! Hundreds of dollars lower-than-ever prices on our signature 158-hour Blackbelt training bundle: Check It Out! SQLskills Complete Short Course Bundle $4,575.00 Original
(This post first appeared on SQLperformance.com four years ago as part of a blog series, before that website was mothballed later in 2022 and the
It’s quite common for a company that experiences a corruption-causing disaster, but has no valid backups to restore from and no ability to fail over
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.
3 thoughts on “TechNet Magazine: August 2009 SQL Q&A column”
Paul,
If you use Bulk Logged in a Log Shipping scenario as opposed to Full recovery will everything be applied to the standby server or are there certain actions that will not be shipped? In other words, when we have to bring the standby server online will it be identical to the source or will some data/indexes/etc be missing as a result of running under Bulk Logged?
Regards;
Greg
Nope – everything works perfectly in BULK_LOGGED as far as log shipping is concerned.
Paul,
I discovered that with Veritas Backup Exec backup software, performing a full backup (as described by the software) does not backup the log file too. Just the database — even if your database is set to Full recovery model. Therefore, the log file continues to grow.
In order to manage your log file with Backup Exec, you actually have to schedule another job to perform a backup of the log file. Then your log gets truncated correctly.
For anyone that uses Backup Exec, or any backup software, review your settings and make sure the log file is included in a "full" backup.