Another use for the Default Trace: Mapping Temporary Tables to Sessions

本文介绍了一种利用SQL Server的默认跟踪功能来确定哪些会话创建了tempdb中的临时表的方法。通过匹配trace文件中特定事件类与tempdb中的对象创建日期,可以追溯到创建这些对象的会话ID。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

The random ramblings and rantings of frazzled SQL Server DBA

Another use for the Default Trace: Mapping Temporary Tables to Sessions

Here’s another use for the information captured by the default trace.  Ever wonder what session created the tables that exist in tempdb?  Well you can find it using the default trace and the sys.objects view in tempdb.  Any time an object is created in a database, EventClass 46 (Object:Created) is captured in the trace output of the DMV.  By scanning the trace files for a matching ObjectID that was created 100 ms before or after the objects create_date with DatabaseID = 2 (tempdb) you can match the objects back to the SPID (session_id) that created the object:

DECLARE  @FileName  VARCHAR ( MAX  

SELECT  @FileName  =  SUBSTRING ( path ,  0 ,  LEN ( path )- CHARINDEX ( '/' ,  REVERSE ( path ))+ 1 ) +  '/Log.trc'  
FROM  sys.traces   
WHERE  is_default  =  1  

SELECT   
     
o.name ,   
     
o. OBJECT_ID  
     
o.create_date , 
     
gt.NTUserName  
     
gt.HostName  
     
gt.SPID  
     
gt.DatabaseName  
     
gt. TEXT Data 
FROM  sys. fn_trace_gettable (  @FileName ,  DEFAULT  )  AS  gt  
JOIN  tempdb.sys.objects  AS  o   
     
ON  gt.ObjectID  =  o. OBJECT_ID  
WHERE  gt.DatabaseID  =  2 
  
AND  gt.EventClass  =  46  -- (Object:Created Event from sys.trace_events)  
  
AND  o.create_date  >=  DATEADD ( ms , - 100 ,  gt.StartTime )   
  AND 
o.create_date  <=  DATEADD ( ms ,  100 ,  gt.StartTime )

If you’ve seen my presentation for the PASS DBA SIG (no longer a SIG but a Virtual Chapter), you will notice a difference in how the @Filename variable is being built in the above code.  Previously I used the fn_trace_getinfo function to get the filename and did a long string parse to go back four file numbers to the current start file.  This is not necessary however if you just use Log.trc as the filename since it will automatically roll forward through the existing files from this point which makes for cleaner code in my opinion.

If I have missed something and there is a better way to do this using DMV’s please post a comment and let me know.

 

 

Additional Information: from envykok

 

--Get ALL Temp Table Size

USE [Tempdb]

GO

 SELECT CAST(sysobjects.[name] AS VARCHAR) AS [TABLE_NAME],
       sysindexes.[rows] AS [NO_OF_ROWS],
       sysindexes.reserved AS [RESERVED_SPACE],
       sysindexes.used AS [USED_SPACE]
  FROM sysobjects
 INNER JOIN sysindexes
    ON sysobjects.[id] = sysindexes.[id]
 WHERE sysindexes.indid < 2
   AND sysobjects.type = 'U'

### NullPointerException in Mapping Processor: Causes and Solutions NullPointerException (NPE) is a common runtime exception in Java that occurs when an application attempts to use `null` in a case where an object is required[^1]. In the context of an internal mapping processor, this error typically arises due to improper handling of null values during the transformation or mapping of objects. #### Common Causes of NullPointerException in Mapping Processors Mapping processors often involve converting data from one format to another, such as transforming entities into DTOs (Data Transfer Objects). The following are typical causes of NPE in this scenario: 1. **Uninitialized Variables**: If a variable used in the mapping process has not been initialized before being accessed, it can lead to NPE[^2]. 2. **Null Values in Input Data**: When the input data contains null values, and these are not properly checked before processing, it results in NPE[^3]. 3. **Improper Use of Optional**: Incorrect handling of `Optional` objects can also cause NPE if the presence of a value is not validated before accessing it[^4]. #### Solution Approaches To address the NullPointerException in a mapping processor, consider the following strategies: - **Null Checks**: Implementing explicit null checks can prevent NPE. For example: ```java if (sourceObject != null && sourceObject.getField() != null) { targetObject.setField(sourceObject.getField()); } ``` This ensures that no attempt is made to access methods or properties of a null object[^5]. - **Use of Optional**: Leveraging the `Optional` class can help manage null values more effectively. Here’s an example: ```java Optional.ofNullable(sourceObject) .map(SourceObject::getField) .ifPresent(targetObject::setField); ``` The `Optional` class provides a way to avoid direct null references by encapsulating the presence or absence of a value[^6]. - **Default Values**: Providing default values for fields that might be null can mitigate NPE risks. This approach ensures that even if a field is null, a fallback value is used instead: ```java targetObject.setField(sourceObject.getField() != null ? sourceObject.getField() : "default"); ``` - **Validation Frameworks**: Utilizing validation frameworks such as Bean Validation (JSR 380) can enforce constraints on input data, reducing the likelihood of encountering null values during processing[^7]. #### Debugging Tips When debugging a NullPointerException in a mapping processor, focus on identifying the exact location where the exception occurs. Techniques include: - **Logging**: Adding detailed logs around the mapping logic to capture the state of objects at runtime. - **Unit Testing**: Writing comprehensive unit tests to simulate various scenarios, including edge cases with null inputs[^8].
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值