Enable row versioning for lock
You have a database named HR1 that includes a table named Employee.
You have several read-only, historical reports that contain regularly changing totals. The reports use multiple queries to estimate payroll expenses. The queries run concurrently. Users report that the payroll estimate reports do not always run. You must monitor the database to identify issues that prevent the reports from running.
You plan to deploy the application to a database server that supports other applications. You must minimize the amount of storage that the database requires. Employee Table - You use the following Transact-SQL statements to create, configure, and populate the Employee table:
Application - You have an application that updates the Employees table. The application calls the following stored procedures simultaneously and asynchronously: ✑ UspA: This stored procedure updates only the EmployeeStatus column. ✑ UspB: This stored procedure updates only the EmployeePayRate column. The application uses views to control access to data. Views must meet the following requirements: ✑ Allow users access to all columns in the tables that the view accesses. ✑ Restrict updates to only the rows that the view returns. Exhibit -
Both of the stored procedures experience blocking issues. UspB must not abort if UspA commits changes to a row before UspB commits changes to the same row. UspA must not abort if UspB commits changes to a row before UspA commits changes to the same row. You need to specify the transaction isolation levels to enable row versioning.
How should you complete the Transact-SQL statements? To answer, drag the Transact-SQL segments to the correct locations. Each Transact-SQL segment may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll
to view content.
Correct Answer: References: https://technet.microsoft.com/en-us/library/ms175095(v=sql.105).aspx https://technet.microsoft.com/en-us/library/ms173763(v=sql.105).aspx
