Options on searching, caching objects or paging on sql server...

Discussion in 'OT Technology' started by hsmith, Aug 31, 2006.

  1. hsmith

    hsmith OT Supporter

    Joined:
    Feb 24, 2002
    Messages:
    124,563
    Likes Received:
    656
    Location:
    Your mother.
    I have an issue...

    Lets say a user is doing a search, the search can either return a result set of 100, or possibly 1000.

    Clearly, I would want to cache the 100 result set in memory. But once the result set gets near 1000, it becomes more inefficent to store all that data, even for a short period of time. (From what I am assuming).

    Would the best option be a "hybrid" approach for this? or strictly stick with sql paging or even caching. the issue w/ sql paging becomes, the more data i have the longer the queries may take. (this isn't true for all queries, two specific sets of searches will have a static set of data, around 30,000 and 600 rows each).

    ojasfdjoi fuck
     
  2. P07r0457

    P07r0457 New Member

    Joined:
    Sep 20, 2004
    Messages:
    28,491
    Likes Received:
    0
    Location:
    Southern Oregon
    use "LIMIT" in your SQL query?
     
  3. hsmith

    hsmith OT Supporter

    Joined:
    Feb 24, 2002
    Messages:
    124,563
    Likes Received:
    656
    Location:
    Your mother.
    well i played with set rowcount and all before, but it led me nowhere.

    i mean, all the data is is a string name and an integer id. but then again, i can't store 1000 rows for 1000 users in cache at once. (well not at once, but worse case, ect)
     

Share This Page