January 4, 2012 at 2:29 am
DBCC ShrinkFile(<name of log file>,<size log file was before abnormal growth>)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 6, 2012 at 10:35 am
Very enlightening. I was actually shrinking my log files in the first and last step of an ETL run LOL. We need a real DBA so badly.
January 6, 2012 at 10:57 am
Good luck in you search. In the meantime, may I suggest this? http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 6, 2012 at 11:08 am
What a great book title :). To give you an idea of how far out of my element I am..I have to read this after I pass my CPA exams, 1 down 3 to go.
January 10, 2012 at 6:00 am
By mistake I choose one star I'm sorry this is great article thanks a lot
January 12, 2012 at 3:48 am
Echoing everyone else's comments - great article!
However, I was all prepared to query your statement in the article:
It is important to note that while a full or differential backup starts a log chain, full and differential backups don't break the log chain
My understanding was always that performing a Full backup would break the log chain, and if you wanted to restore to a given point using your log backups, you would have to restore from the last full backup. That's what I thought copy_only backups were introduced for, to ensure an ad-hoc full backup would not disrupt the log chain.
However, having now tested it against a 2008 R2 instance sure enough taking a full backup does not break the log chain, so I have learned something new today! Thank you! 🙂
But having said that, it begs the question what is the point of copy_only backups now?
January 12, 2012 at 4:16 am
SQLPhil (1/12/2012)
But having said that, it begs the question what is the point of copy_only backups now?
This: http://sqlinthewild.co.za/index.php/2011/03/08/full-backups-the-log-chain-and-the-copy_only-option/
You wouldn't be the first to argue with me about full backups breaking the log chain, it's an (unfortunately) commonly held belief. They've never broken the log chain though.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 12, 2012 at 6:24 am
Thank you very much Gail for clarifying all of this (and for the excellent article on COPY_ONLY). You have certainly added a lot of clarity to my understanding of backups and restores.
Speaking amongst my fellow DBA colleagues we were all under the (misguided) understanding that full backups broke the log chain. In fact, even in some training courses we've been told that this has been the case. It'll be nice to have the opportunity to turn round and inform the instructor for once! 😉
January 12, 2012 at 6:43 am
SQLPhil (1/12/2012)
It'll be nice to have the opportunity to turn round and inform the instructor for once! 😉
😀
Just be polite if you do. Speaking as a occasional trainer and presenter, there's nothing worse than a student who thinks he's right and you're wrong and makes a public issue out of it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 12, 2012 at 6:55 am
GilaMonster (1/12/2012)
...Speaking as a occasional trainer and presenter..
And a darned good one too, may I say ! :w00t:
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 16, 2012 at 7:19 am
Great article, company I contract for are constantly changing the recovery model and shrinking the log then changing the RM back - have presented them with the URL for this, fingers crossed they will see sense! 😉
qh
May 12, 2012 at 10:18 pm
Can we do point in time recovery in Bulk loged recovery model?
If yes then how?
May 13, 2012 at 12:15 am
best_yunus (5/12/2012)
Can we do point in time recovery in Bulk loged recovery model?If yes then how?
Yes but only if there were no minimally logged transactions in the final log file that you want to recover up to the point in time.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2012 at 1:14 pm
Now i got...
Thanks 🙂
May 14, 2012 at 10:57 am
Take a read through this: http://www.sqlservercentral.com/articles/Recovery+models/89664/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 15 posts - 106 through 120 (of 128 total)
You must be logged in to reply to this topic. Login to reply