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. getting data for no of records

getting data for no of records

Scheduled Pinned Locked Moved ASP.NET
helptutorialquestion
5 Posts 3 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.
  • I Offline
    I Offline
    inayat basha
    wrote on last edited by
    #1

    hi all, i an having a data table it contains lakhs of records, when i am getting this data, my browser is becoming slow. how can i get the data to a specific range(example :1000 at one time)paging concept will work for this.... help me.. Regards, S.Inayat Basha.

    P 1 Reply Last reply
    0
    • I inayat basha

      hi all, i an having a data table it contains lakhs of records, when i am getting this data, my browser is becoming slow. how can i get the data to a specific range(example :1000 at one time)paging concept will work for this.... help me.. Regards, S.Inayat Basha.

      P Offline
      P Offline
      PSK_
      wrote on last edited by
      #2

      Yes, paging will definitely work for this scenario. You can implement paging at grid itself or for better performance you can try implementing paging at database level.

      Regards, Prakash Kalakoti

      B 1 Reply Last reply
      0
      • P PSK_

        Yes, paging will definitely work for this scenario. You can implement paging at grid itself or for better performance you can try implementing paging at database level.

        Regards, Prakash Kalakoti

        B Offline
        B Offline
        Brij
        wrote on last edited by
        #3

        In this scenario,Paging at DB side will be better.

        Cheers!! Brij Check my latest Article :Exploring ASP.NET Validators

        P 1 Reply Last reply
        0
        • B Brij

          In this scenario,Paging at DB side will be better.

          Cheers!! Brij Check my latest Article :Exploring ASP.NET Validators

          P Offline
          P Offline
          PSK_
          wrote on last edited by
          #4

          Definitely the DB paging is always a better option, but its little complex in implementation.

          Regards, Prakash Kalakoti

          B 1 Reply Last reply
          0
          • P PSK_

            Definitely the DB paging is always a better option, but its little complex in implementation.

            Regards, Prakash Kalakoti

            B Offline
            B Offline
            Brij
            wrote on last edited by
            #5

            I actually suggested it because in the given scenario ,its having lakhs of records which is not feasible to store at server memory and if its going to be user specific then its going to hazardous for the server and performance of application :) In all it depends on the requirement and the size of data :)

            Cheers!! Brij Check my latest Article :Exploring ASP.NET Validators

            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