Advertisement

03.06.2008 at 09:34AM PST, ID: 23220343
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
8.2

Cross-Server call to stored proc is "hanging"

Asked by tsb5270 in SQL Server 2005, Visual Studio, .NET Framework 2.x

Tags:

We have a .NET 2.0  windows application that accesses a SQL 2000 database.  A stored proc (which is called pAddSecurityRole) in this database simply calls another stored proc that is in a database on a linked server.  Originally, the linked server was also a SQL 2000 box, but was recently migrated to SQL 2005.  After switching to SQL 2005  pAppSecurityRole stopped working.  I mean, it just hangs.  No error messages.  Nothing.  The proc executes fine when run from SQL Management Studio.  It's only when  the proc is called from the .NET app that it is a problem.  Anyone have any ideas what might be going on and what can be done to solve this problem?
Start Free Trial 
1:
2:
3:
4:
5:
6:

-- Stored Proc called from SQL 2000 DB
ALTER Procedure [dbo].[pAddSecurityRole] (@CompanyNumber AS VARCHAR(4), @RoleName AS VARCHAR(50), @AppShortName AS VARCHAR(50))
AS
 
-- calls a proc on a linked SQL 2005 server
EXEC [LNK-SQLDEV03].Security.dbo.pTestProc
[+][-]03.06.2008 at 10:55AM PST, ID: 21063487

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]03.06.2008 at 11:34AM PST, ID: 21063842

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]03.06.2008 at 12:31PM PST, ID: 21064403

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: SQL Server 2005, Visual Studio, .NET Framework 2.x
Tags: SQL Server 2005
Sign Up Now!
Solution Provided By: tsb5270
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628