Tag Info

New answers tagged

-1

Method 1: Restore from the latest good msdb backup Method 2: EXEC sp_resetstatus 'msdb' ALTER DATABASE msdb SET EMERGENCY DBCC CheckDB ('msdb') ALTER DATABASE test SET SINGLE_USER WITH ROLLBACK IMMEDIATE DBCC CheckDB ('msdb', REPAIR_ALLOW_DATA_LOSS) ALTER DATABASE msdb SET MULTI_USER Method 3: Stop the Sql service locate the msdb mdf and ldf ...


1

InnoDB makes it impossible to just cut and paste a database because each .ibd files has tablespace_id that are referenced in the data dictionary within c:/ProgramData/Mysql/Mysql Server 5.5/data/ibdata1. Here is a Pictorial Representation of InnoDB (from Percona CTO Vadim Tkachenko) You cannot recover just a database. You must restore the entire data ...


0

IMHO you MUST take transaction log backup before swithching to simple recovery it would help you in PIT recovery as well as its documented and recommended in BOL Article. It wont do any harm and you will have a failsafe. Please also note its advisable to change recovery model when load on database is relatively less. Although you can change it in peak hour ...


1

Once you switch to Simple the Trans Log will no longer maintain a log of operations since your last (database files) backup - at the point of the switch all transactions will have been committed to the main database files so will not be discarded - they are already effective in the database files. Your point 1 is not (in my opinion) worth doing - once ...


-1

please check user rights for that drive. May be problem is with access rights for particular drive. Give full rights for that drive with 'everyone' user. Your problem will sort out. Restart Sql server instance and check database status, your recovery pending error is solved. Thanks


1

To be clear, the issue is really with the PRINT command and not the SQLCMD utility. I am guessing that your variable is actually NVARCHAR(MAX), not VARCHAR(MAX) since the PRINT command is limited to only 4000 characters using NCHAR / NVARCHAR. Otherwise it can output up to 8000 characters using NVARCHAR / CHAR. To see that VARCHAR does go beyond 4000 ...


0

Yes, following the backup output: RMAN> list backup; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 10 Full 1010.57M DISK 00:00:48 02-APR-15 BP Key: 10 Status: AVAILABLE Compressed: NO Tag: ...



Top 50 recent answers are included