Reputation: 44607

Upload a Massive CSV File to SQL Server Database

I need to upload a massive (16GB, 65+ million records) CSV file to a single table in a SQL server 2005 database. Does anyone have any pointers on the best way to do this?

Details

I am currently using a C# console application (.NET framework 2.0) to split the import file into files of 50000 records, then process each file. I upload the records into the database from the console application using the SqlBulkCopy class in batches of 5000. To split the files takes approximately 30 minutes, and to upload the entire data set (65+ million records) takes approximately 4.5 hours. The generated file size and the batch upload size are both configuration settings, and I am investigating increasing the value of both to improve performance. To run the application, we use a quad core server with 16GB RAM. This server is also the database server.

Update

Given the answers so far, please note that prior to the import:

The database table is truncated, and all indexes and constraints are dropped.
The database is shrunk, and disk space reclaimed.

After the import has completed:

The indexes are recreated

If you can suggest any different approaches, or ways we can improve the existing import application, I would appreciate it. Thanks.

Related Question

The following question may be of use to others dealing with this problem:

Potential Pitfalls of inserting millions of records into SQL Server 2005 from flat file

Solution

I have investigated the affect of altering batch size, and the size of the split files, and found that batches of 500 records, and split files of 200,000 records work best for my application. Use of the SqlBulkCopyOptions.TableLock also helped. See the answer to this question for further details.

I also looked at using a SSIS DTS package, and a BULK INSERT SQL script. The SSIS package appeared quicker, but did not offer me the ability to record invalid records, etc. The BULK INSERT SQL script whilst slower than the SSIS package, was considerably faster than the C# application. It did allow me to record errors, etc, and for this reason, I am accepting the BULK INSERT answer from ConcernedOfTunbridgeWells as the solution. I'm aware that this may not be the best answer for everyone facing this issue, but it answers my immediate problem.

Thanks to everyone who replied.

Regards, MagicAndi

Upvotes: 8

Answers (11)

adopilot

Reputation: 4500

My scenario for things like that is: Create SSIS Package on SQL server which using BLUK insert into sql, Create stored procedure inside the DataBase to can run that Package from T-SQL code

After that send file for bluk insert to SQL server using FTP and call SSIS Package usinfg stored procedure

Upvotes: 0

Santiago Cepas

Reputation: 4094

See this and this blog posts for a comparison. It seems the best alternative is to use BulkInsert with the TABLOCK option set to true.

Upvotes: 1

to StackOverflow

Reputation: 124696

You may be able to save the step of splitting the files as follows:

Instantiate an IDataReader to read the values from the input CSV file. There are several ways to do this: the easiest is probably to use the Microsoft OleDb Jet driver. Google for this if you need more info - e.g. there's some info in this StackOverflow question.

An alternative method is to use a technique like that used by www.csvreader.com.
Instantiate a SqlBulkCopy object, set the BatchSize and BulkCopyTimeout properties to appropriate values.
Pass the IDataReader to SqlBulkCopy.WriteToServer method.

I've used this technique successfully with large files, but not as large as yours.

Upvotes: 2

Joel Coehoorn

Reputation: 415665

The SqlBulkCopy class that you're already using is going to be your best bet. The best you can do from here in your c# code is experiment with your particular system and data to see what batch sizes work best. But you're already doing that.

Going beyond the client code, there might be some things you can do with the server to make the import run more efficiently:

Try setting the table and database size before starting the import to something large enough to hold the entire set. You don't want to rely on auto-grow in the middle of this.
Depending on how the data is sorted and any indexes one the table, you might do a little a better to drop any indexes that don't match the order in which the records are imported, and then recreate them after the import.
Finally, it's tempting to try running this in parallel, with a few threads doing bulk inserts at one time. However, the biggest bottleneck is almost certainly disk performance. Anything you can do to the physical server to improve that (new disks, san, etc) will help much more.

Upvotes: 2

ConcernedOfTunbridgeWells

Reputation: 66612

BULK INSERT is run from the DBMS itself, reading files described by a bcp control file from a directory on the server (or mounted on it). Write an application that splits the file into smaller chunks, places them in an appropriate directory executes a wrapper that executes a series of BULK INSERTS. You can run several threads in parallel if necessary.

This is probably about as fast as a bulk load gets. Also, if there's a suitable partitioning key available in the bulk load file, put the staging table on a partition scheme.

Also, if you're bulk loading into a table with a clustered index, make sure the data is sorted in the same order as the index. Merge sort is your friend for large data sets.

Upvotes: 5

cjk

Reputation: 46415

Just to check, your inserting will be faster if there are no indexes on the table you are inserting into.

Upvotes: 0

Rad

Reputation: 8381

Have you tried SQL Server Integration Services for this? It might be better able to handle such a large text file

Upvotes: 0

Daniel Brückner

Reputation: 59645

BULK INSERT is probably already the fastest way. You can gain additional performance by dropping indexes and constraints while inserting and reestablishing them later. The highest performance impact comes from clustered indexes.

Upvotes: 0