Is it feasible to use datatable copyBulk for DBMS data loading?

Asked

Viewed 47 times

1

I went through an experience in doing a large load of data from a text file, which needed to be criticized before writing to BD. I used Datatable with copybulk. I realized that the data load in Datatable and later in BD was fast. I received criticism regarding the use of Datatable. The advantage of Datatable is the possibility of creating indexes and creating it identical to the BD table.

  • What reviews have you received? You are questioning the feasibility of using copyBulk in what sense?

  • ´I don’t question the use of copyBulk. It’s very efficient and fast. The criticism I received is that datatable is an outdated and slow technology. In my case the performance was very good (about 100,000 records). What bothers me is that the existing standards are often seen as a law, and those who do not use it can be considered a "marginal". I love patterns, but I don’t let myself be enslaved by any of them. After all they were developed by professionals like us.

  • Well, I understand very little of C, and therefore I’m not qualified to answer. However, your question seems more like an outburst than a question looking for an answer. I couldn’t understand what kind of information you’d expect to see in an answer. Try to edit it to make it clearer which is specifically your question and what is it you expect to see in the answer.

1 answer

1

Yes, it is feasible, as long as you answer and solve your specific problem.

As with all kinds of software, there is not just a single language or a single technology or a single standard to implement software. Software should be understood as a solution to a particular problem. The language, technology or standard will depend on a number of variables such as: Customer needs, customer infrastructure, hardware and licensing costs, manpower and knowledge available in your region, software lifetime etc.

For a simple data import program that will be used to migrate from one system to another or from one database to another, if used once and then discarded, the design pattern used or the language or libraries will not matter much as it is not something you will be maintaining in the future. So, by solving your problem today, implement it the way it works and fit well. But if this program is used frequently, and there is a need to maintain it, modify it or evolve it, think about it better, because other people will have to tamper with the code, so it’s good that it uses a more up-to-date standard, because it is rare to find in the market professionals who work with older technologies. Seek consensus with your team or your team.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.