• pdanes (10/17/2012)


    Jamie Scharbrough (10/17/2012)


    The answer to this is: It depends.

    I guess I'm approaching this with the view that this is a learning enviornment, and so you should do all the steps for practice.

    That's certainly legit, but I'm trying to comprehend some justifications for various strategies at the same time.

    I think I'm not explaining myself correctly. Here's a more detailed try:

    I can do a nightly full and an hourly trans (9am, 10am, 11am...)

    - or -

    a nightly full and an hourly differential (9am, 10am, 11am...)

    In the first case, if I want to recover to 3pm status, I'll have to use the nightly full and the 9am trans, the 10am trans, the 11am trans, the 12noon trans, the 1pm trans, the 2pm trans and the 3pm trans, to recover all the things that happened that day.

    In the second case, to get to 3pm, I need only the nightly full and the 3pm diff, no?

    If I comprehended the concept of the trans and differential correctly, the differential carries everything since the last full, while the trans carries only the stuff since the last trans, potentially requiring numerous steps to recover to a certain point, while a diff can do it in one step, at the cost of more space used in the backup file.

    Also, if one of the trans files is corrupt, everything after that is unusable, since trans log restores build on one another. If one of the diff files is corrupt, the one just after may well be okay. In a trans recovery chain, -every- file in the chain has to be okay. Restore from a diff file is not dependent on any other diff files.

    Okay I get what you're saying. And yes, you're right; so your best bet WOULD be to do a nightly full and an hourly diff. Sorry, I was hung up on the learning part.

    I'm not sure that's possible, as snapshots only include full backups. There may be a way to do this via a 3rd party tool; I'd have to look into this. (I'm pretty new to snapshots). You can use them for differentials, but you'll need the VSS interface.

    I think my terminology was sloppy here. I meant a backup-restore point, of the sort achieved by one of the normal SQL backup operations, not something exotic.

    Ah, okay. If you want a specific point in time, a simple T-SQL statement could do it, or you could create a job.

    _____________________________________________________________________
    -Jamie Scharbrough
    MCTS: SQL 2008R2