Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

smsinger3 (Programmer) (OP)
11 Sep 02 16:07
I run the exact same site on 2 servers.  I use a datareader to cycle through my main data.  It look like this:

   While drRecords.Read()
        Call DetailLine(intI)
   End While

One one server, it very fast. On the other it is so slow it usually times out. I have narrowed the line to the first time the "While drRecords.Read()" is called.  It literally takes about 75 seconds for 65 rows.  The weird thing is this runs slow on a server with 4gig of ram and 4processers.   It runs extrememely fast on a crappy test server.

Both servers have .Net sp2 and mdac 2.7.

Any ideas why it's running slow?

Thanks for your help!

Steve
link9 (Programmer)
11 Sep 02 22:02
could be a network problem between the web server and the data server...

possibly the "crappy" server has a better connection to the data store...  this was the case once for me in ASP classic.

Keep in mind that the datareader is a connected object, so it's only going to be as fast as it's connection to the data.  Generally speaking, the datareader should be a very high performance object.

smsinger3 (Programmer) (OP)
30 Sep 02 22:09
For anyone interested... the entire problem was a database problem.  Even though the test and database were basically defined as the same,  they both were different enough that the production database used different indexes that made the entire query about 2 minutes slower that it should.  How frustrating!

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close