System.Data is core part of MS..NET Framework, you really cannot remove it
with removing whole .NET framework. The question is, why do yuo want to
remove it? Are you saying that you develop your own ".NET framework" and you
want to replace MS .NET framework with yours? Probably not. If you developed
something, which is based on System.Data/MS .NET framework (that is most
.NET development do), you do not throw those your product based on away, you
nedd them in order for your product to work. If your product is developed
correctly and ready to be placed into GAC, just place it in, and have your
other .NET projects to use it, rather than directly using System.Data (if
your stuff is indeed a replacement of System.Data, but I really doudt it,
sorry.).

Hi Gilad,

It's a bad idea to replace System.Data.

Instead, create a class that wraps SqlConnection and trace the calls in
that.  You'll have to use your wrapper class instead of SqlConnection
throughout your application:

public class TracedSqlConnection : DbConnection
{
   private readonly SqlConnection connection;
   private readonly string id;

   public TracedSqlConnection(string id, string connectionString)
   {
       this.id = id;
       this.connection = new SqlConnection(connectionString);
   }

   public override void Open()
   {
       System.Diagnostics.Trace.WriteLine("Calling Open()",
           "TracedSqlConnection: " + id);

       connection.Open();

       System.Diagnostics.Trace.WriteLine("Open() called",
           "TracedSqlConnection: " + id);
   }

   // TODO: remaining method implementations here
}