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. Database & SysAdmin
  3. Database
  4. Provide large data updates to desktop users

Provide large data updates to desktop users

Scheduled Pinned Locked Moved Database
announcementdatabasehelpquestion
4 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.
  • K Offline
    K Offline
    Kukreja Sonu
    wrote on last edited by
    #1

    We have a software that provide data from automobile (like parts of various vehicle). For now we release / provide DVDs at a regular interval of time to our users so that they can remain updated with required data. Now we are planning to provide data update via internet i.e. client's DB can be updated based on some information available on internet. This will help us to get rid of releasing monthly DVDs. Any idea on the process? Please help.

    M 2 Replies Last reply
    0
    • K Kukreja Sonu

      We have a software that provide data from automobile (like parts of various vehicle). For now we release / provide DVDs at a regular interval of time to our users so that they can remain updated with required data. Now we are planning to provide data update via internet i.e. client's DB can be updated based on some information available on internet. This will help us to get rid of releasing monthly DVDs. Any idea on the process? Please help.

      M Offline
      M Offline
      Mycroft Holmes
      wrote on last edited by
      #2

      This is simply a method of delivery, all you need to do is get your user to download the DVD content and initiate the local update. So get your app to check a URL for an update available flag and prompt the user to download and then install using your current method.

      Never underestimate the power of human stupidity RAH

      K 1 Reply Last reply
      0
      • M Mycroft Holmes

        This is simply a method of delivery, all you need to do is get your user to download the DVD content and initiate the local update. So get your app to check a URL for an update available flag and prompt the user to download and then install using your current method.

        Never underestimate the power of human stupidity RAH

        K Offline
        K Offline
        Kukreja Sonu
        wrote on last edited by
        #3

        Thanks Holmes. As of now we write all the changed data into an XML file at server and upload the same to a centralized location. Then client downloads the xml and executes queries one by one accordingly to update target DB. But this is a long process: 1. Populating DB at server with change only data 2. Initiate process to prepare XML based on above data. 3. Client downloads the XML and update target DB. This takes around 3-4 days for single run. So, we want to have some other process if possible to minimize the time :(

        1 Reply Last reply
        0
        • K Kukreja Sonu

          We have a software that provide data from automobile (like parts of various vehicle). For now we release / provide DVDs at a regular interval of time to our users so that they can remain updated with required data. Now we are planning to provide data update via internet i.e. client's DB can be updated based on some information available on internet. This will help us to get rid of releasing monthly DVDs. Any idea on the process? Please help.

          M Offline
          M Offline
          Mycroft Holmes
          wrote on last edited by
          #4

          You will get better ideas if you reply through the forum! There are others who will be able to help better than I.

          Kukreja Sonu wrote:

          Thanks Holmes. As of now we write all the changed data into an XML file at server and upload the same to a centralized location. Then client downloads the xml and executes queries one by one accordingly to update target DB. But this is a long process: 1. Populating DB at server with change only data 2. Initiate process to prepare XML based on above data. 3. Client downloads the XML and update target DB. This takes around 3-4 days for single run. So, we want to have some other process if possible to minimize the time

          The more I think about this the nastier it gets, are you up to changing the way you identify your change sets or do you have to stick with the current design/structure? First I would look into change the format from xml to something less verbose. XML is fine for communication as a transport medium it sucks. We use CSV. It sounds like each client has a different requirement!

          Never underestimate the power of human stupidity RAH

          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