Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Which tools and programming libraries are you aware of that can help accelerate CSV manual correction process when column separator characters are encountered within data elements?

I'm currently not able to correct the generation of source CSV files, such as adding quote delimiters. Manual verification is always required to certify that corrections are properly made.

In my case I currently need to run a portable solution on Win32 (i.e. doesn't require administration permissions) and open source would be preferable. Any language is a possibility. Destination is to a SQL Server 2008 instance with very limited permissions (BULK INSERT, OPEN ROWSET and such are not allowed). DTS/SSIS are also not available, neither is Visual Studio. The current method is opening up Excel, filter non-blanks on the last column, correct those filtered out rows, and then export to SQL Server via bcp or MS Access.


share|improve this question

We implemented a pretty simple C# command-line program that acted as a pre-parser before bulk inserting. It worked quite fast and you could create something with the free Visual Studio Express (or even with just the compiler, I imagine).

To be clear, you would only potentially need Visual Studio to CREATE the program (you can do it without Visual Studio, but you shouldn't need to). To run the .exe on the destination machines, the requirements are far lower - you just copy the .exe and it will use the .NET Framework that was already there. If you didn't do anything fancy and targeted a low-enough version of the framework you probably wouldn't need to add anything to the clients. Worst case would be a .NET Framework update (and that would only be if you targeted a newer version of the framework or have very antiquated clients running XP RTM or older).

share|improve this answer
In %WINDIR%\Microsoft.NET\Framework\<version> there are C# compilers (csc.exe). I'll look into it and see if there are any limitations on just using the compiler. In the meantime, VS Express is not portable. – Pedro Palhoto May 22 '12 at 15:05
You don't have to port VS Express - just the C# executable you write. Surely your .exe can run on all your Win32 destinations? – Aaron Bertrand May 22 '12 at 15:07
Aaron, I was referring to portable as in portable app, when the installer application doesn't write to registry. I don't have administration privileges on my workstation. – Pedro Palhoto May 23 '12 at 9:53
What does an .exe have to do with the registry? – Aaron Bertrand May 23 '12 at 11:47
Some application installers write to protected sections in registry. Anyway, I believe the VS Express installer is an .msi (Microsoft Installer) if I recall correctly from what I installed at home. – Pedro Palhoto May 23 '12 at 13:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.