I am such a moron. I thought the error message was telling what's wrong with the database, but it appears I typed in the wrong sql command. Honestly, this is what I copied and pasted after search for a solution on google. Here's the error message I got with the CHECKDB command:
Database 'BTData' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Here's the last log file:
2011-03-19 13:53:35.92 Server Microsoft SQL Server 2005 - 9.00.1406.00 (Intel X86)
Mar 3 2007 18:40:02
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2011-03-19 13:53:35.92 Server (c) 2005 Microsoft Corporation.
2011-03-19 13:53:35.92 Server All rights reserved.
2011-03-19 13:53:35.92 Server Server process ID is 4224.
2011-03-19 13:53:35.92 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2011-03-19 13:53:35.92 Server This instance of SQL Server last reported using a process ID of 716 at 3/19/2011 1:16:10 PM (local) 3/19/2011 8:16:10 PM (UTC). This is an informational message only; no user action is required.
2011-03-19 13:53:35.92 Server Registry startup parameters:
2011-03-19 13:53:35.92 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-03-19 13:53:35.92 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-03-19 13:53:35.92 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-03-19 13:53:35.95 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-03-19 13:53:35.95 Server Detected 2 CPUs. This is an informational message; no user action is required.
2011-03-19 13:53:36.01 Server Error: 8313, Severity: 16, State: 1.
2011-03-19 13:53:36.01 Server Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
2011-03-19 13:53:36.01 Server Error: 3409, Severity: 16, State: 1.
2011-03-19 13:53:36.01 Server Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
2011-03-19 13:53:36.01 Server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
2011-03-19 13:53:36.62 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.
2011-03-19 13:53:36.70 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2011-03-19 13:53:36.75 Server The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2011-03-19 13:53:36.75 Server Database Mirroring Transport is disabled in the endpoint configuration.
2011-03-19 13:53:36.76 spid4s Starting up database 'master'.
2011-03-19 13:53:36.89 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-03-19 13:53:37.00 spid4s SQL Trace ID 1 was started by login "sa".
2011-03-19 13:53:37.03 spid4s Starting up database 'mssqlsystemresource'.
2011-03-19 13:53:37.26 spid4s Server name is 'MAIN-STATION'. This is an informational message only. No user action is required.
2011-03-19 13:53:37.26 spid8s Starting up database 'model'.
2011-03-19 13:53:37.40 spid8s Clearing tempdb database.
2011-03-19 13:53:37.57 Server A self-generated certificate was successfully loaded for encryption.
2011-03-19 13:53:37.59 Server Server is listening on [ 'any' <ipv4> 1433].
2011-03-19 13:53:37.59 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-03-19 13:53:37.59 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2011-03-19 13:53:37.61 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-03-19 13:53:37.61 Server Dedicated admin connection support was established for listening locally on port 1434.
2011-03-19 13:53:37.64 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2011-03-19 13:53:37.64 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-03-19 13:53:37.68 spid13s Starting up database 'ProList'.
2011-03-19 13:53:37.68 spid11s Starting up database 'msdb'.
2011-03-19 13:53:37.68 spid12s Starting up database 'test_BTData'.
2011-03-19 13:53:37.68 spid14s Starting up database 'BTData'.
2011-03-19 13:53:38.17 spid14s Error: 9003, Severity: 20, State: 9.
2011-03-19 13:53:38.17 spid14s The log scan number (7941:97506:1) passed to log scan in database 'BTData' 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.
2011-03-19 13:53:38.17 spid14s Error: 3414, Severity: 21, State: 1.
2011-03-19 13:53:38.17 spid14s An error occurred during recovery, preventing the database 'BTData' (database ID 7) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2011-03-19 13:53:40.11 spid8s Starting up database 'tempdb'.
2011-03-19 13:53:40.64 spid11s The Service Broker protocol transport is disabled or not configured.
2011-03-19 13:53:40.64 spid11s The Database Mirroring protocol transport is disabled or not configured.
2011-03-19 13:53:40.73 spid11s Service Broker manager has started.
2011-03-19 13:53:41.86 spid4s Recovery is complete. This is an informational message only. No user action is required.
2011-03-19 13:54:10.84 spid52 Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2011-03-19 14:15:42.76 Logon Error: 18456, Severity: 14, State: 16.
2011-03-19 14:15:42.76 Logon Login failed for user 'MAIN-STATION\SHOCKINGPRICE'. [CLIENT: <local machine>]
The database that has problem is "BTData". From this log, it looks like I have a corrupted log file? When I copy the files from one machine and pasted it on another machine for backup, then use the backup to overwrite the original file, I may have corrupted the log file?