• Aaron N. Cutshall - Wednesday, February 27, 2019 7:58 PM

    The issue I have is when those techniques are implemented in a production environment in lieu of a relational database when the data being loaded is relational (most come from another RDBMS) and the tools are implemented to operate as though it were an RDBMS.

    I understand that, but you have mentioned this numerous times in similar threads. The techniques has nothing to do with how good or bad the technology is nor does it mean it's the wrong tool for the job. Anyone can misuse a hammer when trying to hammer in a nail to a board. It does not mean the hammer is not a good tool or the right tool for the job.

    The same also applies for other tools. I have seen plenty of people misuse their RDBMS. Does not mean it's a bad tool or the wrong tool.

    I know you followed up saying similar to Steve, but just have to point that out because it seems to be a constant theme here on how people use these tools. Yes, people use them differently. Some good, some bad. The RDBMS is not the end all be all solution nor is it the only tool in the toolbox. And with that, I would go on to say that the RDBMS is still here to stay and has a critical part to these other tools for the sheer fact it does what it was designed to do so well IF the operators behind the tool know what they are doing.