InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 03:50:46 GMT20http://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxHi,You shoul be try any third party data recovery software for recover your data of SQL.There are so may software you can select one of them for your information i can recommended you one of them which is "Kernel for SQL Server Repair" you can try this software to repair SQL server.Mon, 03 Sep 2012 06:50:14 GMTkarrylopezhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxBooks Online, the section bcp (stands for bulk copy program)Fri, 10 Aug 2012 05:10:35 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxhow to use BCP out? i never do this b4. can u show the related articles? tq 4 info...Thu, 02 Aug 2012 02:13:25 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxAs I said, export what data you can from the damaged database to flat files (use BCP out or just query and copy). Then restore the latest version and use some tool (any tool, datacompare's just the one I know) to sync the restored database with the data you exported.Tue, 31 Jul 2012 10:55:54 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxyes, i know that the system tables was damaged especially sysindexes & sysindexkeys. the important thing is a data from the main table. what Redgate's SQLDataCompare can do for this? i ever use stella phoenix, kernel, systool & mdfviewer but it just viewing only & cannot export to other file...Tue, 31 Jul 2012 09:25:17 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxIt's not repairable. The damage is in the system tablesI suggest you export all the data that you can from the tables that you can query (bcp out or similar) then restore the latest backup that you have. Then you can use the exported data with something like Redgate's SQLDataCompare to get the restored database as close to current as possible.Tue, 31 Jul 2012 01:54:58 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxoh, i'm so sorry...forgot to ans it. i have old backup before hard disk failure. i just get mdf & ldf file only after retrieving. i try to set emergency mode but certain table can view correctly & some table show; "I/O error (bad page ID) detected during read at offset 0x000000f9a70000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\Data\PMSdb.mdf'." after viewing. so how to repair it using SQL command?Mon, 30 Jul 2012 19:34:36 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspx[quote][b]slizam (7/30/2012)[/b][hr]that is for the demo version only, it just for viewing & cannot take the data unless pay more for it :-)[/quote]Of course. And some don't work after you've paid either. Buyer beware, they may get something back, they may get nothing back.But you haven't answered my question about log backups. Do you have any?If not, with the DB in emergency mode can you query any of the tables?Mon, 30 Jul 2012 10:53:39 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxthat is for the demo version only, it just for viewing & cannot take the data unless pay more for it :-)Mon, 30 Jul 2012 10:45:39 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspx[quote][b]slizam (7/29/2012)[/b][hr]if i restore the last full backup, how about the data since then lost? [/quote]In this case, You should use SQL repair software. You can easily search these software on Google: [url=http://www.google.com/search?hl=&q=sql+repair+software]http://www.google.com/search?hl=&q=sql+repair+software[/url]Sun, 29 Jul 2012 22:47:28 GMTprettsonshttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxWas the database in full recovery model?Do you have log backups since that last full backup?Sun, 29 Jul 2012 07:00:07 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxif i restore the last full backup, how about the data since then lost? Sun, 29 Jul 2012 04:14:15 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxIf you don't have any log backups, then you'll just have to restore the last full backup that you have and accept the data since then lostSat, 28 Jul 2012 05:01:36 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxwhen i run this...backup log PMSdbto disk='D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb_Log.trn'with NO_TRUNCATEServer: Msg 3033, Level 16, State 1, Line 1BACKUP DATABASE cannot be used on a database opened in emergency mode.Server: Msg 3013, Level 16, State 1, Line 1BACKUP LOG is terminating abnormally.i have no backup log...FYI, my database (PMSdb.mdf) was corrupted before this when i attach database and the result is...Error823: I/O error (bad page ID) detected during read at offset 0x000000e1b78000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\DATA\PMSdb.mdf'.actually, what is the correct step?Fri, 27 Jul 2012 19:55:54 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxbackup log PMSdbto disk='D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb_Log.trn'with NO_TRUNCATEYou do not use NORECOVERY in a disaster situation (damaged or missing data file). You use it when backing up a working and online database in preparation for a restore.Continue after error was added in SQL 2005.Is the DB in full recovery and do you have log backups at all?Fri, 27 Jul 2012 11:59:28 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspx[quote][b]Scott D. Jacobson (7/27/2012)[/b][hr]"NORECOVERY", no underscore.[/quote]Nice catch, mistake in my typing. I should have just done a cut and paste.Fri, 27 Jul 2012 11:09:46 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxbackup log PMSdbto disk='D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb_Log.bak'with NO_TRUNCATE,NORECOVERYMsg 3031, Level 16, State 1, Line 1Option 'no_truncate' conflicts with option(s) 'norecovery'. Remove the conflicting option and reissue the statement.backup log PMSdbto disk='D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb_Log.bak'with NORECOVERYMsg 3101, Level 16, State 2, Line 1Exclusive access could not be obtained because the database is in use.Msg 3013, Level 16, State 1, Line 1BACKUP LOG is terminating abnormally.Fri, 27 Jul 2012 10:29:29 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspx"NORECOVERY", no underscore.Fri, 27 Jul 2012 10:10:01 GMTScott D. Jacobsonhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxsorry -- backup log dbname to disk with no_truncate,norecoveryFri, 27 Jul 2012 10:08:55 GMTHadrianhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxuse backup log with no_truncateFri, 27 Jul 2012 10:05:41 GMTHadrianhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxmssql2000Fri, 27 Jul 2012 09:58:08 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxwhich mssql version?Fri, 27 Jul 2012 09:51:46 GMTHadrianhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxbackup log PMSdbto disk='D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb_Log.bak'WITH NO_RECOVERYMsg 155, Level 15, State 1, Line 3'NO_RECOVERY' is not a recognized BACKUP option.Fri, 27 Jul 2012 09:48:34 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxTry:BACKUP LOG database_name TO <backup_device> WITH NO_RECOVERYBased on what I read here:[url]http://msdn.microsoft.com/en-us/library/aa225964(v=sql.80)[/url]Fri, 27 Jul 2012 09:39:33 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxNo truncate...backup log PMSdbto disk='D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb_Log.bak'with NO_TRUNCATEServer: Msg 3033, Level 16, State 1, Line 1BACKUP DATABASE cannot be used on a database opened in emergency mode.Server: Msg 3013, Level 16, State 1, Line 1BACKUP LOG is terminating abnormally.continue after error...backup log PMSdbto disk='D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb_Log.bak'with CONTINUE_AFTER_ERRORServer: Msg 155, Level 15, State 1, Line 3'CONTINUE_AFTER_ERROR' is not a recognized BACKUP option.Fri, 27 Jul 2012 09:29:10 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxBACKUP LOG database_name TO <backup_device> [WITH { CONTINUE_AFTER_ERROR | NO_TRUNCATE }Fri, 27 Jul 2012 08:40:19 GMTHadrianhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxbackup log not backup database!Fri, 27 Jul 2012 08:36:27 GMTHadrianhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxBack up the tail of your transaction log...is it this one?BACKUP DATABASE [PMSdb] TO DISK = N'D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\PMSdb.bak' WITH NOFORMAT, NOINIT, NAME = N'PMSdb-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10GObut the result is...Msg 3033, Level 16, State 0, Line 1BACKUP DATABASE cannot be used on a database opened in emergency mode.Msg 3013, Level 16, State 1, Line 1BACKUP DATABASE is terminating abnormally.from table sysdatabases, PMSdb status is 4194328 not 32768 (emergency mode)Fri, 27 Jul 2012 08:26:55 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxBack up the tail of your transaction log.Restore your database from the most recent good backup, with NORECOVERY.Restore the transaction logs up to the point immediately before the corruption occurred.Recover the database.Investigate the cause of the corruption and check that all your firmware and drivers for RAID and so on are up to date.JohnFri, 27 Jul 2012 08:04:11 GMTJohn Mitchell-245523http://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxwhen i running this...DBCC CHECKDB('PMSdb') WITH NO_INFOMSGSServer: Msg 8966, Level 16, State 1, Line 1Could not read and latch page (1:399112) with latch type SH. sysindexes failed.and DBCC CHECKTABLE ('sysindexes') WITH NO_INFOMSGSServer: Msg 8966, Level 16, State 1, Line 1Could not read and latch page (1:399112) with latch type SH. sysindexes failed.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 1735289202, index ID 26996, page ID (1:399112). The PageId in the page header = (8224:538976288).CHECKTABLE found 0 allocation errors and 1 consistency errors in table '(Object ID 1735289202)' (object ID 1735289202).repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (PMSdb.dbo.sysindexes ).what should i do after this? lets discuss it...Fri, 27 Jul 2012 07:51:42 GMTslizam