Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Facebook Sign In with Google Sign In with OpenID


We have migrated to a new platform! Please note that you will need to reset your password to log in (your credentials are still in-tact though). Please contact if you have questions.
Welcome to the new platform of Programmer's Heaven! We apologize for the inconvenience caused, if you visited us from a broken link of the previous version. The main reason to move to a new platform is to provide more effective and collaborative experience to you all. Please feel free to experience the new platform and use its exciting features. Contact us for any issue that you need to get clarified. We are more than happy to help you.

MsSql v6.5; Large Result Set Problems

When I use a TQuery into a table that produces a large result set (> 100 rows), if I DON'T traverse the result set immediately, after several seconds the server will drop my connection without any notification. This doesn't happen with Interbase or Oracle. Is there a parameter (either BDE or MsSql) that I need to set, or is this just some type of known problem with MsSql? If it's a problem, is there a known fix/work-a-round? If not, is there a 3rd party BDE replacement that corrects this problem? Any additional info on this would be appreciated.

Sign In or Register to comment.