Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 66285
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T19:04:45+00:00 2026-05-10T19:04:45+00:00

I have some complex stored procedures that may return many thousands of rows, and

  • 0

I have some complex stored procedures that may return many thousands of rows, and take a long time to complete.

Is there any way to find out how many rows are going to be returned before the query executes and fetches the data?

This is with Visual Studio 2005, a Winforms application and SQL Server 2005.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-10T19:04:46+00:00Added an answer on May 10, 2026 at 7:04 pm

    A solution to your problem might be to re-write the stored procedure so that it limits the result set to some number, like:

    SELECT TOP 1000 * FROM tblWHATEVER 

    in SQL Server, or

    SELECT * FROM tblWHATEVER WHERE ROWNUM <= 1000 

    in Oracle. Or implement a paging solution so that the result set of each call is acceptably small.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have some search functionality that can return tens of thousands of results from
I have a Linq-to-SQL model that uses stored procs in some places to return
I have some idea that it is due to some complex calculation, but i
I have a MVVM application that contains multiple views with some complex IsReadOnly rules
I have a list of objects, that are pre-sorted based on some complex criteria
I have a stored procedure that is performing some ddl dml operations. It retrieves
We have an application that relies on some pretty interesting and complex MS SQL
I have a Entity Framework data mode that I insert to it some stored
Say I have a stored procedure, ProcA. It calls ProcB some of the time,
The tool currently used is Informatica and we have bookend stored procedures that drop

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.