SQL Server Performance

Stange enteries in SQL Server management log - Anyone know what causes these?

Discussion in 'General DBA Questions' started by vdemsky, Sep 18, 2009.

  1. vdemsky New Member

    Hi all. I've noticed some unusual (or at least unusual to me) entries in my SQL Server management log. I'm running SQL Server 2000. I've been having entries similar to the following randomly throughout the day over the last 4 days. Does anyone know what process, or DBCC command, or sp_* command causes these types of entries? I'm just trying to figure out what this information means and why it has started showing up in the log.
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:08,spid74,Unknown,m_guid = 00000000-0000-0000-0000-000000000000
    09/18/2009 08:16:08,spid74,Unknown,dbi_differentialBaseGuid = b0c4e235-6015-42ec-8940-92bcc52fed1b
    09/18/2009 08:16:08,spid74,Unknown,dbi_collation = 872468488 dbi_category = 0
    09/18/2009 08:16:08,spid74,Unknown,dbi_maxLogSpaceUsed = 5346114560
    09/18/2009 08:16:08,spid74,Unknown,DBCC TRACEOFF 3604<c/> server process ID (SPID) 74.
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:08,spid74,Unknown,dbi_familyGUID = 77631639-5a08-44c8-9ea3-36b29ded3236
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 735582 m_blockOffset = 5275 m_slotId = 1
    09/18/2009 08:16:08,spid74,Unknown,m_guid = d8576258-bda4-4dd5-b902-a6f87bcaf963
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,dbi_nextseqnum = 1900-01-01 00:00:00.000
    09/18/2009 08:16:08,spid74,Unknown,dbi_crdate = 2005-01-24 13:37:14.020 dbi_filegeneration = 0
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 736073 m_blockOffset = 15243 m_slotId = 4
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 735582 m_blockOffset = 5205 m_slotId = 4
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,DBCC TRACEON 3604<c/> server process ID (SPID) 74.
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,
    09/18/2009 08:16:08,spid74,Unknown,dbi_dbid = 30 dbi_status = 24 dbi_nextid = 2026867429
    09/18/2009 08:16:08,spid74,Unknown,dbi_dbname = ReportData dbi_maxDbTimestamp = 30079100
    09/18/2009 08:16:08,spid74,Unknown,dbi_version = 539 dbi_createVersion = 539 dbi_ESVersion = 0
    09/18/2009 08:16:03,spid74,Unknown,dbi_differentialBaseGuid = 10771943-85c5-45d9-abdb-cfdabf979de9
    09/18/2009 08:16:03,spid74,Unknown,dbi_collation = 872468488 dbi_category = 0
    09/18/2009 08:16:03,spid74,Unknown,dbi_maxLogSpaceUsed = 115184128
    09/18/2009 08:16:03,spid74,Unknown,DBCC TRACEOFF 3604<c/> server process ID (SPID) 74.
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:03,spid74,Unknown,m_guid = 00000000-0000-0000-0000-000000000000
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:03,spid74,Unknown,dbi_familyGUID = bbb30fce-488b-49d5-b6aa-ac588c650e18
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 6776 m_blockOffset = 439 m_slotId = 1
    09/18/2009 08:16:03,spid74,Unknown,m_guid = 750c97b9-7038-482b-9b93-30914d0fc79a
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 6776 m_blockOffset = 437 m_slotId = 2
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 6776 m_blockOffset = 437 m_slotId = 2
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,m_fSeqNo = 0 m_blockOffset = 0 m_slotId = 0
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,dbi_nextseqnum = 1900-01-01 00:00:00.000
    09/18/2009 08:16:03,spid74,Unknown,dbi_crdate = 1900-01-01 00:00:00.000 dbi_filegeneration = 0
    09/18/2009 08:16:03,spid74,Unknown,DBCC TRACEON 3604<c/> server process ID (SPID) 74.
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,
    09/18/2009 08:16:03,spid74,Unknown,dbi_dbid = 1 dbi_status = 24 dbi_nextid = 1769109393
    09/18/2009 08:16:03,spid74,Unknown,dbi_dbname = master dbi_maxDbTimestamp = 32400
    09/18/2009 08:16:03,spid74,Unknown,dbi_version = 539 dbi_createVersion = 539 dbi_ESVersion = 0
  2. ghemant Moderator

    Welcome to the Forums!
    Your server has trace on when server services starts or you do have a job that continuously monitoring servers using automated trace?
  3. vdemsky New Member

    Hmm. Looks like the server had flags T1204 and T3605 for service startup. My understanding is that 1204 is for deadlocks and 3605 sends output to the error log. My guess is that these were configured by someone trying to trace deadlocks and print the info back out to the error log. Still, seems odd to me as the log information doesn't look like what I'd expect from a deadlock.
  4. satya Moderator

Share This Page