Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 912417 - Last Review: February 15, 2006 - Revision: 1.2
The module information is represented incorrectly when you profile managed code that is running in SQL Server 2005 by using performance tools in Visual Studio Team Edition for Software Developers
Bug #: 408396 (SQLBUDT)
SYMPTOMS
When you use performance tools in Microsoft Visual Studio Team Edition
for Software Developers to profile managed code that is running in Microsoft SQL Server 2005, the
information about SQL Server integration with the Microsoft .NET Framework common
language runtime (CLR) module is represented incorrectly.
For
example, if you try to profile managed code of a user-defined function in SQL
Server 2005, you may notice that the name of the user-defined function is
incorrectly represented as
LRStubOrUnknownAddress. Additionally, if you develop your own tool by using the CLR Profiling API, the tool may not work correctly.
CAUSE
This problem occurs because the module load event is not generated with the CLR that is being hosted within the SQL Server process.
WORKAROUND
If you want to profile some part of your managed code, follow these steps:
- Use Visual Studio 2005 to create a separate project that is not a SQL Server
project.
- Profile the separate project.
- Integrate the separate project into a SQL Server
project. Note that the code that you profile cannot reference any SQL
Server objects, such as the SqlContext object.
STATUS
This
behavior is by design.
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Workgroup Edition
- Microsoft Visual Studio 2005 Team System Developer Edition
| kbprb kbsql2005clr kbexpertiseadvanced KB912417 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please