Tag Info

New answers tagged

0

I would be a little concerned. When you run COMMIT; you should get this mysql> commit; Query OK, 0 rows affected (0.00 sec) mysql> If the prompt has not returned yet, run this SHOW PROCESSLIST; just to see if any queries are processing. Notwithstanding, MySQL could be still processing things. How ? Look at the InnoDB Architecture (Picture made ...


1

You should have him send you a public gpg key that he has the private key for, which you use to encrypt the dump. You can then deliver it to him using any method that is comfortable for you, and then he can decrypt it once he has received it. If you're on Windows.. http://www.gpg4win.org/ is a great tool for that.


2

Of course you can put it up on Dropbox - or anywhere else. Depends on how secure you want your data to be? Do you want the NSA looking at it? Dropbox employees? I would put up an encrypted version of your mysqldump and securely transmit the key to your colleague - either face to face or over encrypted email, or have the password/key sent by courrier. ...


2

You can import your .csv file and replace after: Make your date column new_date_column VARCHAR(10). Import the file. UPDATE with REPLACE. UPDATE db1.table1 SET new_date_column = STR_TO_DATE(REPLACE(new_date_column,'/','.'),GET_FORMAT(DATE,'EUR')); Change the datatype of new_date_column. ALTER TABLE db1.table1 MODIFY new_date_column ...


0

Well, I couldn't figure out how to do it in Mysql Workbench, but I have a workaround. Use: mysqldump -u mysqlUser -p DatabaseName TableName > table_data To get data out of the table you want to use, then use: mysql -u mysqlUser -p DatabaseName TableName < table_data To get the data into the desired table. This will retain the correct values.


0

Another way to import dump files when source <filename> doesn't work is to do the following: Dump ~> mysqldump --user=<user> --password=<password> <db_name> > <export_file_name>.sql Import > mysql -u <user> -p <pass> <db_name> mysql> USE <db_name>; (if you didn't already select) mysql> ...


1

When code starts with something like this /*!50100 the code following till */ is executed only, when MySQL is installed in a version above 5.0.100 The error here is, that you're mixing table options with partition options. From the manual: CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name (create_definition,...) [table_options] ...


0

At least 14 GB. Maybe more if the dump file is compressed. Maybe less if the tables are compressed. A bit more or lot more if there are indexes. Even Data Pump will miscalculate the required space in case of compressed tables. Index data is not stored in the dump file, only index definitions. You can have a 14 GB dump file with 14 GB table data and 0 ...


0

Using a combination of MASTER_ONLY and KEEP_MASTER switches, it's possible to get Data Pump import to do the dependency tracking, calculations, and estimations of sizes that it does at the beginning, create the master table that it uses to track everything, and then stop. You can then examine the master table to see how big the various tables are estimated ...


1

You can edit the dump file and change the included NLS_LENGTH_SEMANTICS from BYTE to CHAR. Near the beginning of the file you find a line ending like this : ^@02:00:^@^@^D^@BYTE^F^@UNUSED^A^@2^K^INTERPRETED^K^@DISABLE:ALL^@^@ Change BYTE to CHAR using your favorite text editor and save the file. When you will imp that new dump file, all columns will be ...



Top 50 recent answers are included