TAILIEUCHUNG - Microsoft SQL Server 2008 R2 Unleashed- P144

Microsoft SQL Server 2008 R2 Unleashed- P144: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 | 1374 CHAPTER 37 Locking and Performance could lead to greater page-level contention because the likelihood of the data rows being requested by different processes residing on the same page is greater. Using row-level locking increases the concurrent access to the data. On the other hand row-level locking consumes more resources memory and CPU than page-level locks simply because there is a greater number of rows than pages in a table. If a process needed to access all rows on a page it would be more efficient to lock the entire page than acquire a lock for each individual row. This would result in a reduction in the number of lock structures in memory that the Lock Manager would have to manage. Which is better greater concurrency or lower overhead As shown earlier in Figure it s a trade-off. As lock size decreases concurrency improves but performance degrades due to the extra overhead. As the lock size increases performance improves due to less overhead but concurrency degrades. Depending on the application the database design and the data either page-level or row-level locking can be shown to be better than the other in different circumstances. SQL Server makes the determination automatically at runtime based on the nature of the query the size of the table and the estimated number of rows affected of whether to initially lock rows pages or the entire table. In general SQL Server attempts to first lock at the row level more often than the page level in an effort to provide the best concurrency. With the speed of today s CPUs and the large memory support the overhead of managing row locks is not as expensive as in the past. However as the query processes and the actual number of resources locked exceed certain thresholds SQL Server might attempt to escalate locks from a lower level to a higher level as appropriate. At times SQL Server might choose to do both row and page locking for the same query. For example if a query returns multiple rows and if enough .

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.