Hello,
i have two questions :
1 - it's a better solution to save a database SQL with
log technic than a full save ' For a good restoration.
Without speak of all data restore possibility , just the
technic of restore.
2 - it's true that it's necessary to have the double disk
space to restore a full database ? Ex : 30 Go free space
to restore a database of 15 Go
Thanks for responseIt is depend what kind of restore possibility do you want.
If you will make only FULL BACKUP with Recovery Model Simple(SQL 2K) or
'Truncate Log on chk. point' checked(SQL 7)
you will not able to restore DB on any point of time. Aslo you will lose all
changes since last FULL BACKUP in case of DB corruption.
With Tr.Log BACKUP for example you will make FULL BACKUP once per some
period of time. Let say every night.
And then LOG BACKUP every let say hour.
So you will have the chain:
FULL BACKUP
LOG BACKUP
LOG NACKUP
LOG BACKUP
...
FULL BACKUP
In this scenario in case of DB corruption and if Log will corrupted too, you
will lose only data since last LOG BACKUP.
So, if you'll make LOG BACKUP hourly, maximun for one hour.
Regards
---
All information provided above AS IS.
"dtc" <anonymous@.discussions.microsoft.com> wrote in message
news:03fe01c39f18$6edb8ea0$a101280a@.phx.gbl...
> Hello,
> i have two questions :
> 1 - it's a better solution to save a database SQL with
> log technic than a full save ' For a good restoration.
> Without speak of all data restore possibility , just the
> technic of restore.
> 2 - it's true that it's necessary to have the double disk
> space to restore a full database ? Ex : 30 Go free space
> to restore a database of 15 Go
> Thanks for response
No comments:
Post a Comment