﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Database Design / Design Ideas and Questions  / Server-Side Trace in CLR Stored Procedure / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sun, 19 May 2013 16:35:15 GMT</lastBuildDate><ttl>20</ttl><item><title>Server-Side Trace in CLR Stored Procedure</title><link>http://www.sqlservercentral.com/Forums/Topic989139-373-1.aspx</link><description>For application debugging purpose, we are designing for a trace feature to capture all application related SQL batches and debug messages on a SQL Server Instance.  Exporting the trace is also required.We run SQL batches and write the debug messages all within CLR Stored Procedures.We are considering to- Write code to insert trace records into database table.- Use SQL Trace T-SQL.Which do you think is usual practice and better? Or could you see any another approach?Thank you.</description><pubDate>Mon, 20 Sep 2010 00:13:53 GMT</pubDate><dc:creator>cwfongwork</dc:creator></item></channel></rss>