SQL Server 2008 brings even greater attention to the tail-log within the GUI. As Figure A-1
shows, you now have the option within the GUI of backing up the tail-log and leaving the
database in a NO RECOVERY state.
Figure A-1. The option to back up the tail-log and leave the database in a NO RECOVERY state
This new ability to leave the database in a NO RECOVERY state after backing up the taillog
may seem like a relatively insignificant change, but I??™ve seen far too many tail-logs
destroyed by accident (usually followed by the question, ???So how do I get those changes
back????). Anything that raises awareness of the need to perform a tail-log backup is good,
to my mind.
Native Backup Compression
SQL Server 2008 finally provides a native method for compressing backups. If you??™ve ever
looked closely at the size of an uncompressed backup, you??™ve seen that it is generally the
same size as the original database. Since everyone seems to agree with the mantra, ???Disk
is cheap,??? databases tend to grow at an alarming rate. That means the backups of those
databases grow as well.
Pages:
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604