Wrong column delimiter

Column delimiters in plain text files can cause annoying problems. Solving such a problem will take you a lot of time. And this is time that you rather spend on doing some real work, or basically anything else that you like to spend your time on.

In this blog post, I will explain which root causes there are for the column delimiter issue. At the last part of this article, I will also offer you the solution. This solution involves using the SQL DataTool.

In a different article, I went through giving the solution of unexpected line breaks in flat files. This might also interest you when you run into the issue of a wrong column delimiter.

SQL database import errors: line breaks

When importing huge plain text files or comma separated files, different errors may occur while using the SQL Server import wizard. One of such errors is line breaks in the source files.

SQL Server import and export wizard expects a line break before a new record begins. However, when importing plain text that contains (larger) text columns, you might walk into a record that contains an unexpected line break in the text column. The larger the number of records to be imported, the bigger the chance that a record causes an error.

Import date with SQL Server Management Studio

SQL Server Management Studio (SSMS) has the option to import data to a database. This functionality is part of the SQL Server Import and Export Wizard. Using this wizard, importing and exporting data becomes very easy. However, the SQL Server Import and Export Wizard needs clean and perfect import files. Importing dates into SQL Server databases might cause some headaches, therefore I will also offer a solution using the SQL DataTool to import dates into SQL databases.

In this blogpost, I will first show how to use the wizard, and which errors you might see while importing date fields. After that, the SQL DataTool is described and how it will help you importing files that cause errors when importing date fields using the SQL Import wizard.