If you’ve ever tried to use PowerShell’s Import-CSV with large files, you know that it can exhaust all of your RAM. Previously, I created a script on ScriptCenter that used an alternative technique to import large CSV files, and even imported them into SQL Server at a rate of 1.7 million rows a minute. I’ve now gotten that number up to a massive 3.2 million rows a minute 5.35 million rows a minute for non-indexed tables and 2.6 million rows a minute 4.35 million rows a minute for tables with clustered indexes.
Importing into SQL Server
Two of the fastest ways to import data is to use bcp or SqlBulkCopy. BCP is finicky, and requires a separate download. My intention is to create a script that can be used on any machine running PowerShell v3 and above, so these scripts will be using SqlBulkCopy. The catch is that SqlBulkCopy.WriteToServer() requires a Datatable, Datarow, or IDataReader as input. This means your plain-text CSV data must be transformed into one of these objects prior to being passed to WriteToServer().
I’ve tested three different methods for transforming CSV data to a consumable object. The first method uses SqlBulkCopy, StreamReader and DataSet batches. The second streams an OleDbconnection query result set to SqlBulkCopy. The third uses SqlBulkCopy, VisualBasic.FileIO.TextFieldParser and DataSet batches. I actually tested logparser, too, but while logparser is amazing (and way way faster) for parsing files, it doesn’t take advantage of sqlbulkcopy, so these approaches actually outperform logparser (and my tests with SSIS for that matter).
Setup
My lab is a VMWare virtualized lab which now consists of a Windows 10 machine with 6GB RAM, and a SQL Server 2014 instance with 12GB RAM (8 dedicated to SQL Server). Both are on on the same ESX host which sports a directly connected Samsung 850 EVO 500GB SSD drive. The database’s recovery model is set to SIMPLE.
The 1.2 GB CSV in this example contains 10 million+ rows of tab-delimited longitude and latitude data. A zip containing the CSV is available for download at geonames.org.
First, I had to create the SQL table.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
CREATE TABLE allCountries ( GeoNameId int PRIMARY KEY, Name nvarchar(200), AsciiName nvarchar(200), AlternateNames nvarchar(max), Latitude float, Longitude float, FeatureClass char(1), FeatureCode varchar(10), CountryCode char(2), Cc2 varchar(255), Admin1Code varchar(20), Admin2Code varchar(80), Admin3Code varchar(20), Admin4Code varchar(20), Population bigint, Elevation varchar(255), Dem int, Timezone varchar(40), ModificationDate smalldatetime, ) |
Then I tested the various methods. You’ll probably notice that these scripts don’t have much error handling. I wanted to keep the code easy to read and straightforward. Finalized scripts with error handling and all that will be placed on ScriptCenter shortly.
StreamReader to DataTable batches
This one is by far the fastest, at up to 5.35 million rows per minute on a non-indexed table.
Realistically, you’ll probably be importing to an indexed table, which performs up to 4.35 million rows per minute on optimized systems.
Basically, the script performs the following
- Creates the SQL Bulk Copy connection
- Creates the PowerShell datatable, along with its columns
- Reads the CSV file using System.IO.StreamReader
- Using readline(), loads the CSV data row by row into the datatable
- Performs the bulk import every x number of rows
- Empties the datatable
- Rinse repeat starting at step 4 until the end of the CSV file
In order to avoid having to specify column names each time you import a new CSV, the SQL table column order and CSV column order must be the same. If you need to rearrange your columns, I suggest creating a view and importing to the view.
If you’re wondering why batching was used, it’s because the datatable seems to get exponentially slower as it grows above a few hundred thousand rows. I actually wasn’t able to import all 9 million rows into the datatable before my memory was exhausted. I tested various batch sizes, and 50k worked best for me.
The downside to using this script is that it doesn’t handle embedded delimiters well. So if you have a comma delimiter, and your data contains “This Works”,”This, doesn’t”, then it will fail on “This, doesn’t.” You can address this with a regex (as seen below, after the code).
The Script
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 |
# Database variables $sqlserver = "sqlserver" $database = "locations" $table = "allcountries" # CSV variables $csvfile = "C:\temp\allcountries.txt" $csvdelimiter = "`t" $firstRowColumnNames = $false ################### No need to modify anything below ################### Write-Host "Script started..." $elapsed = [System.Diagnostics.Stopwatch]::StartNew() [void][Reflection.Assembly]::LoadWithPartialName("System.Data") [void][Reflection.Assembly]::LoadWithPartialName("System.Data.SqlClient") # 50k worked fastest and kept memory usage to a minimum $batchsize = 50000 # Build the sqlbulkcopy connection, and set the timeout to infinite $connectionstring = "Data Source=$sqlserver;Integrated Security=true;Initial Catalog=$database;" $bulkcopy = New-Object Data.SqlClient.SqlBulkCopy($connectionstring, [System.Data.SqlClient.SqlBulkCopyOptions]::TableLock) $bulkcopy.DestinationTableName = $table $bulkcopy.bulkcopyTimeout = 0 $bulkcopy.batchsize = $batchsize # Create the datatable, and autogenerate the columns. $datatable = New-Object System.Data.DataTable # Open the text file from disk $reader = New-Object System.IO.StreamReader($csvfile) $columns = (Get-Content $csvfile -First 1).Split($csvdelimiter) if ($firstRowColumnNames -eq $true) { $null = $reader.readLine() } foreach ($column in $columns) { $null = $datatable.Columns.Add() } # Read in the data, line by line while (($line = $reader.ReadLine()) -ne $null) { $null = $datatable.Rows.Add($line.Split($csvdelimiter)) $i++; if (($i % $batchsize) -eq 0) { $bulkcopy.WriteToServer($datatable) Write-Host "$i rows have been inserted in $($elapsed.Elapsed.ToString())." $datatable.Clear() } } # Add in all the remaining rows since the last clear if($datatable.Rows.Count -gt 0) { $bulkcopy.WriteToServer($datatable) $datatable.Clear() } # Clean Up $reader.Close(); $reader.Dispose() $bulkcopy.Close(); $bulkcopy.Dispose() $datatable.Dispose() Write-Host "Script complete. $i rows have been inserted into the database." Write-Host "Total Elapsed Time: $($elapsed.Elapsed.ToString())" # Sometimes the Garbage Collector takes too long to clear the huge datatable. [System.GC]::Collect() |
As I mentioned earlier, you can use regex if you have delimiters embedded in quotes. This slows down the script by a fair degree, but here’s some code to get you started.
|
1 2 3 4 5 6 7 8 9 10 11 12 |
# from http://stackoverflow.com/questions/15927291/how-to-split-a-string-by-comma-ignoring-comma-in-double-quotes $fieldsEnclosedInQuotes = $true ... if ($fieldsEnclosedInQuotes) { $csvSplit = "($csvdelimiter)" $csvsplit += '(?=(?:[^"]|"[^"]*")*$)' } else { $csvsplit = $csvdelimiter } $regexOptions = [System.Text.RegularExpressions.RegexOptions]::ExplicitCapture ... $columns = [regex]::Split($firstline, $csvSplit, $regexOptions) ... $null = $datatable.Rows.Add($([regex]::Split($line, $csvSplit, $regexOptions))) |
Streaming a 32-bit OleDbconnection
What I like about this method is that it’s still high performance (~2million rows/minute) and you can select subsets of data from CSV if you wish. Just change the CommandText to have a where clause, for example: $cmd.CommandText = “SELECT count(*) FROM [$tablename] WHERE Category=’Cajun'”. If your CSV doesn’t have column names, you can use the built-in column names F1, F2, F3, etc.
Here are the results from a million row subset:
The downside to this script is that you have to use an x86 shell, but because it doesn’t use any RAM, the performance actually isn’t impacted. Switching to another shell may just get a little complex if you embed this script in a function. I’ve mitigated this to the best of my ability by telling it to call the 32-bit shell with the current scriptname and arguments.
The Script
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 |
# The Text OleDB driver is only available in PowerShell x86. Start x86 shell if using x64. # This has to be the first check this script performs. if ($env:Processor_Architecture -ne "x86") { Write-Warning "Switching to x86 shell" $ps32exe = "$env:windir\syswow64\windowspowershell\v1.0\powershell.exe" &$ps32exe "$PSCommandPath $args"; return } # Database variables $sqlserver = "sqlserver" $database = "locations" $table = "allcountries" # CSV variables $csvfile = "C:\temp\million.csv" $csvdelimiter = "," $firstRowColumnNames = $true ################### No need to modify anything below ################### Write-Host "Script started..." $elapsed = [System.Diagnostics.Stopwatch]::StartNew() [void][Reflection.Assembly]::LoadWithPartialName("System.Data") [void][Reflection.Assembly]::LoadWithPartialName("System.Data.SqlClient") # Setup bulk copy $connectionstring = "Data Source=$sqlserver;Integrated Security=true;Initial Catalog=$database" $bulkcopy = New-Object Data.SqlClient.SqlBulkCopy($connectionstring, [System.Data.SqlClient.SqlBulkCopyOptions]::TableLock) $bulkcopy.DestinationTableName = $table $bulkcopy.bulkcopyTimeout = 0 # Setup OleDB using Microsoft Text Driver. $datasource = Split-Path $csvfile $tablename = (Split-Path $csvfile -leaf).Replace(".","#") switch ($firstRowColumnNames) { $true { $firstRowColumnNames = "Yes" } $false { $firstRowColumnNames = "No" } } $connstring = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=$datasource;Extended Properties='text;HDR=$firstRowColumnNames;FMT=Delimited($csvdelimiter)';" $conn = New-Object System.Data.OleDb.OleDbconnection $conn.ConnectionString = $connstring $conn.Open() $cmd = New-Object System.Data.OleDB.OleDBCommand $cmd.Connection = $conn # Perform select on CSV file, then add results to a datatable using ExecuteReader $cmd.CommandText = "SELECT * FROM [$tablename]" $bulkCopy.WriteToServer($cmd.ExecuteReader([System.Data.CommandBehavior]::CloseConnection)) # Get Totals $totaltime = [math]::Round($elapsed.Elapsed.TotalSeconds,2) $conn.Close(); $conn.Open() $cmd.CommandText = "SELECT count(*) FROM [$tablename]" $totalrows = $cmd.ExecuteScalar() Write-Host "Total Elapsed Time: $totaltime seconds. $totalrows rows added." -ForegroundColor Green # Clean Up $cmd.Dispose(); $conn.Dispose(); $bulkcopy.Dispose() |
VisualBasic.FileIO.TextFieldParser to DataTable batches
This technique is the slowest, but if you’ve got embedded delimiters and need to stay in x64, you may want to consider it.
The Script
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 |
# Database variables $sqlserver = "sqlserver" $database = "locations" $table = "allcountries" # CSV variables $parserfile = "C:\temp\million.csv" $parserdelimiter = "," $firstRowColumnNames = $false $fieldsEnclosedInQuotes = $true ################### No need to modify anything below ################### Write-Host "Script started..." $elapsed = [System.Diagnostics.Stopwatch]::StartNew() [void][Reflection.Assembly]::LoadWithPartialName("System.Data") [void][Reflection.Assembly]::LoadWithPartialName("System.Data.SqlClient") [void][Reflection.Assembly]::LoadWithPartialName("Microsoft.VisualBasic") # 50k worked fastest and kept memory usage to a minimum $batchsize = 50000 # Build the sqlbulkcopy connection, and set the timeout to infinite $connectionstring = "Data Source=$sqlserver;Integrated Security=true;Initial Catalog=$database;" $bulkcopy = New-Object Data.SqlClient.SqlBulkCopy($connectionstring, [System.Data.SqlClient.SqlBulkCopyOptions]::TableLock) $bulkcopy.DestinationTableName = $table $bulkcopy.bulkcopyTimeout = 0 $bulkcopy.batchsize = $batchsize # Open text parser for the column names $columnparser = New-Object Microsoft.VisualBasic.FileIO.TextFieldParser($parserfile) $columnparser.TextFieldType = "Delimited" $columnparser.HasFieldsEnclosedInQuotes = $fieldsEnclosedInQuotes $columnparser.SetDelimiters($parserdelimiter) Write-Warning "Creating datatable" $datatable = New-Object System.Data.DataTable foreach ($column in $columnparser.ReadFields()) {[void]$datatable.Columns.Add()} $columnparser.Close(); $columnparser.Dispose() # Open text parser again from start (there's no reset) $parser = New-Object Microsoft.VisualBasic.FileIO.TextFieldParser($parserfile) $parser.TextFieldType = "Delimited" $parser.HasFieldsEnclosedInQuotes = $fieldsEnclosedInQuotes $parser.SetDelimiters($parserdelimiter) if ($firstRowColumnNames -eq $true) {$null = $parser.ReadFields()} Write-Warning "Parsing CSV" while (!$parser.EndOfData) { try { $null = $datatable.Rows.Add($parser.ReadFields()) } catch { Write-Warning "Row $i could not be parsed. Skipped." } $i++; if (($i % $batchsize) -eq 0) { $bulkcopy.WriteToServer($datatable) Write-Host "$i rows have been inserted in $($elapsed.Elapsed.ToString())." $datatable.Clear() } } # Add in all the remaining rows since the last clear if($datatable.Rows.Count -gt 0) { $bulkcopy.WriteToServer($datatable) $datatable.Clear() } Write-Host "Script complete. $i rows have been inserted into the database." Write-Host "Total Elapsed Time: $($elapsed.Elapsed.ToString())" # Clean Up #$parser.Dispose(); $bulkcopy.Dispose(); $datatable.Dispose(); $totaltime = [math]::Round($elapsed.Elapsed.TotalSeconds,2) Write-Host "Total Elapsed Time: $totaltime seconds. $i rows added." -ForegroundColor Green # Sometimes the Garbage Collector takes too long to clear the huge datatable. [System.GC]::Collect() |
VB.NET Equivalent
Using a VB.NET compiled exe imports about 4 million rows a minute.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 |
Sub Main() Dim oTimer As New System.Diagnostics.Stopwatch oTimer.Start() Dim iRows As Int64 = 0 Using oBulk As New Data.SqlClient.SqlBulkCopy("server=.;database=DATABASE;trusted_connection=yes", SqlClient.SqlBulkCopyOptions.TableLock) With {.DestinationTableName = "AllCountries", .BulkCopyTimeout = 0, .BatchSize = 100000} Using oSR As New IO.StreamReader("C:\allcountries.txt") Using oDT As New DataTable With oDT.Columns .Add("GeoNameID", GetType(System.Int32)) .Add("Name", GetType(System.String)) .Add("AsciiName", GetType(System.String)) .Add("AlternateNames", GetType(System.String)) .Add("Latitude", GetType(System.Decimal)) .Add("Longitude", GetType(System.Decimal)) .Add("FeatureClass", GetType(System.String)) .Add("FeatureCode", GetType(System.String)) .Add("CountryCode", GetType(System.String)) .Add("Cc2", GetType(System.String)) .Add("Admin1Code", GetType(System.String)) .Add("Admin2Code", GetType(System.String)) .Add("Admin3Code", GetType(System.String)) .Add("Admin4Code", GetType(System.String)) .Add("Population", GetType(System.Int64)) .Add("Elevation", GetType(System.String)) .Add("Dem", GetType(System.Int32)) .Add("Timezone", GetType(System.String)) .Add("ModificationDate", GetType(System.DateTime)) End With Dim iBatchsize As Integer = 0 Do While Not oSR.EndOfStream Dim sLine As String() = oSR.ReadLine.Split(vbTab) oDT.Rows.Add(sLine) iBatchsize += 1 If iBatchsize = 100000 Then oBulk.WriteToServer(oDT) oDT.Rows.Clear() iBatchsize = 0 Console.WriteLine("Flushing 100,000 rows") End If iRows += 1 Loop oBulk.WriteToServer(oDT) oDT.Rows.Clear() End Using End Using End Using oTimer.Stop() Console.WriteLine(iRows.ToString & "Records imported in " & oTimer.Elapsed.TotalSeconds & " seconds.") Console.ReadLine() End Sub |
Conclusion
There are a number of tools that can be used to import CSV files into SQL Server. If you’re looking to use PowerShell, the StreamReader will give you the fastest results, but if your code has embedded delimiters, this may not be the method for you. Using OleDBConnection is a powerful, fast way to import entire CSVs or subsets of CSV data, but requires the use of an x86 shell, unless you download the Microsoft Access Database Engine 2010 Redistributable which provides a 64-bit text driver. Microsoft.VisualBasic.FileIO.TextFieldParser is slower, but works in 64-bit and processes embedded delimiters well.
Chrissy is a Cloud and Datacenter Management MVP who has worked in IT for over 20 years. She is the creator of the popular SQL PowerShell module dbatools, and holds a number of certifications, including those relating to SQL Server, Linux, SharePoint and network security. You can follow her on Twitter at @cl.
Hi Chrissy.
Trying to have your StreadReader to DataTable batches example working.
I’ve got conversion error between string to int (and decimal) when calling WriteToServer.
Since every columns in the DataTable is of type String, what is wrong ?
In the example in VB.NET, columns types are provided, so everything works fine.
What am I missing ?
Hey Eric,
That is strange. I’ve had luck with int and decimal. Are implicit conversions allowed on your database?
Try removing this part:
foreach ($column in $columns) {
$null = $datatable.Columns.Add()
}
And then explicitly specify your column names. For example:
[void]$datatable.Columns.Add(“ID”,[int64])
[void]$datatable.Columns.Add(“filename”,[string])
[void]$datatable.Columns.Add(“totalmb”,[int64])
Thanks for your help.
What do you mean by “Are implicit conversions allowed on your database?”
How can I do that in SQL Server ?
I already use the solution you provided. But I still have another problem.
Parsing my CSV, with empty values (empty strings) that are NULL values for Integer (for example), I received an error message that I cannot load an empty string to an Int32 (or something like that).
So I have to convert my empty values to System.DBNULL.Value for those cases. So it slow the overall process.
Hello Chrissy,
I found your post and I set your script and it works great. One question is when I run this script lets nightly new entry in the SQL database. Is these why I can just have it append the DB entries or overwrite them?
thanks
Paul
Hey Chrissy,
Thanks a lot for the awesome script.
The script works perfectly if the table does not have an IDENTITY Column.
I have a column [UniqueID] [bigint] IDENTITY(1,1) NOT NULL,
Is there any way to insert data into a SQL Table with IDENTITY COlumn using the bulkCopy method?
Thanks,
Praveen
I’ve figured it out..!!
The script actually works for identity columns as well..
The catch is that we need to have the columns in the same order in csv and sql table and in the powershell datatable.
I have populated the identity column in csv with dummy values and executed the script.
it worked!! The Sql table ignored dummy values of datatable and inserted the values in Identity Column from where they ended earlier.
hi
how can i ignore or import the row that have extra separator(comma)?
thanks for your attention
Mah,
If you are using VB.Net you can use Lumenwork’s free opensource CSV reader instead of streamreader (with the split command). I had to parse the fields back into a string() using the following function:
Public Shared Function GetStringArray(iNumFields As Integer, crCsvReader As CsvReader) As String()
Dim saValues(iNumFields – 1) As String
For i As Integer = 0 To iNumFields – 1
saValues(i) = crCsvReader(i)
Next
Return saValues
End Function
I then fed this to the datatable.
Hi Chrissy,
Thanks for the excellent script. But just curious to know, if there is an equivalent PS script to copy data of a table in 2 different SQL instances. At present, we tried the SSIS Data flow task and the speed is not on par. Please let me know if there is any modified version of this script to use this as an alternative for SQL import and export. Thanks alot!!
Thanks
Sethu
Actually, yes, I’ve done this a bunch of times before and I plan on making it part of the dbatools module.
You’d basically do a $bulkcopy.WriteToServer($sqlcmd.ExecuteReader())
Chrissy,
Very nice.
I’m sure that you already know that the speed depends on the number of columns as well as the number of rows. These performance numbers are both interesting and amazing.
I can’t wait to try this with a very large CSV file. I specifically need to create a very generic CSV importer to SQL that creates an SQL table with it’s field names then pulls the data into it. Your code makes the import process very quick. I think using it with the lumenworks CSV reader which will validate the data will allow for this utility to work very well.
Thanks again,
Peter
Peter, great point! Maybe i’ll include LumenWorks in my official module. I hate it right now because it doesn’t handle stuff well. This was mostly for proof of concept, but yeah, SUPER FAST = No error handling, which is fun, but not long term useful.
I came up with a way to do it even faster (25 million rows in less than 2 minutes using multithreading) but the garbage collection doesn’t collect fast enough so it suffers from memory issues.
As someone described above, if there is an identity column, the script might fail. To fix it:
$bulkcopy = New-Object Data.SqlClient.SqlBulkCopy($connectionstring, [System.Data.SqlClient.SqlBulkCopyOptions]::KeepIdentity)
Hi there,
$null = $datatable.Rows.Add($([regex]::Split($line, $csvSplit, $regexOptions))) inserts double quotes into the table. Is there a way we could avoid it from happening?
Hey JD, I need to revamp this article. I don’t recommend these techniques for most data. It turns out the two datasets I was working with were nice and perfect and anything outside of that is subject to breakage. The second option (OLE) in this case will remove the quotes.
Btw, where did you find the site? There seems to be more comments than usual.
If you guys wanna see what I did with runspaces, I gave a talk at PSCONF.eu. My slides are stacked with code and stuff.
https://github.com/psconfeu/2016/tree/master/Chrissy%20LeMaire/JourneyTo200k
Yep, I’ll take a look at it. BTW, Is there a recorded session for psconfeu? It would be great if it was out there. :)
Waiting! It was recorded but they are doing the edits still. I’ll post here when it’s out :D
Awesome. Thanks! Meanwhile, let me try to figure out runspaces. I’m sure there is a steep learning curve there.
oque seria esse (OLE)?
voce conseguiu tirar as aspas duplas ?
I’m wondering if it would be possible to make a “matching importer”, where it queries a table for its field list, compares to the header row, then creates a smaller $datatable with just the matching fields, and then insert them. That way if there’s an extra field in the second file sometimes, then it would ignore it.
I got rather far into it but I think I’m stuck – I get all the way up to inserting into the datatable. At that point, because it’s a simple insert, there’s no way to tell it “just do these fields”. I was hoping that $datatable.Rows.Add($line.Split($csvdelimiter)) would realize that some fields don’t exist, and wouldn’t add them. Does not appear so.
#adapted from https://blog.netnerds.net/2015/01/powershell-high-performance-techniques-for-importing-csv-to-sql-server/
. C:\powershell_scripts\Join-Object.ps1
. C:\powershell_scripts\invoke-sqlcmd2.ps1
$csvdelimiter = “|”
$csvfile = “c:\temp\myfile.txt”
# 50k worked fastest and kept memory usage to a minimum
$batchsize = 50000
remove-variable header_columns
remove-variable list_of_fields
$list_of_fields = invoke-sqlcmd2 -query “SELECT name FROM sys.columns WHERE OBJECT_ID = OBJECT_ID(‘view_that_i_insert_into’) ORDER BY column_id;” -serverinstance “myserver” -Database mydb
#the whole purpose of the select-string and pattern is to get it back into an object array for the join-object
[regex]$pattern = “[^|]” #using the pipe because I know it won’t be in there.
$header_columns = (Get-Content $csvfile -First 1).Split($csvdelimiter)|select-string -pattern $pattern
#external module by powershell team. Gives us our inner join, and now we just get the fields that match.
$fields_to_import = join-object -left $header_columns -Right $list_of_fields -Where {$args[0].Line -eq $args[1].name} -leftproperties Line -rightproperties name -type OnlyIfInBoth |select Line
remove-variable datatable
$datatable = New-Object System.Data.DataTable
# creates the fields in the datatable to be populated with. It will have no rows, though
# This is the target of the join-object.
foreach ($column in $fields_to_import) {
$null = $datatable.Columns.Add()
}
# Open the text file from disk – doing this here because we did it with get-content earlier. If it’s slow, use that
$reader = New-Object System.IO.StreamReader($csvfile)
if ($firstRowColumnNames -eq $true) { $null = $reader.readLine() }
# Read in the data, line by line
#alas, this doesn’t look like it’ll work; it grabs the entire string and inserts it into the datatable. Which won’t work since the datatable is just “what matches”.
while (($line = $reader.ReadLine()) -ne $null) {
$null = $datatable.Rows.Add($line.Split($csvdelimiter))
$i++; if (($i % $batchsize) -eq 0) {
$bulkcopy.WriteToServer($datatable)
Write-Host “$i rows have been inserted in $($elapsed.Elapsed.ToString()).”
$datatable.Clear()
}
}
So… any way to turn the process around, and write data to text files quickly?
SSIS is OK, but…
Hi Chrissy,
Great Script. I am wondering if the StreamReader “split” method expects a Delimiter to appear after the last column record for a given line.
I was able to successfully run the script for one set of data which had the delimiter after the final column record, but was unable to do the same when the data had no comma after the last record.
Example 1 (Works)
John Smith, [email protected], 12345678,
Jane Smith, [email protected], 987654321
Example 2 (Does Not Work)
John Smith, [email protected], 123456789
Jane Smith, [email protected], 987654321
It is possible I am breaking at another point, but the error I am getting states “Additional information: Input array is longer than the number of columns in this table.”
Anyway, I have been trying to get it to run over a few specific file formats, if you happen to know if the method expects the end delimiter, let me know as I have been wrestling with it for a while.
Thanks again for the great solution.
Figured out the problem, a comma snuck into one of the fields where there isn’t supposed to be one. The only problem is the file is comma delimited, shoot…
Hi
Interesting script but any way to export millions of events. I´m trying to export more tan 7 millions of events and ONLY get time out and high memory consumption.
It must be an option to optimize the export when you are using a variable to store all events.
Regards and thanks
I have a TAB-DELIMITED .txt file and I’m getting the following errors:
Exception calling “WriteToServer” with “1” argument(s): “The given value of type String from the data source cannot be converted to type bigint of the
specified target column.”
At C:\Users\MELINDA.SAVOY\MyDirectory\TEST_CopyToCFLE_table.ps1:60 char:9
+ $bulkcopy.WriteToServer($datatable)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException
100000 rows have been inserted in 00:00:35.3103642.
Exception calling “WriteToServer” with “1” argument(s): “The given value of type String from the data source cannot be converted to type decimal of the
specified target column.”
At C:\Users\MELINDA.SAVOY\MyDirectory\TEST_CopyToCFLE_table.ps1:60 char:9
+ $bulkcopy.WriteToServer($datatable)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException
The same data types are defined in my data source (postgresql) as they are in the table of my sql server table. I’m not sure how to correct. Any help/direction would be appreciated. Thanks.
Thansk for your response, but the point that I am trying to highlight is about exporting data (event logs) to a CSV in a faster way. Because as you Said RAM consumption is a concern. It’s not recommended using a variable, because RAM consumption, instead you can export to a CSV but process is slow. You explanation is focused to import data to SQL and that is not my concern.
It’s brilliant, i was looking for a method to import 623k zipcodes from a csv to a databasetable, and the powershellscript works better than expected. I decreased the batch size to 500, just for fun actually and to see some more lines passing through, it took only 14 seconds. The previous import with a regular .sql file with insert statements took 15 minutes.
So thank you =)
needed help, wanted something that overwritten the data already contained, or erased all the data in the table before entering new data.
Hi ! I tried using the first script , all looks good but nothing really happens , what could i have done wrong , i got some errors with
Exception calling “Add” with “1” argument(s): “Input array is longer than the number of columns in this table. IS this operation Atomic ? so if something breaks all will break ?
also , whats the meaning of : $csvdelimiter = “`t” ? is not in your csv file “,” the delimiter ?