70-450 · Question #27
You deploy a new database application to a SQL Server 2008 instance on a server that has 4 processor cores and 64 GB of RAM. The application uses partitioned tables. During testing, deadlocks…
The correct answer is A. Disable partition-level lock escalation. Full-recovery Model - Requires log backups. - No work is lost due to a lost or damaged data file. - Can recover to an arbitrary point in time (for example, prior to application or user error). Work loss exposure - Normally none. - Il the tail of the log is damaged, changes…
Question
You deploy a new database application to a SQL Server 2008 instance on a server that has 4 processor cores and 64 GB of RAM. The application uses partitioned tables. During testing, deadlocks occasionally occur on queries that are attempting to read data. You find out that the deadlocks are related to the table partitions. You need to ensure that the application executes without deadlocks for the read queries. You also need to ensure that dirty reads do not occur. What should you do? (More than one answer choice may achieve the goal. Select the BEST answer.)
Options
- ADisable partition-level lock escalation.
- BMove each partitioned table to its own filegroup.
- CAdd additional database files to each partitioned table.
- DMove the clustered indexes for the partitioned tables to a separate filegroup.
How the community answered
(23 responses)- A74% (17)
- B4% (1)
- C13% (3)
- D9% (2)
Explanation
Full-recovery Model - Requires log backups. - No work is lost due to a lost or damaged data file. - Can recover to an arbitrary point in time (for example, prior to application or user error). Work loss exposure - Normally none. - Il the tail of the log is damaged, changes since the most recent log backup must be redone. Recover to point in time S3. - Can recover to a specific point in time, assuming that your backups are complete up to that
Topics
Community Discussion
No community discussion yet for this question.