A MySQL MyISAM table is the combination of three files: The FRM file is the table definition. The MYD file is where the actual data is stored. The MYI file is where the indexes created on the table are stored. You should be able to restore by copying them in your database folder (In linux, … Read more
The other official way would be using git bundle That will create a file that supports git fetch and git pull to update your second repo. Useful for incremental backup and restore. But if you need to backup everything (because you do not have a second repo with some older content already in place), the … Read more
Yeah I just scored this one. Look in Windows Services. Start > Administration > Services Find the Service in the list called: SQL Server (MSSQLSERVER) look for the “Log On As” column (need to add it if it doesn’t exist in the list). This is the account you need to give permissions to the directory, … Read more
You want to set your db to single user mode, do the restore, then set it back to multiuser: ALTER DATABASE YourDB SET SINGLE_USER WITH ROLLBACK AFTER 60 –this will give your current connections 60 seconds to complete –Do Actual Restore RESTORE DATABASE YourDB FROM DISK = ‘D:\BackUp\YourBaackUpFile.bak’ WITH MOVE ‘YourMDFLogicalName’ TO ‘D:\Data\YourMDFFile.mdf’, MOVE ‘YourLDFLogicalName’ … Read more
git bundle I like that method, as it results in only one file, easier to copy around. See ProGit: little bundle of joy. See also “How can I email someone a git repository?”, where the command git bundle create /tmp/foo-all –all is detailed: git bundle will only package references that are shown by git show-ref: … Read more
From the pg_dump documentation: Examples To dump a database called mydb into a SQL-script file: $ pg_dump mydb > db.sql To reload such a script into a (freshly created) database named newdb: $ psql -d newdb -f db.sql To dump a database into a custom-format archive file: $ pg_dump -Fc mydb > db.dump To dump … Read more
I’d just drop the database and then re-create it. On a UNIX or Linux system, that should do it: $ dropdb development_db_name $ createdb development_db_name That’s how I do it, actually.
Check the installed version(s) of pg_dump: find / -name pg_dump -type f 2>/dev/null My output was: /usr/pgsql-9.3/bin/pg_dump /usr/bin/pg_dump There are two versions installed. To update pg_dump with the newer version: sudo ln -s /usr/pgsql-9.3/bin/pg_dump /usr/bin/pg_dump –force This will create the symlink to the newer version.
You could use something like (Linux): svnadmin dump repositorypath | gzip > backupname.svn.gz Since Windows does not support GZip it is just: svnadmin dump repositorypath > backupname.svn
I have just had this issue with SQL Server 2012. It turns out all I had to do was tick the box marked ‘Relocate all files to folder’ on the ‘Files’ section: (Click to see image full size) This of course assumes you have the correct version of SQL Server installed.