Home Forums SQL Server 2005 Administering "Database 'COMMON' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details." RE: "Database 'COMMON' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details."

  • April 21, 2009 at 7:56 am

    #981445

    when I checked into the log files i got some message like..

    2009-04-21 14:28:24.96 spid27s Starting up database 'DUMMY'.

    2009-04-21 14:28:26.84 spid4s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.

    2009-04-21 14:28:37.32 spid9s Starting up database 'tempdb'.

    2009-04-21 14:28:38.59 spid4s Recovery is complete. This is an informational message only. No user action is required.

    2009-04-21 14:28:38.59 spid12s The Service Broker protocol transport is disabled or not configured.

    2009-04-21 14:28:38.59 spid12s The Database Mirroring protocol transport is disabled or not configured.

    2009-04-21 14:28:38.76 spid12s Service Broker manager has started.

    2009-04-21 14:28:45.76 spid51 Using 'xpsqlbot.dll' version '2005.90.3042' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.

    2009-04-21 14:28:45.98 spid51 Using 'xpstar90.dll' version '2005.90.3042' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.

    2009-04-21 14:28:46.12 spid51 Using 'xplog70.dll' version '2005.90.3042' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.

    2009-04-21 14:41:04.84 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 1712, committed (KB): 74716, memory utilization: 2%.

    2009-04-21 14:46:36.79 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 331 seconds. Working set (KB): 16892, committed (KB): 39140, memory utilization: 43%.

    2009-04-21 14:51:08.57 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 603 seconds. Working set (KB): 15104, committed (KB): 36524, memory utilization: 41%.

    2009-04-21 14:56:35.23 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 930 seconds. Working set (KB): 17212, committed (KB): 38988, memory utilization: 44%.

    2009-04-21 15:01:07.17 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1202 seconds. Working set (KB): 15148, committed (KB): 36524, memory utilization: 41%.

    2009-04-21 15:06:33.90 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1529 seconds. Working set (KB): 17200, committed (KB): 38708, memory utilization: 44%.

    2009-04-21 15:11:05.84 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1801 seconds. Working set (KB): 15164, committed (KB): 36516, memory utilization: 41%.

    2009-04-21 15:42:02.53 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 3657 seconds. Working set (KB): 17276, committed (KB): 38876, memory utilization: 44%.

    2009-04-21 16:41:54.65 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 7249 seconds. Working set (KB): 8276, committed (KB): 38900, memory utilization: 21%.

    2009-04-21 18:41:38.96 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 14434 seconds. Working set (KB): 10540, committed (KB): 38756, memory utilization: 27%.