home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.databases:7940 comp.databases.oracle:2240 comp.databases.sybase:351 comp.databases.informix:2465 comp.databases.ingres:1929
- Newsgroups: comp.databases,comp.databases.oracle,comp.databases.sybase,comp.databases.informix,comp.databases.ingres
- Path: sparky!uunet!sun-barr!ames!nsisrv!stars.gsfc.nasa.gov!thompson
- From: thompson@stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040)
- Subject: Validating data imported from text files.
- Message-ID: <18NOV199217192059@stars.gsfc.nasa.gov>
- News-Software: VAX/VMS VNEWS 1.4-b1
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Nntp-Posting-Host: stars.gsfc.nasa.gov
- Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics
- Distribution: usa
- Date: Wed, 18 Nov 1992 21:19:00 GMT
- Lines: 17
-
- I was just told something startling. In an E-mail message from Myron China
- <mryo@ind_maroon.gwl.com>, I was told
-
- problem with flat file xfers is verifying successful completions of both
- the dump and the import. oracle products, for instance, always signal
- a 0 return code whether or not it had a problem. so you end up spooling
- log files and checking them for errors yourself. we also check file
- record layouts for validity before anything goes through.
-
- That's an astonishing statement to me! Our current plan calls for *ALL* data
- imported into the database to come from flat ASCII files generated by other
- programs. Populating the database is supposed to be an automatic process that
- works unattended. Problems are supposed to be signalled when they occur.
-
- Is this the same with the other major SQL databases: Ingres, Sybase, Informix?
-
- Bill Thompson
-