|
|
Posted by David Portas on 07/15/07 12:46
On 15 Jul, 13:34, raylopez99 <raylope...@yahoo.com> wrote:
> Also
> remember right now with RDBMS you expend a tremendous amount of work
> putting data into "orthogonal" databases, via data entry forms. You
> have to pay people to enter the data correctly (even if your program
> rejects bad data entry, you still have to pay people to enter the data
> correctly). You can avoid all of this with a flat file. Just dump
> the raw data into memory and let an inference or search engine index
> the data and make the associations via pointers.
>
So your only alternative is to disregard data integrity? I hope you
won't ever be tempted to try that out in anything other than toy
experiments. Consider finance, medical, military or safety systems for
example. Or systems that preserve confidential personal or legal
information. Or e-commerce. Do you really think integrity features are
unnecessary or unimportant enough to discard? I assume you do not, but
it's far from clear just how "dump the raw data" makes it easier or
cheaper or faster to guarantee data integrity.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|