Export: mysqldump -u root -p –all-databases > alldb.sql Look up the documentation for mysqldump. You may want to use some of the options mentioned in comments: mysqldump -u root -p –opt –all-databases > alldb.sql mysqldump -u root -p –all-databases –skip-lock-tables > alldb.sql Import: mysql -u root -p < alldb.sql
Exclude the tables you do not want to backup pg_dump -U “postgres” -h “local” -p “5432” -d dbName -F c -b -v -f c:\uti\backup.dmp –exclude-table-data ‘*.table_name_pattern_*’ –exclude-table-data ‘some_schema.another_*_pattern_*’ The function creation code is part of the schema.
Yes Yes if the table is using the MyISAM (default) engine. Not if it’s using InnoDB. Probably not, and if there is, you just need to execute mysql_upgrade to fix them To avoid getting databases in a inconsistent state, you can either shutdown MySQL or use LOCK TABLES and then FLUSH TABLES before the backup. … Read more
Looks like its the -W option. There is no value to go with that option. -W, –password force password prompt (should happen automatically) If you want to run the command without typing is a password, use a .pgpass file. http://www.postgresql.org/docs/9.1/static/libpq-pgpass.html
sqlcmd -S servername -Q “BACKUP DATABASE [DBName] TO DISK = ‘C:\backup.bak’ WITH INIT”
The usual process is: pg_dumpall –globals-only to get users/roles/etc pg_dump -Fc for each database to get a nice compressed dump suitable for use with pg_restore. Yes, this kind of sucks. I’d really like to teach pg_dump to embed pg_dumpall output into -Fc dumps, but right now unfortunately it doesn’t know how so you have to … Read more
Did you try specifying the host, user, & db? pg_dump -U someuser -h localhost somedb > directory/somefile.dump
For regular backups I’d go for option 1, using PostgreSQL’s own native tool, as it is probably the most efficient. I would argue that option 2 is primarily concerned with creating the tables and loading initial data so is not suitable for backups. Option 3 can be used for backups and would be particularly useful … Read more
This happens if, when you made the backup, you had multiple files listed in the backup destination textbox. Go back to your source server and create the backup again; this time, make sure there’s only one destination file listed. If you had more than one file listed as the backup destination, the backup is striped … Read more
There is a step by step explanation (with pictures) available @ Restore DataBase Click Start, select All Programs, click Microsoft SQL Server 2008 and select SQL Server Management Studio. This will bring up the Connect to Server dialog box. Ensure that the Server name YourServerName and that Authentication is set to Windows Authentication. Click Connect. … Read more