Re: Production DBs are going to suspect mode automatically

From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 21 Apr 2007 08:51:25 -0500

The first think you should do is look at the SQL Server error log. The log should be an indication of why SQL Server marked the database suspect.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Sathiamoorthy" <someone@xxxxxxxxxxxxx> wrote in message news:%23kcjEUmgHHA.392@xxxxxxxxxxxxxxxxxxxxxxx

Dear All,
In our server,Our Production DBs are going to suspect mode automatically.
Any body help us for this issues.

Regards,

R.Sathiamoorthy

References:
- Production DBs are going to suspect mode automatically
  - From: Sathiamoorthy

Prev by Date: Re: BULK INSERT and Application role
Next by Date: Assigning database level db_owner permission to a SQL Server Login
Previous by thread: Re: Production DBs are going to suspect mode automatically
Next by thread: RE: View SQL Diagrams if user has view definition rights via domain gr
Index(es):
- Date
- Thread

Relevant Pages

Re: SQL Sever 2008 RC0 fail to install almost all services
... Check the SQL Server error log for potential causes. ... The SQL Server Error Log file, ...
(microsoft.public.sqlserver.setup)
Re: trace 1204
... you can turn on trace flag 3605 so that the deadlock ... diagnostics are written to the SQL Server error log. ...
(microsoft.public.sqlserver.programming)
Re: Unable to connect to SQLExpress Remotely - no matter what
... If there is no error in the SQL Server error log when the login fails then ... that would indicate that the connection is not getting to SQL Server. ...
(microsoft.public.sqlserver.connect)
Re: Unable to connect to SQLExpress Remotely - no matter what
... the SQL Server error log. ... An error has occurred while establishing a connection to the server. ... fact that under the default settings SQL Server does not allow remote ... connecting and are there errors put into the SQL Server error log file ...
(microsoft.public.sqlserver.connect)
Re: SQL Sever 2008 RC0 fail to install almost all services
... Brander" <ge brander microsoft> wrote in message ... Check the SQL Server error log for potential causes. ...
(microsoft.public.sqlserver.setup)