DRAG DROP
You plan to deploy SQL Server 2014.
Your company identifies the following monitoring requirements:
• Tempdb must be monitored for insufficient free space.
• Deadlocks must be analyzed by using Deadlock graphs.
You need to identify which feature meets each monitoring requirement.
Which features should you identify?
To answer, drag the appropriate feature to the correct monitoring requirement in the answer area.
Explanation:
Reference:
* You can use the sys.dm_db_file_space_usage dynamic management view to monitor the
disk space used by the user objects, internal objects, and version stores in the tempdb files.
Additionally, to monitor the page allocation or deallocation activity in tempdb at the session
or task level, you can use the sys.dm_db_session_space_usage and
sys.dm_db_task_space_usage dynamic management views. These views can be used to
identify large queries, temporary tables, or table variables that are using a large amount of
tempdb disk space.
*
/ Use SQL Server Profiler to identify the cause of a deadlock. A deadlock occurs when there
is a cyclic dependency between two or more threads, or processes, for some set of
resources within SQL Server. Using SQL Server Profiler, you can create a trace that
records, replays, and displays deadlock events for analysis./ SQL Server Profiler and SQL Server Management Studio use a deadlock wait-for graph to
describe a deadlock. The deadlock wait-for graph contains process nodes, resource nodes,
and edges representing the relationships between the processes and the resources.
Reference: Troubleshooting Insufficient Disk Space in tempdb
Reference: Analyze Deadlocks with SQL Server Profiler
Sql Trace? I think it should be Sql Profiler. Like mentioned in explanation
What is a ‘Profiler” w/out its workload?!
The workload required for analysis by the SQL Database Tuning Engine, is provided by SQL Profiler; and, SQL Profiler is useless without being able to capture SQL Trace. So, there you have the correlation btw the two.
SQL Server Profiler and SQL Server Management Studio use a deadlock wait-for graph to describe a deadlock.
so
deadlock wait-for graph it is activity monitor
Nope! Deadlock wait-for graphs is produced from SQL Trace; not by Activity Monitor, but by the SQL Profiler.
This, may however be analyzed by the Database Tuning Engine for resolution of bottlenecks.
Database Mirroring
AlwaysOn Avaibility groups
AlwaysOn Avaibility groups
Dynamics Management View
SQL Trace
Policy-Based Management
A maintenance plan
Dynamics Management View
SQL Trace
Database Mirroring
AlwaysOn Avaibility groups
AlwaysOn Avaibility groups
Policy-Based Management
A maintenance plan
[email protected]
Mirroring for ENV1 (Sql version is Standard, so only mirroring met condition – servers will be witness, principal and mirror);
AlwaysOn for ENV2 and 3 (Sql version is Enterprise, so AlwaysOn feature is available)
Log shipping and peer to peer replication have no automatic failover, so cannot candidate for correct answers.