If you're just importing from a dump file from the CLI on *nix, e.g.
mysql -uxxx -pxxx dbname < /sqlfile.sql
then first install pipe viewer on your OS then try something like this:
pv sqlfile.sql | mysql -uxxx -pxxxx dbname
which will show a progress bar as the program runs.
It's very useful and you can also use it to get an estimate for mysqldump ...
.bacpac file = Schema + Data. Note that Data is BCP'ed out using Native format (not readable by Human).
You can rename the .bacpac to .zip to see the actual contents.
You can use ...DAC\bin\sqlpackage.exe commandline to extract the .bacpac contents programatically.
It is a snapshot that includes User data + Schema from SQL Server or Azure SQL Database.
If you've already started the import, you can execute this command in another window to see the current size of your databases. This can be helpful if you know the total size of the .sql file you're importing.
SELECT table_schema "Data Base Name", sum( data_length + index_length ) / 1024 / 1024 "Data Base Size in MiB"
FROM information_schema.TABLES GROUP ...
Given that there are probably just as many unfounded fears as there are unknown risks, I would think that it is difficult to really say why a policy is in place without asking whomever created the policy why they are concerned.
However, I would guess that it probably has something to do with what BULK INSERT / SqlBulkCopy / BCP / OPENROWSET(BULK ...) allow ...
I am unsure if its necessary to add the TABLOCK table hint to an empty temporary table, defined with a clustered index in order to get minimal logging.
No. Local temporary tables (#temp) are private to the creating session, so a table lock hint is not required. A table lock hint would be required for a global temporary table (##temp) or a regular table (dbo....
It's not actually possible to specify a different tablespace when importing using the oracle imp utility. However, as a workaround, you can pre-create the tables by doing a ROWS=N import into the USERS tablespace, then alter table mytable move tablespace BLOG_DATA; for each table to move them to the new tablespace, then do the import again with the IGNORE=Y ...
First, you need to know what you are doing to InnoDB when you plow millions of rows into an InnoDB table. Let's take a look at the InnoDB Architecture.
In the upper left corner, there is an illustration of the InnoDB Buffer Pool. Notice there is a section of it dedicated to the insert buffer. What does that do ? It is ised to migrate changes to secondary ...
Don't just use the whole table. Instead choose the option to write a query.
Then simply write a select statement that doesn't use that Identity Column.
Alternatively, when you map columns, if you click "Delete rows in destination table", it will truncate the target table before loading data. If the opportunity exists for data to be removed from the source ...
The mysqldump, by default, will drop the table. You should specified the --no-create-info option like this:
mysqldump -u... -p... --no-create-info --skip-extended-insert mydb t1 > mydb_table.sql
That way, you only have inserts to deal with. Using --skip-extended-insert will insert one row at a time. This help deal with duplicate issues, but you will ...
In the end I coded a Python function import_csv_to_dynamodb(table_name, csv_file_name, colunm_names, column_types) that imports a CSV into a DynamoDB table. Column names and column must be specified. It uses boto, and takes a lot of inspiration from this gist. Below is the function as well as a demo (main()) and the CSV file used. Tested on Windows 7 x64 ...
Every 2 seconds you will see the processes running.
watch 'echo "show processlist;" | mysql -uuser -ppassword';
If you want it less frequent then add -n x where x is the number of seconds. 5 seconds would be:
watch -n 5 'echo "show processlist;" | mysql -uuser -ppassword';
You can use csvsql, which is part of csvkit (a suite of utilities for converting to and working with CSV files):
Linux or Mac OS X
free and open source
sudo pip install csvkit
Example: csvsql --dialect mysql --snifflimit 100000 datatwithheaders.csv > mytabledef.sql
It creates a CREATE TABLE statement based on the file content. Column names are taken ...
Achieving optimal import performance in this scenario requires three things:
Minimally-logged base table inserts
Minimally-logged nonclustered index builds
Avoiding physical reads
Achieving minimally-logged inserts to an empty clustered table without nonclustered indexes requires:
Using either the SIMPLE or BULK_LOGGED database recovery ...
You are probably seeing an error like:
Msg 7357, Level 16, State 1, Line xx
Cannot process the object "<query text>".
The OLE DB provider "<provider>" for linked server "<server>" indicates that either
the object has no columns or the current user does not have permissions on that object.
This occurs when SQL Server tries to discover the ...
SQL Server has always supported bulk inserting from CSV files, you just have to specify field/row terminators.
Then we do this:
CREATE TABLE #foo(a varchar(32), b varchar(32), c int);
BULK INSERT #foo FROM 'c:\temp\file.csv'
WITH (ROWTERMINATOR = '\n', FIELDTERMINATOR = ',');
SELECT * FROM #foo;
If you want access to all data (ie, all tables in all schemas), you would need to grant dataaccess.
db2 grant dataaccess on database to user winuser1
If you only want winuser1 to access just the 100 tables in the schema you are referring to, then unfortunately, there is no easy way, you would need to grant SELECT on each table. That being said, it can be ...
I wanted to write a comment (as this is not a definitive answer), but it became too long:
I am going to give you several broad pieces of advice, and we can go into details for each one, if you want:
Reduce durability (you have already done some of it). Latest versions allow even doing it more. You can go as far as disabling the double write buffer,as ...
Unfortunately that's not possible if you insist on using the wizard, you would need to edit the package using Visual Studio.
There is an option 'keep null's' when editing the package in Visual Studio
Given this .csv file:
and this table definition
CREATE TABLE [dbo].[NullTest](
No need to run unique_checks = 0 and foreign_key_checks = 0. See my 3-year-old post Speeding up mysqldump / reload (ASPECT #2 shows a standard header of a mysqldump. Lines 13 and 14 handle the disabling of those checks for you)
Please note the InnoDB Architecture (Picture From Percona CTO Vadim Tkachenko)
If you want to reload ...
With an average of 2.4 characters (more relevant: avg bytes - but that's the same for all ASCII characters) I would not bother to use enums. Those occupy 4 bytes on disk plus, possibly, alignment padding. (text does not require alignment padding.) You are not even saving storage and get more overhead for it.
With most values below 7 characters (= 8 bytes on ...
Another way to import dump files when source <filename> doesn't work is to do the following:
~> mysqldump --user=<user> --password=<password> <db_name> > <export_file_name>.sql
> mysql -u <user> -p <pass> <db_name>
mysql> USE <db_name>; (if you didn't already select)
Create an empty database or if you have one already target that one.
Open CMD with elevated privilege and run:
sqlcmd -S SERVERNAME -d MYDATABASE -U USERNAME -P PASSWORD -i C:\path\mysqlfile.sql -o C:\path\results.txt
-S: is your servername or localhost
-d: is the database you are targeting
-U: is the username
-P: is the password
-i: is the ...
You just need to add OPTIONALLY ENCLOSED BY '"':
LOAD DATA INFILE 'filename.csv' INTO TABLE table_name
FIELDS TERMINATED BY ','
OPTIONALLY ENCLOSED BY '"'
IGNORE 1 LINES;
Table and test:
mysql> create table tbl_name (