TAILIEUCHUNG - Microsoft SQL Server 2008 R2 Unleashed- P49

Microsoft SQL Server 2008 R2 Unleashed- P49:SQL Server 2005 provided a number of significant new features and enhancements over what was available in SQL Server 2000. This is not too surprising considering there was a five-year gap between these major SQL Server 2008 is not as much of a quantum leap forward from SQL Server 2005 | 424 CHAPTER 14 Database Backup and Restore The frequency of changes to the data and method by which it is changed The acceptable amount of data loss in the event of a failure The acceptable recovery time in the event of a failure First you must establish what your backup window will be. Because SQL Server allows dynamic backups users can still access the database during backups however this affects performance. This means you should still schedule backups for low-activity periods and have them complete in the shortest possible time. After you establish your backup window you can determine your backup method and schedule. For example if it takes 4 hours for a full backup to complete and the database is quiescent between midnight and 6 00 . you have time to perform a full backup each night. On the other hand if a full backup takes 10 hours and you have a 2-hour window you should consider monthly or weekly backups perhaps in conjunction with filegroup differential and transaction log backups. In many decision-support databases populated with periodic data loads it might suffice to back up once after each data load. Backup frequency is also directly tied to acceptable data loss. In the event of catastrophic failure such as a fire in the server room you can recover data only up to the point of the last backup moved offsite. If it is acceptable to lose a day s worth of data entry nightly backups might suffice. If your acceptable loss is an hour s worth of data hourly transaction log backups would have to be added to the schedule. Your backup frequency affects your recovery time. In some environments a weekly full backup plus transaction log backups taken every 10 minutes provide an acceptable data loss factor. A failure a few days after backup would require a full database restore and the application of hundreds of transaction logs. Adding a daily differential backup in this case would vastly improve restore time. The full and differential backups would be restored .

TỪ KHÓA LIÊN QUAN
TAILIEUCHUNG - Chia sẻ tài liệu không giới hạn
Địa chỉ : 444 Hoang Hoa Tham, Hanoi, Viet Nam
Website : tailieuchung.com
Email : tailieuchung20@gmail.com
Tailieuchung.com là thư viện tài liệu trực tuyến, nơi chia sẽ trao đổi hàng triệu tài liệu như luận văn đồ án, sách, giáo trình, đề thi.
Chúng tôi không chịu trách nhiệm liên quan đến các vấn đề bản quyền nội dung tài liệu được thành viên tự nguyện đăng tải lên, nếu phát hiện thấy tài liệu xấu hoặc tài liệu có bản quyền xin hãy email cho chúng tôi.
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.