New answers tagged restore
Using tsql: CREATE DATABASE MyDB ON (FILENAME = 'D:\MySQLServer\MyDB.mdf'), (FILENAME = 'D:\MySQLServer\MyDB_Log.ldf') FOR ATTACH;
You've left out so much that your chances of recovering useful data are negligible. pg_clog contains the commit/rollback logs. Without these, the system doesn't know which parts of the database files are valid and which are not. (gross oversimplification, but hey). pg_xlog, the write-ahead logs. Without these, the database can't handle incomplete writes, ...
Alternatively you may consider setting up replications from the main server to your dev machines. It would require to have a direct connection from your master to the slaves (the dev machines), but it doesn't need to be permanent. If you connect it once a month then the master will replicate only the changes, which should still be much faster. I doubt any ...
You can take a backup from the live MySQL with Xtrabackup. Percona provides deb repository for Ubuntu. To install the repo for Ubuntu 12.04 follow instructions: Install the key: # apt-key adv --keyserver keys.gnupg.net --recv-keys 1C4CBDCDCD2EFD2A Add the source file: # cat /etc/apt/sources.list.d/percona.list deb http://repo.percona.com/apt precise ...
When a database backup is restored it almost immediately allocates the space needed for the database files. So a 300 GB database will quickly appear in the file system at full size, but the file will be essentially empty to start with. Once the space is allocated, the restore process goes on to read the backup file restoring data at the speed sustainable ...
[Can some moderator please make this answer a comment to Balazs Papp`s answer?] I'm not sure if the above solution works across different endianesses. I tried to copy a cold backup of a 64bit SPARC Database to a 64bit Linux x86 system and tried to verify the the answer but I keep getting errors e.g. if I try to generate a new control file I keep on getting ...
Mount the database and make a level 3 datafile header dump: alter session set tracefile_identifier = 'header_dump'; alter session set events 'immediate trace name file_hdrs level 3'; In the trace file, you will find this section: Platform Information: Creation Platform ID: 13 Current Platform ID: 13 Last Platform ID: 13 The platform ID identifies ...
You can't restore a 2008 backup on SQL Server 2005. Simply not possible. You'll need to either: (a) Restore it on 2008, then use Import/Export wizard, Generate Scripts Wizard, Copy Database Wizard, SSIS, 3rd party tools like SQL Compare, etc. to move the structure and data to the 2005 instance, or (b) Upgrade. Developer Edition is $50 or so.
Does this failover cluster impose any restrictions on this backup restore or will it be a normal backup restore operation. It will be a normal backup and restore operation (provided there are no other issues with the actual backup and/or restore). The fact that you are going from a standalone instance to a failover cluster instance will not negatively ...
I would use BigDump for this. BigDump - http://www.ozerov.de/bigdump/ - The script imports only a small part of the huge dump and restarts itself. The next session starts where the last was stopped.
Try some GUI clients like SQLyog or MySQL workbench.
You can use MySql Workbench for managing your remote database here is the link for downloading MySql Workbench http://dev.mysql.com/downloads/tools/workbench/
Top 50 recent answers are included