Re: SELECT Optimalization

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Adam Skrodzki

    Re: SELECT Optimalization

    Thanks for replay,

    I'm not sure where bottleneck is.
    I suppose the problem is that i read row by row not a package of rows
    in one read, as I've wrote I couldn't find the way to read more rows
    in one fetch
  • Dan Guzman

    #2
    Re: SELECT Optimalization

    Although you read one row at a time in your code, a fast-forward cursor
    basically means that many rows are buffered on the client side in
    anticipation of the next fetch.

    You might check network utilization. If you are reading 400MB of data,
    roughly double that amount for network overhead. I would expect that to
    take over a minute on a 100mb network.

    --
    Hope this helps.

    Dan Guzman
    SQL Server MVP


    "Adam Skrodzki" <adamskrodzki@g mail.comwrote in message
    news:e15088f9-a43b-4a2d-9eeb-89d6ad382f54@l4 2g2000hsc.googl egroups.com...
    Thanks for replay,
    >
    I'm not sure where bottleneck is.
    I suppose the problem is that i read row by row not a package of rows
    in one read, as I've wrote I couldn't find the way to read more rows
    in one fetch

    Comment

    Working...