Discussion Overview
The discussion revolves around methods for importing flat files, such as Excel, directly into an SQL database. Participants explore various approaches, tools, and programming options for handling this task, with a focus on efficiency and the suitability of different methods based on the volume of data.
Discussion Character
- Exploratory
- Technical explanation
- Debate/contested
Main Points Raised
- One participant inquires about alternatives to Microsoft's import/export Wizard for importing legacy files into an SQL database.
- Another participant suggests using Microsoft's wizard for a small number of files but recommends writing a custom program for larger datasets.
- A participant mentions that BULK INSERT can import files wholesale, noting their experience with CSV files but not confirming other supported formats.
- There is a question regarding whether the database schema needs to match the flat files for the import process to succeed.
- One participant proposes writing a Java application for the import, estimating it could be a short program depending on the complexity of the data differences.
- Another participant suggests that Groovy could also be used for this purpose, highlighting its advantages over Java in terms of flexibility and ease of use.
- Further discussion touches on the merits of Groovy as a scripting language and its potential for prototyping developer tools.
Areas of Agreement / Disagreement
Participants express differing opinions on the best approach to importing files, with some advocating for existing tools like Microsoft's wizard and others favoring custom programming solutions. The discussion remains unresolved regarding the necessity of schema similarity for successful imports.
Contextual Notes
There are assumptions about the volume of files and the complexity of differences between file formats and database schemas that are not fully explored. The discussion also reflects varying levels of familiarity with programming languages and tools.