Sql-server – Upload multiple csv file to multiple tables sqlServer

csvrestoresql servertable

I have over than 200 csv files that each of them is diffrent table.

I create now a new DB and want to upload them all so I will have all the table.

I not accessable to old DB to backup in diffrent way.

I looking for a simple way to do it fast (script/gui/ 3pary tool)

I found I can do it with sqlServer gui but I cant upload there multiple files, only 1 by 1, so it will takes hours.

I saw this post How to upload multiple csv files to sql server without constrains but it not help me, not found there any solution.

Best Answer

I you want to use powershell to upload these CSV files, without having to code/script, take a look dbatools.io. Look for the cmdlet Import-DbaCsv

All the documentation is available on the site. Just download the tools from github or the powershell gallery.

You can use Get-ChildItem cmdlet to get all the CSV files in a folder and use the pipeline to send the files to Import-DbaCsv (optionally specifying the -AutoCreateTable flag). For example:

Get-ChildItem -Path "C:\Path\To\your\CSVs" | ForEach-Object {
    Import-DbaCsv -Csv $_.FullName -SQLInstance "localhost" -Database "yourdb" -AutoCreateTable
}

Related Solutions

Postgresql – Set field values to newly imported rows in PostgreSQL table with existing data

I'd recommend using the COPY command from psql. You can set a DEFAULT value for a column and omit that value from the COPY command, eg:

\copy tablename(col1,col2,col3) FROM 'thefile.csv' WITH (FORMAT CSV)

Alternately, you can create a new TEMPORARY table in PgAdmin-III wtih just the columns in the CSV, import the CSV into it, and use SQL like this to merge it into the main table:

INSERT INTO realtable (col1, col2, col3, colwithdefault)
SELECT
    col1, col2, col, 'some default value'
FROM tempcsvtable;

You can use this to calculate columns based on expressions, combine and split columns, omit some rows, etc.

SQL Server Restore – Create Database Before Restoring Multiple Files

I think the main problem is that you think that creating the database first will allow you to bypass WITH MOVE. This is not the case.

If the destination file paths don't match those contained in the backup file, the presence of a database (and its file locations) aren't going to make a difference. RESTORE is going to look at the file locations specified in the backup file, completely ignoring the existing database. And this can only be overridden by using WITH MOVE.

Best Answer

Related Solutions

Postgresql – Set field values to newly imported rows in PostgreSQL table with existing data

SQL Server Restore – Create Database Before Restoring Multiple Files

Related Question