Archive for May, 2013

Know more about following in Microsoft Report Server using

  • System information, including operating system, version, number of processors, and memory.
  • Reporting Services component and version information.
  • Events logged the Application log.
  • Exceptions generated by the report server.
  • Low resource warnings logged by a report server.
  • Inbound SOAP envelopes and summarized outbound SOAP envelopes.
  • HTTP header, stack trace, and debug trace information
Use the Report Log Viewer tool to get more information on the reporting service trace log and reporting service execution log …
Run the executable ReportViewer.exe from C:\Program Files (x86)\Microsoft\Reporting Services folder and select the log files location (C:\Program Files\Microsoft SQL Server\MSRS11.<instance name>\Reporting Services\LogFiles) and select one of following 3 views to analyze the data.
Trace Log Histogram – Shows the histogram view of event and number of times it occured. This view should help us pinpoint bottleneck areas if we look for spikes in certain events
Raw – Provides more information on bottleneck events because it has the “Time” component built-in
Threads – Find resource contention thru threads to get to know where the waits occur

— Following query is helpful to find all db objects that used to set value for the given columnname of a table …

select distinct name,o.type
from syscomments c
join sysobjects o on =
where TEXT like ‘%TableName%’ and TEXT like ‘%Set%ColumnName%’
order by name

— Finding table dependencies using SP

sp_depends ‘<Table Name>’


<meta http-equiv=”X-UA-Compatible” content=”IE=Edge” />

<clear />
<add name=”X-UA-Compatible” value=”IE=Edge” />