New answers tagged upgrade
I have completed the migration with no problems. Creating the dump is easy: sudo -u postgres pg_dump --verbose --no-tablespaces --format=directory --file=/backup/path old_database_name Restoring on a new instance: first, create a new tablespace, and a target database in that tablespace. Then import your dump like this: sudo -u postgres pg_restore ...
Since you are using pg_dump it will dump the schema and the data. pg_dump -d mydb -f dump_file_name.sql To restore you have to createdb first and then restore it so, the new name issue can be solved when creating the new database. createdb mynewdb For the tablespace, you first have to create the tablespace in the newly created database. create ...
Mysql version upgrade will not make any changes to your stored data from your database! But as a best practice make sure you make a full backup for your database(dump + cold bkp) before you start the upgrade process. Always have rollback plan
It depends on your downtime window. My preferred steps would be : -- take full backup from sql 2008 R2 and restore it on 2012 server. -- do all the post restore steps. -- Add the database to Availability Group. Possibly (with modifications as per your environment), you can use automatically add databases using T-SQL script.
Had a similar issue today. Had to migrate two databases from a 8.2.14 version to 9.3.2 plus switching operating systems from Suse to Ubuntu. I tried several ways, in the end the 'easiest' won. I created a dump with pg_dump but using inserts instead of copies and created the database from the dump file: pg_dump 'database' -f 'filename' -C -D -U 'user' -W ...
Top 50 recent answers are included