January 4, 2014 at 4:10 am
Please Provide details regarding below questions:
What special option/argument must be given to the BACKUP LOG command to perform this action?
What options/arguments can be specified in a BACKUP LOG statement to keep inactive log records from being truncated?
Is the sequence of data rows on given data/index page guaranteed to physically match the logical order of rows (i.e. by index key, row id, etc.)?
January 4, 2014 at 4:22 am
What are your thoughts, first of all?
January 4, 2014 at 5:14 am
I don't Know idea regarding those questions dats'y I'm asking to know about that....
Regards,
Manikumar.
January 4, 2014 at 9:50 am
Have you tried looking this up in Books Online? While in SSMS press Shift-F1.
January 4, 2014 at 10:18 am
1 and 2: Google backup log SQL Server
3: Google index data physical order (and be prepared to weed out the true from the false). Rather weird interview question.
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, 2014 at 3:59 pm
Sounds like someone copied questions from a chapter review section of an exam preparation book. They might not even recognize a correct answer if the wording differed from what the author of the book wrote.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply