Viewing 9 posts - 1 through 9 (of 9 total)
There is enough disk space, log is ok, and everything looks fine.
But MOM still reports error.
Vera
January 26, 2006 at 7:32 am
Oops!
Sorry for this. Something went wrong with posting so it's has been posted for 4 times.
Hope you are still willing to help me.
Vera
January 26, 2006 at 6:27 am
I am so sorry.
Here is the message:
Operations Manager Critical Error Alert on ServerNAme
Severity: Critical Error
Status: New
Source: SQL Server 2000 Database
Health:MSSQLSERVER
January 26, 2006 at 6:23 am
I am so sorry.
Here is the message:
Operations Manager Critical Error Alert on ServerNAme
Severity: Critical Error
Status: New
Source: SQL Server 2000 Database
Health:MSSQLSERVER
January 26, 2006 at 6:22 am
I am so sorry.
Here is the message:
Operations Manager Critical Error Alert on ServerNAme
Severity: Critical Error
Status: New
Source: SQL Server 2000 Database
Health:MSSQLSERVER
January 26, 2006 at 6:21 am
I am so sorry.
Here is the message:
Operations Manager Critical Error Alert on ServerNAme
Severity: Critical Error
Status: New
Source: SQL Server 2000 Database
Health:MSSQLSERVER
January 26, 2006 at 6:20 am
Forgot to mention:
Restrict file growth of transaction log is not such a good idea. I think you shouldn't change this option (unrestricted tlog growth). The better solution is to maintain...
December 14, 2005 at 4:52 am
First aid:
Check the recovery model of your database. I suppose it is FULL recovery model. Do your have a lot of bulk inserts? Do you need all of them to...
December 14, 2005 at 3:41 am
Hi.
I am not an expert, but I would like to suggest you to check the combination of WITH INIT and NOSKIP while doing backup with retaindays.
INIT means that you want...
December 7, 2005 at 2:49 am
Viewing 9 posts - 1 through 9 (of 9 total)