[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[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.0

SSIS 2005: OLE DB Source task returns 'Query tiemout expired'

Asked by jimhorn in SSIS, SQL Server 2005

Hi All

I'm using SSIS 2005.  I have a SP that runs about nine minutes long in Query Analyzer.  In SSIS I'd like this SP to be the source in an OLE DB Source task, but every time I put it in the OLE DB Source Task Editor, SQL Command text: textarea, and hit the Preview button 30 seconds later it returns a 'Query tiemout expired' error message.

In the Source Task: Properties I have tried this with the CommandTimeout propert set to both 0 and 600000, no luck.
The task is in a container, which does not have a timeout property I can see.
In the Connection Manager I set the Initialization:Connect Timeout and General Timeout task to 0, no luck.

Is there another Timeout property I'm missing?

[+][-]09/28/09 01:44 PM, ID: 25443204Accepted Solution

View this solution now by starting your 30-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: SSIS, SQL Server 2005
Sign Up Now!
Solution Provided By: dodge20
Participating Experts: 1
Solution Grade: A
 
[+][-]09/29/09 05:33 AM, ID: 25448116Author Comment

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 30-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625