Results 1 to 3 of 3
  1. #1
    Join Date
    Oct 2011

    Managing a gap in data feed

    I run an database for my department. It currently gets data from 3 sources; User input and 2 remote systems. one of the remote systems that updates the static data; names, address, dob etc. will be going down for a period of time (few months).

    The static data is available from another yet system but not one we can immediately interface with.

    What's the best way to go about managing the gap in static data? I come up with a blank after thinking manual entry

  2. #2
    Join Date
    Jun 2003
    Export the data from the secondary system as flatfiles, if possible.
    If it's not practically useful, then it's practically useless.

    blindman "sqlblindman"

  3. #3
    Join Date
    Feb 2004
    In front of the computer
    Do you need to manage the gap in static data? What are the consequences and does anyone care about them from a business perspective?

    One of the things that we as geeks often miss is that the business knows there will be a gap and doesn't really care.

    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts