December 5, 2019 at 12:00 am
Comments posted to this topic are about the item Database Backup Types
December 5, 2019 at 1:10 pm
Nice one, sergey
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
December 5, 2019 at 3:15 pm
Nice one, sergey
Agreed. I'm not sure why 3 people's votes came out at a low "3". I gave it a 5.
The unexpected good thing about it is that the number of incorrect answers actually show a really bad thing... a lot of people don't know backups deep enough.
To be honest, I think this would make a great pre-interview question.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 3:29 pm
Thanks for the instructive question - even though I got it wrong (mistakenly thought choice 4 was true).
-- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
December 5, 2019 at 9:26 pm
Am I the only one who struggled with item 1 thinking "What if the previous log backup was done with COPY_ONLY?"
December 6, 2019 at 7:30 am
Am I the only one who struggled with item 1 thinking "What if the previous log backup was done with COPY_ONLY?"
COPY_ONLY will not break the backup chain. They can also not be used as a base for further differential backups
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
December 6, 2019 at 4:40 pm
True, but a COPY_ONLY log backup will not truncate the log, which is what I was getting at.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply