Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Datagrid Development Discussion

Datagrid Development Discussion

Scheduled Pinned Locked Moved ASP.NET
databasexmlcsharpasp-nethelp
5 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    R Thomas 0
    wrote on last edited by
    #1

    Topic : I have a datagrid (ASP.NET) and i need to bind this datagrid to a Database table. the number of records to be bound are, say... 100,000 or more... Agenda : How to achive this, while keeping the datafetching process very fast and the paging with out POSTBACK... Idea: using some XSLT , XML, or something? Adressing Issue : the issue of getting 100,000 or more data can be achieved by keeping a composite key and retriving only 10 records from database at a time to show in the datagrid and when the user clicks next or previous we can use that composite key to fetch the next batch of data. Makin it seem that all the data is in the datagrid but actually its still in the DB. That is not a very big deal Next Issue : the issue of paging without postback, that mean the data should all be out of the DB? or using the XSLT to pipe the data to the cliet and updata the datagrid? Anybody would like to comment on this? thanks and appreciate your time. "Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you."1Thess. 5:16-18

    S 1 Reply Last reply
    0
    • R R Thomas 0

      Topic : I have a datagrid (ASP.NET) and i need to bind this datagrid to a Database table. the number of records to be bound are, say... 100,000 or more... Agenda : How to achive this, while keeping the datafetching process very fast and the paging with out POSTBACK... Idea: using some XSLT , XML, or something? Adressing Issue : the issue of getting 100,000 or more data can be achieved by keeping a composite key and retriving only 10 records from database at a time to show in the datagrid and when the user clicks next or previous we can use that composite key to fetch the next batch of data. Makin it seem that all the data is in the datagrid but actually its still in the DB. That is not a very big deal Next Issue : the issue of paging without postback, that mean the data should all be out of the DB? or using the XSLT to pipe the data to the cliet and updata the datagrid? Anybody would like to comment on this? thanks and appreciate your time. "Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you."1Thess. 5:16-18

      S Offline
      S Offline
      Sarvesvara BVKS Dasa
      wrote on last edited by
      #2

      ** Method to acoid data retricing in postback - Retrive the data in the page load - store it in the cache memory or session memory (see notes below) - Pick from the stored data when you do the post back Notes: If you feel all the data for all the users are same... store in the single Cache variable... else use separate ones. I would recomment cache var than the session, as session var may not supported in all IE settings. There is nothing new under the sun,
      But there are lots of old things we don't know.

      - Ambrose Bierce

      R 1 Reply Last reply
      0
      • S Sarvesvara BVKS Dasa

        ** Method to acoid data retricing in postback - Retrive the data in the page load - store it in the cache memory or session memory (see notes below) - Pick from the stored data when you do the post back Notes: If you feel all the data for all the users are same... store in the single Cache variable... else use separate ones. I would recomment cache var than the session, as session var may not supported in all IE settings. There is nothing new under the sun,
        But there are lots of old things we don't know.

        - Ambrose Bierce

        R Offline
        R Offline
        R Thomas 0
        wrote on last edited by
        #3

        Thanks for ur thoughts... but the thing is bringning 100,000 records to the client side is not a good idea, let alone storing it in cache... Moreover, i am trying to avoid post back... maybe trying to use some XML and XSLT? or something to pipe the data from DB to the client, without storing data in client.... "Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you."1Thess. 5:16-18

        S 1 Reply Last reply
        0
        • R R Thomas 0

          Thanks for ur thoughts... but the thing is bringning 100,000 records to the client side is not a good idea, let alone storing it in cache... Moreover, i am trying to avoid post back... maybe trying to use some XML and XSLT? or something to pipe the data from DB to the client, without storing data in client.... "Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you."1Thess. 5:16-18

          S Offline
          S Offline
          Sarvesvara BVKS Dasa
          wrote on last edited by
          #4

          I dont know the proccess involved in your case. So, I am not sure if you can put the whole stuff in the single cache or individual cache depending on the content/users.... Regarding the postback issue... when we say that the contents are in the cache... it doesnt make much of a difference in the performance for the postback and paging. Anyway, I am not very sure of using the XML etc. There is nothing new under the sun,
          But there are lots of old things we don't know.

          - Ambrose Bierce

          R 1 Reply Last reply
          0
          • S Sarvesvara BVKS Dasa

            I dont know the proccess involved in your case. So, I am not sure if you can put the whole stuff in the single cache or individual cache depending on the content/users.... Regarding the postback issue... when we say that the contents are in the cache... it doesnt make much of a difference in the performance for the postback and paging. Anyway, I am not very sure of using the XML etc. There is nothing new under the sun,
            But there are lots of old things we don't know.

            - Ambrose Bierce

            R Offline
            R Offline
            R Thomas 0
            wrote on last edited by
            #5

            its ok if u are not sure about xml... but the whole point is to NOT keep any records in the cache...:D "Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you."1Thess. 5:16-18

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups