You are developing an ADO.NET 4.0 application that interacts with a Microsoft SQL Server 2008 server through the SQL Server Native Client. You create a trace DLL registry entry and you register all…

The correct answer is A. ctrl.guid.snac10. ctrl.guid.adonet-ADO.NET only ctrl.guid.msdadiag-MSDADIAG only ctrl.guid.snac10-SQL Server Native Client Providers only (SQL Server 2008) ctrl.guid.mdac-Windows Data Access Components (formerly Microsoft Data Access Components) on Windows 7 only Data Access Tracing in SQL…

Deploying and Troubleshooting Data Access

Question

You are developing an ADO.NET 4.0 application that interacts with a Microsoft SQL Server 2008 server through the SQL Server Native Client. You create a trace DLL registry entry and you register all of the trace schemas. You need to trace the application data access layer. Which control GUID file should you use?

Options

Actrl.guid.snac10
Bctrl.guid.mdac
Cctrl.guid.adonet
Dctrl.guid.msdadiag

How the community answered

(37 responses)

A
84% (31)
B
3% (1)
C
5% (2)
D
8% (3)

Explanation

ctrl.guid.adonet-ADO.NET only ctrl.guid.msdadiag-MSDADIAG only ctrl.guid.snac10-SQL Server Native Client Providers only (SQL Server 2008) ctrl.guid.mdac-Windows Data Access Components (formerly Microsoft Data Access Components) on Windows 7 only Data Access Tracing in SQL Server 2008

Topics

#ADO.NET tracing#SQL Server Native Client#control GUID#diagnostics

Community Discussion

No community discussion yet for this question.

Full 70-516 Practice