You need to implement changes to the system to reduce contention and improve performance of the SalesOrderDetail table. Which three actions should you perform? (Each correct answer presents part of th

Question

Options

• AUse (SNAPSHOT] hints in the report queries
• BALTER DATABASE [ProdDB] SET READ_COMMITTED_SNAPSHOT ON
• CALTER DATABASE [ProdDB] SET READ_COMMITTED_SNAPSHOT OFF
• DSET TRANSACTION ISOLATION LEVEL SNAPSHOT
• EUse (TABLOCK) hints in the report queries
• FSET TRANSACTION ISOLATION LEVEL SERIALIZABLE
• GALTER DATABASE [ProdDB] SET ALLOW.SNAPSHOT ISOLATION ON
• HUse (SNAPSHOT] hints in the update statements

• A
  76% (16)
• C
  5% (1)
• D
  5% (1)
• G
  14% (3)

Explanation

The SalesOrderDetail table holds the details about each sale. It is in the Salesschema owned by the SalesStaff Windows group. This table is constantly being updated, inserted into, and read. * Regardless of which office runs a sales force report, the SalesOrderDetail table should only return valid, committed order data; any orders not yet committed should be ignored. * READ_COMMITTED_SNAPSHOT { ON | OFF } ON Enables Read-Committed Snapshot option at the database level. When it is enabled, DML statements start generating row versions even when no transaction uses Snapshot Isolation.Once this option is enabled, the transactions specifying the read committed isolation level use row versioning instead of locking. When a transaction runs at the read committed isolation level, all statements see a snapshot of data as it exists at the start of the statement. Turns off Read-Committed Snapshot option at the database level. Transactions specifying the READ COMMITTED isolation level use locking. ALTER DATABASE SETOptions (Transact-SQL) SET Statements (Transact-SQL)

No community discussion yet for this question.