Tag Info

New answers tagged

0

STEP 01 Go see if MySQL is running on the Server. Run this service mysql status If the status says SUCCESS! MySQL running (some number) then shutdown mysql service mysql stop STEP 02 Run ls -l /etc/my.cnf. If the file exists, rename it with mv /etc/my.cnf /etc/my.cnf.backup Then, copy your my.cnf into /etc STEP 03 See if you have a previous mysql ...


1

Finally after two days I get those error, because of lack of memory you need to add more memory if you work with big collection.


1

Perhaps you should dump the users and load the users into the VM Here is my post : Export all MySQL users After running the code in it and saving it to a file called MyDatabaseUSers.sql, you log into mysql on the VM and run this: mysql> source MyDatabaseUSers.sql This will create all the users with the same grants and passwords. Don't worry: ...


0

I'm sorry, I don't have a corrupt pg_conversion table to help perform any verifications. My answers here must, by necessity, be heavily based on speculation. With the limited information we have, I am guessing that you are attempting to do a full database pg_dump, along the lines of pg_dump --host 127.0.0.1 --port 5432 --username "postgres" ... ...


0

What is the best approach to migrate all databases in single shot to the new instance without doing one at a time? Log Shipping is a very effective approach for a situation like this... Configure Log Shipping to the new server for all 8 databases. When ready to migrate, use this solution to fail over all databases at the same time. Run the script ...


1

For first you can configure log shipping to a new box. So at any given time you can switch to new box fast, but it will be impossible to revert to an old box if something happened after you have started to work with databases on a new box.


2

First thing i would like to highlight is you should have the system backups in addition to user databases handy when you said you need to migrate from SQL2k5 to SQL2k8R2. You can copy all the latest backups from the current server onto the Windows2K8 box you mentioned. Once copied, the first thing you should be looking is restoring the system database ...


2

Original Answer (leaving for people that might hit this because of the simple explanation): The clusterAdmin role only applies when you authenticate against the admin database, so unless you specify the --authenticationDatabase option to be admin when you are running mongodump/mongorestore I suspect you are getting a lesser privilege when authing against ...


1

That's the error you get when you restore the master database from a server with AlwaysOn Availability Groups configured, or try to restore additional user databases onto a server that had the master database from an AG replica restored. Don't restore the master database from an AG replica onto a different SQL Server as the master database. If you ...


0

If the file is what you have in hand and you are manipulating it from a shell / console, I would use sed to do string replacements on lines starting with CREATE DABATASE, USE and optionnally -- (mysqldump comments) Replacing the db name on lines that matches Create Database, Use and mysqldump comments dbfile="yoursqldumpfile.sql"; dbname="current_db_name"; ...


0

We have the below script handy when have a scenario to restore multiple tran logs in sequence during an issue from here DECLARE @databaseName sysname DECLARE @backupStartDate datetime DECLARE @backup_set_id_start INT DECLARE @backup_set_id_end INT -- set database to be used SET @databaseName = '<your_database_name_here>' SELECT @backup_set_id_start ...


4

I would suggest to use Restore Gene : Automating SQL Server Database Restores - written by Paul Brewer The Restore Gene stored procedure generates the required restore scripts, including the DBCC CHECKDB command, if required. It is a useful tool, by itself; in disaster recovery situations, it can construct a restore script, in seconds. It optionally ...


0

This uses xp_cmdshell to look at the file system for the log files. If you're OK with that.... DECLARE @databaseName AS VARCHAR(100) DECLARE @restoreName AS VARCHAR(100) SET @databaseName = 'OriginalDBName' SET @restoreName = 'RestoredDBName' CREATE TABLE #dirList ( id int identity(1,1), line nvarchar(1000) ) DECLARE @cmdShellStatement ...


1

Check if the SQL Server user account is able to read from "\Mylocation\DBRestores\", the security permissions from file share and file system. To really test that it works, copy the backup to local server and run it from there.


0

This part of your SQL is incorrect DISK = N'\Mylocation\DBRestores\MyBackupFile' it should be for example DISK = N'\Mylocation\DBRestores\MyBackupFile.bak' you are supplying a directory but should be supplying the full spec of the backup file.


2

CREATE VIEW or CREATE TABLE... AS SELECT have to infer the column types for the relation to create. Sometimes the context is not sufficient to guess a datatype, for example when it's just a string literal. In this case it's created as unknown. Example : test=> CREATE VIEW testview AS SELECT 'bla' AS foobar; WARNING: column "foobar" has type "unknown" ...


0

Based on the first error message, the .gz backup file seems to be truncated. This could be confirmed with the command: gunzip -c my_db_dump.sql.gz >/dev/null Presumably this will lead to the same error message: unexpected end of file which is the root cause, the other error from postgres being the consequence of the abrupt end of the data stream. If ...


1

With the default settings, when rows (or entire tables) are deleted, SQLite does not remove empty pages from the database file. (This setting can be changed with PRAGMA auto_vacuum.) In most cases, keeping empty pages in the database file is good idea because they will be reused by new rows that are inserted later, and adjusting the database file to remove ...


0

Sorry for the above wrong input. I had not followed the question. Here is another set of solution for the above problem: Step 1: create .monetdb file in the home directory as below: cat << EOF > $HOME/.monetdb user=monetdb password=monetdb EOF Step 2: Replace the above content with your monetdb username and password. Step 3:Change the file ...



Top 50 recent answers are included