Hi,Im completely inexperienced with SQL databases, and Im in desperate need of help trying to get a database migrated from my Dad's old computer to his new one.I apologize in advance for being long winded...Brief back story:Old computer was running XP and SQL Server 2005 with a proprietary medcal front end program called Chiro8000, which created database called PM_CHIRO.mdf. Old PC's motherboard decided it had had enough of life and one morning it simply stopped turning on. I put together a new computer with the exact same software, and installed the old harddrive as a slave so i could access the data.The new install of the Chiro8000 program created its own empty database at C:\Program Files\Forte Systems\Chiro8000\Data\PM_CHIRO.mdfThe old database I need to restore is at D:\Program Files\Forte Systems\Chiro8000\Data\PM_CHIRO.mdfThe Chiro program has a "database manager tool" but Ive been using MS SQL Server Management Studio ExpressObviously if I try to just attach the old one I get "Cannot attach a database with the same name as an existing database" error.So I try detaching the new blank one and attaching the old version, which gives me: ______________________________________________________________________________________________________________An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)The log scan number (9884:437:2) passed to log scan in database 'PM_CHIRO' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. Could not open new database 'PM_CHIRO'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 9003)_______________________________________________________________________________________________________________There is no .BAK to restore from, and the old database worked fine up until the point that the computer died. For those wondering, it did not crash while running, it shut down politely and then refused to turn on. I've also tried to rebuild the log using the syntax:USE [master]GOCREATE DATABASE [PM_CHIRO] ON (FILENAME = N'D:\Program Files\Forte Systems\Chiro8000\Data\PM_CHIRO.mdf') FOR ATTACH_REBUILD_LOGGOWhich gives me the error:Msg 5173, Level 16, State 1, Line 1One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.Log file 'C:\Program Files\Forte Systems\Chiro8000\Data\PM_CHIRO_log.LDF' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.Msg 1813, Level 16, State 2, Line 1Could not open new database 'PM_CHIRO'. CREATE DATABASE is aborted.So at this point...no clue... I'm sure all of you SQL people out there could figure this out pretty quick, but Im way over my head as it is. I dont have a .BAKIf its a corruption issue Id love to know how to repair it, even if it means possibly losing some data, because right now Im up a creek without a paddle....and theres a waterfall...made of sharks.Thanks in advance.
↧
Trying to migrate old mdf to new system, possible corruption?
↧
cannot attach mdf file
Hi,I have the following problem: Due to a harddisk problem the database went into Suspect mode.I don't want to risk losing any data by trying to fix it directly on the server since there are no recent backups so I copied the mdf and ldf files to another computer. While trying to attach the files a message came out: Attach database failed for Server 'SALESIRM\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)------------------------------For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476------------------------------Program Location: at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files, String owner) at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabaseData.PrimaryFile.Attach() at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabase.SendDataToServer()===================================An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)------------------------------Program Location: at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType) at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection queries) at Microsoft.SqlServer.Management.Smo.Server.AttachDatabaseWorker(String name, StringCollection files, String owner, AttachOptions attachOptions) at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files, String owner)===================================SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:12459; actual 0:0). It occurred during a read of page (1:12459) in database ID 5 at offset 0x00000006156000 in file 'C:\Users\Terziyski\Desktop\insider\IrmCrm.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.During redoing of a logged operation in database 'IrmCrm', an error occurred at log record ID (14623:1865:10). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.Could not open new database 'IrmCrm'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)------------------------------For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=824&LinkId=20476------------------------------Server Name: SALESIRM\SQLEXPRESSError Number: 824Severity: 24State: 2Line Number: 1------------------------------Program Location: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)My question is: Is there a way to attach the mdf and ldf files or should I risk and try to remove the Suspect mode on the server?Regards
↧
↧
Question
The ssis db in the c drive is getting full with the transaction log files when the packages are running for evry 2 minutes...how can I delete the transaction files in ssis db
↧
Unable to Start Backup Exec And MS SQL Services and Databases SQL 2005
getting the errors belowIn Event viewer I have Event ID 17120 SQL Server Could not Spawn FRuncm thread check the sql server error log and the windows event logs for information about possible related problems.Event id 17826 Could not start the Network Library because of an internal error in the netwpork library. To determine the cause review the errors immediately preceding this one in the error log.Also Event id 17182 TDSSN1 Client initialization failed with error 0x2,status code 0x1I think this link could help me but I do not knowwhat is the domain login account for the SQL service is in sql 2005.Please see the link belowhttp://www.sqlteam.com/forums/topic.asp?TOPIC_ID=163860I hope someone can help me with this. this broken Backup exec Database has become a nightmare. Two of the sql databases, both the bkup exec one and one called MS SQlserver will not start under services and the local system account or the Administrator account.I also tried this http://www.sqlserverblogforum.com/tag/could-not-spawn-fruncm-thread/ but it will not work.Ouya Master
↧
5242 errors
Hi,I recieved the following 5242 error today.An inconsistency was detected during an internal operation in database 'XXXXX'(ID:15) on page (1:161834). Please contact technical support. Reference number 6.A dbcc checkdb with ALL_ERRORMESSAGES comes up cleanbut a dbcc page(xxx,1,161834) gives a severe error.What is likely to cause these errors? How is the best way to fix this? If I restore with transaction log backup the severe error dbcc page(xxx,1,161834) goes away.
↧
↧
Transaction log backup is not working
I am trying to take transaction log backup using following query -BACKUP LOG [Test] TO DISK = N'X:\Backup\TestLog.trn' WITH NOFORMAT, NOINIT, NAME = N'TestLog', SKIP, REWIND, NOUNLOAD, STATS = 10But it gives me error -Msg 3049, Level 16, State 1, Line 1BACKUP detected corruption in the database log. Check the errorlog for more information.Msg 3013, Level 16, State 1, Line 1BACKUP LOG is terminating abnormally.I am using sqlserver 2008. How can i fix this?thanks in advance,Harish
↧
Can't drop, detach or set SUSPECT database to emergency mode
I have a database in a dev enviroment that is in SUSPECT mode. This is 2005. I don't need to recover the database. It is just development and the users can restore and/or upgrade from backup. I just want to remove it. I have browsed the forums but have not found a way to do it. Here is what I tried and the messages I received back:> drop database my_databaseMsg 926, Level 14, State 1, Line 1Database 'my_database' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.> EXEC sp_detach_db 'my_database';Msg 3707, Level 16, State 2, Line 1Cannot detach a suspect database. It must be repaired or dropped.> ALTER DATABASE my_database SET EMERGENCY;Msg 926, Level 14, State 1, Line 1Database 'my_database' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.Msg 5069, Level 16, State 1, Line 1ALTER DATABASE statement failed.I am not sure what else to try. Is there a way to force a db to be dropped? I can't open/view the errorlog (another issue, perhaps related?). I get an error message saying "Unicode File expected". Our RAID 5 had some issues last week and the systems guy fixed that. There are also 5 dbs whose state is "Recovery_Pending". I mention this in case it is all related and that it might help. I would like to remove these as well but I will tackle one issue at a time. :) Thanks!
↧
DBCC Checkdb consistency Error on Production Database
Hi All,My production server details are :Microsoft SQL Server 2005 - 9.00.5000.00 (X64) Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2) I have had a consistency error on one of my databases last week in a non clustered index on a table and I had dropped and recreated the non-clustered index to get rid of it.Following the incident, I came across another cnsitency check error on the same table and I have attached a complete dump of the error.Is repair_allow_data_loss the only option here? Do I have to take a downtime for this activity since this is a critical production database?Thanks in advance..
↧
CheckDB on Read_only database sometimes reports issues ??
Last week I noticed DBCC Checkdb reported an issue with one of my databases. ( SQL 2005 Enterprise Edition (64-bit) 9.00.5000.00 SP4 )[quote]CHECKDB found 0 allocation errors and 1 consistency errors in table 'sys.sysmultiobjrefs' (object ID 75).[b] [SQLSTATE 01000] (Error 8990) CHECKDB found 0 allocation errors and 1 consistency errors in database 'MYDB'. [SQLSTATE 01000] (Error 8989) repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MYDB). [SQLSTATE 01000] (Error 8958) DBCC execution completed.[/b] If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Error 2528). The step failed.[/quote]As this database is a read_only database and has been in that state for a long time, I wondered what could have caused this corruption.I didn't repair anything, drives have enough space, no RAM pressure, ...This weekend, the same DBCC Checkdb job reported no issues at all with that database.[b]Any hints as to why DBCC Checkdb gave me a false positive/negative ??[/b]
↧
↧
order of rows during bulk insert
Hi,When a bulk insert is done from a flat file or a xls file, how do u ensure the rows are added in the same order as they are in the xls file?Basically, I want to load the data into a table which has an identity column which would need to store the rownumber of each record in the original flat file or xls file.Thanks.
↧
DBCC CheckDb Error Message
Hi,I'm trying to recover a database which unfortunately we don't have any backups of.I have ran the following command "DBCC CHECKDB ('CustomerAccounts') WITH TABLOCK, ALL_ERRORMSGS, NO_INFOMSGS;"And I'm getting this error:Msg 8921, Level 16, State 1, Line 1Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.Msg 8968, Level 16, State 1, Line 1Table error: SinglePage page (0:249856) (object ID 485576768, index ID 2, partition ID 72057594097827840, alloc unit ID 72057594105167872 (type In-row data)) is out of the range of this database.CHECKDB found 1 allocation errors and 0 consistency errors in table 'CTL_DBCONFIG' (object ID 485576768).CHECKDB found 1 allocation errors and 0 consistency errors in database 'CustomerAccounts'.Msg 824, Level 24, State 2, Line 1SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x369dfd27; actual: 0xd5f0c896). It occurred during a read of page (1:1599) in database ID 7 at offset 0x00000000c7e000 in file 'D:\Act Database Files\CustomerAccounts.ADF'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.Please could someone advise.
↧
Unable to attach MDF File to sql server
Dear All,Please help, I'm unable to attach mdf file to the sql server . Error Message :An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
↧
DBCC CHECKDB wont run - Interesting Challenge
Hi All,Very long time since i was last here.Need some advice with this challenge, hopefully Gail or Paul might be around?.SQL 2005 SP2Dedicated NAS - about 8 years old3.5TB database split over multiple volumes, largest datafile is 2.3TB.operating system is windows 2003There have been issues with sql database consistency problems being reported for quite a while, checks on the storage indicate no problem, but I am not convinced. Database is still usable and is a production server, but the server is restarted/rebooted on what used to be weekly, to pretty much every day and recently 3-4 + times a day now.got about 200K messages like the following within the last 24 hours, although this has been ongoing for a long time.SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x75cac85e). It occurred during a read of page (6:91296219) in database ID 5 at offset 0x0000ae223b6000 in file 'I:\.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x784b5a48; actual: 0xe8681f5f). It occurred during a read of page (6:91088683) in database ID 5 at offset 0x0000adbce56000 in file 'I:\.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 6:91296185; actual 2057:151455495). It occurred during a read of page (6:91296185) in database ID 5 at offset 0x0000ae22372000 in file 'I:df'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.basically error 824 serverity 24 state 2all within the same datafile, and ironically one that has autogrowth switched off.msdb..suspect_pages currently has 405 rows with the errorcount for each row varying from 1 to 100kwhen i try to run dbcc checkdb with any options i getMsg 1823, Level 16, State 2, Line 1A database snapshot cannot be created because it failed to start.Msg 5123, Level 16, State 1, Line 1CREATE FILE encountered operating system error 1450(error not found) while attempting to open or create the physical file 'H:\.mdf:MSSQL_DBCC11'.Msg 7928, Level 16, State 1, Line 1The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.Msg 5030, Level 16, State 12, Line 1The database could not be exclusively locked to perform the operation.Msg 7926, Level 16, State 1, Line 1Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.Is causing me a few headaches, no backups exist for this database, dont get me started :-Pdatabase is absolutely critical to the businessReally need advice from someone who understands DBCC CHECKDB extremely well, as I am not sure if the reason DBCC CHECKDB doesnt run, could be down to insufficent space to create the internal snapshot, if someone could give a rough estimate on how much space is required, for a 3.5 TB database, that would be great and bad in a way, as I cannot add any more storage to this server.Seriously hoping i dont need to go down the DBCC PAGE and IND route, with hex editior in hand but have endless supply of caffeine if required. ;-)Any helpful advice is always appreciated, if you need more info, just let me know.CheersDarrennew update, think i might be in new world of painmanaged to work with dbcc checktable briefly, still errors out but recommended repair is allow data loss.done it with estimateonly with main table, need close to 300GB for tempdb, that drive has 2GB free and cannot be increased.
↧
↧
MSSQL logs eating disk space
Hi Guys,We are having an issue with MSSQL logs (C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\) eating disk space after making a backup restore of the server. Logs were eating up to 10 Gb of space in just a day. server crestes SQLDumpxxxx.log,SQLDumpxxxx.mdmp and SQLDumpxxxx.txt> Tried deleting it but it keeps generating logs.[quote]2014-02-15 22:26:37.55 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86) Dec 10 2010 10:56:29 Copyright (c) 1988-2005 Microsoft Corporation Express Edition with Advanced Services on Windows NT 6.0 (Build 6002: Service Pack 2)2014-02-15 22:26:37.57 Server (c) 2005 Microsoft Corporation.2014-02-15 22:26:37.57 Server All rights reserved.2014-02-15 22:26:37.57 Server Server process ID is 11764.2014-02-15 22:26:37.57 Server Authentication mode is WINDOWS-ONLY.2014-02-15 22:26:37.57 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.2014-02-15 22:26:37.57 Server This instance of SQL Server last reported using a process ID of 3004 at 2/15/2014 10:19:40 PM (local) 2/16/2014 6:19:40 AM (UTC). This is an informational message only; no user action is required.2014-02-15 22:26:37.57 Server Registry startup parameters:2014-02-15 22:26:37.57 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf2014-02-15 22:26:37.57 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG2014-02-15 22:26:37.57 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf2014-02-15 22:26:37.60 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.2014-02-15 22:26:37.60 Server Detected 4 CPUs. This is an informational message; no user action is required.2014-02-15 22:26:38.14 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.2014-02-15 22:26:38.49 Server Database mirroring has been enabled on this instance of SQL Server.2014-02-15 22:26:38.53 spid5s Starting up database 'master'.2014-02-15 22:26:38.74 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.2014-02-15 22:26:39.08 spid5s SQL Trace ID 1 was started by login "sa".2014-02-15 22:26:39.11 spid5s Starting up database 'mssqlsystemresource'.2014-02-15 22:26:39.13 spid5s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.2014-02-15 22:26:39.52 spid8s Starting up database 'model'.2014-02-15 22:26:39.55 spid5s Server name is 'CORP\SBSMONITORING'. This is an informational message only. No user action is required.2014-02-15 22:26:39.75 Server The certificate was successfully loaded for encryption.2014-02-15 22:26:39.77 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SBSMONITORING ].2014-02-15 22:26:39.77 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SBSMONITORING\sql\query ].2014-02-15 22:26:39.77 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.2014-02-15 22:26:39.78 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.2014-02-15 22:26:39.95 spid8s Clearing tempdb database.2014-02-15 22:26:39.97 spid5s Starting up database 'msdb'.2014-02-15 22:26:41.37 spid8s Starting up database 'tempdb'.2014-02-15 22:26:41.78 spid5s Recovery is complete. This is an informational message only. No user action is required.2014-02-15 22:26:41.79 spid11s The Service Broker protocol transport is disabled or not configured.2014-02-15 22:26:41.79 spid11s The Database Mirroring protocol transport is disabled or not configured.2014-02-15 22:26:41.89 spid11s Service Broker manager has started.2014-02-15 22:30:00.20 Server Server resumed execution after being idle 166 seconds: user activity awakened the server. This is an informational message only. No user action is required.2014-02-15 22:30:00.43 spid51 Starting up database 'SBSMonitoring'.2014-02-15 22:30:01.55 spid51 Recovery is writing a checkpoint in database 'SBSMonitoring' (5). This is an informational message only. No user action is required.2014-02-15 22:32:41.27 spid51 ex_raise2: Exception raised, major=52, minor=43, state=1, severity=22, attempting to create symptom dump2014-02-15 22:32:41.28 spid51 Using 'dbghelp.dll' version '4.0.5'2014-02-15 22:32:41.28 spid51 **Dump thread - spid = 51, PSS = 0x804ED540, EC = 0x804ED5482014-02-15 22:32:41.28 spid51 * 2014-02-15 22:32:41.28 spid51 * User initiated stack dump. This is not a server exception dump.2014-02-15 22:32:41.28 spid51 * 2014-02-15 22:32:41.28 spid51 ***Stack Dump being sent to C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt2014-02-15 22:32:41.28 spid51 * *******************************************************************************2014-02-15 22:32:41.28 spid51 *2014-02-15 22:32:41.28 spid51 * BEGIN STACK DUMP:2014-02-15 22:32:41.28 spid51 * 02/15/14 22:32:41 spid 512014-02-15 22:32:41.28 spid51 *2014-02-15 22:32:41.28 spid51 * ex_raise2: Exception raised, major=52, minor=43, state=1, severity=22[/quote]Also, just recently we have noticed that disabling the SBS$MONITORING stop it from generating logs. Any idea how is it related, or what could be the issue.Any advise is greatly appreciated.Thank you,jace
↧
corrupted mdf file
hello: i was given a corrupted mdf file, the server the database (sql 2000) crashed and the only file recovered was this .mdf file. I have tried as many of the options that i can find, and still cannot get this database recovered. downloaded several of the programs that claim to be able to recover mdf files and none work.. This latest gives me the following error:SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0xd8b4c0f2). It occurred during a read of page (0:0) in database ID 0 at offset 0000000000000000 in file 'C:\DBIO\testy.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.I created a new database (sql 2008 r2) since I do not have sql 2000 anywhere. renamed the mdf file and then renamed the corrupted one to the new name and restarted. This then brings up the db in recovery_pending mode and I cannot get it out of that mode. Tried setting it to emergency mode, no luck. Is there anyway for me to recover this db? No there were no backups of this database at all, and yes, i completely agree that a backup strategy is needed, but i'm just the lucky recipient of the issue :)thank you for any help!
↧
No catalog entry found for partition ID (MSSQL 2005)
I've seen few posts regarding this error msg but none that have yet helped me. This error has happened a few times in our environment at seemingly random times, necessitating a restart of the DB service. SQL logs the error as:Date 9/13/2009 1:06:36 AMLog SQL Server (Archive #1 - 9/13/2009 1:09:00 AM)Source spid57MessageNo catalog entry found for partition ID xxx in database yyy. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.In the Windows Event Viewer:Source:MSSQLSERVERTime: 1:06:36 AMCategory: (2)Type: ErrorEventID: 608Description:No catalog entry found for partition ID xxx in database yyy. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.The following SQL statement returns no results:SELECT OBJECT_NAME([object_id]) FROM sys.partitions WHERE partition_id = xxxThe SQL log does provide the SpID...is it possible to identify the process that ran into this problem? Are there additional things I can look at to try and determine where/what is causing this problem.Further Note: I do not have any jobs scheduled for this time and DBCC returns no errorsTIA
↧
Backup Failed SQL 2005
Hi,I cant able to take the database full backup its says database log file is corrupted. Please find the attached screenshot for your ref.Its very urgent. Please help on this.
↧
↧
how to restore .ndf file in database SQL 2005
hi all,i have mistakenly deleted .ndf file of the database and but i have a backup of that file any one help my how to restore .ndf file in my database or any other suggestion so that my database can worked again right now by database is currpt its not working properly
↧
Backup failed but DBCC CHECKDB has no errors
SQL 2008 R2 Database. Backup failed with this message:BACKUP 'Db' detected an error on page (1:24909497) in file 'D:\Data\Db.mdf'.Msg 3013, Level 16, State 1, Server xxxxx, Line 1BACKUP DATABASE is terminating abnormally.I ran DBCC CHECKDB on the database which came back without any errors. The backup ran successfully after that and the next day too.I looked at the page with DBCC PAGE - each time I ran it gave a different output. sometimes more sometimes less.msdb..suspect_pages has 2 entries for event type 1 and 2.What would I look for particularly on the output to check for corruption?What would be the next steps to make sure everything is good?Thanks!
↧
Corrupt DB -repair or restore
I have a dept who would prefer I repair instead of restore else they'll lose 4 hours of work:DBCC CHECKDB with PHYSICAL_only output:DBCC results for 'sysdevcq'.Msg 8909, Level 16, State 1, Line 2Table error: Object ID 0, index ID 0, page ID (1:1515894). The PageId in the page header = (0:2).CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.Msg 8928, Level 16, State 1, Line 2Object ID 181575685, index ID 255: Page (1:1515893) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 2Table error: Object ID 181575685, index ID 255, page (1:1515893). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.Msg 8928, Level 16, State 1, Line 2Object ID 181575685, index ID 255: Page (1:1515894) could not be processed. See other errors for details.There are 0 rows in 0 pages for object 'cq.attachments_blob'.CHECKDB found 0 allocation errors and 3 consistency errors in table 'cq.attachments_blob' (object ID 181575685).Msg 8928, Level 16, State 1, Line 2Object ID 629577281, index ID 0: Page (1:2085142) could not be processed. See other errors for details.Msg 8941, Level 16, State 102, Line 2Table error: Object ID 629577281, index ID 0, page (1:2085142). Test (sorted [i].offset <= m_freeData) failed. Slot 3, offset 0x202c is invalid.There are 0 rows in 0 pages for object 'cq.history'.CHECKDB found 0 allocation errors and 2 consistency errors in table 'cq.history' (object ID 629577281).CHECKDB found 0 allocation errors and 6 consistency errors in database 'sysdevcq'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (sysdevcq ).DBCC execution completed. If DBCC printed error messages, contact your system administrator.Can I repair or shall I restore? Where is Paul Randall when I need him.... :)cheers
↧