Server side trace to database
I highly doubt no one is interested! :-)

Here's my link collection that I used to get into the topic:


http://www.toadworld.com/platforms/sql-server/w/wiki/10400.the-server-side-trace-what-why-and-how.aspx
http://www.mssqltips.com/sqlservertip/1035/sql-server-performance-statistics-using-a-server-side-trace/
http://consultingblogs.emc.com/jamesrowlandjones/archive/2009/05/28/the-curious-case-of-the-dubious-deadlock-and-the-not-so-logical-lock.aspx


Hope those help you as well !

Update:

Ok, to clear things up:


in order to create a server-side trace, you need a trace definition script 
to create that trace definition script, the easiest approach is to use SQL Server Profiler to define what you want to trace - which events, what properties
you then use SQL Server Profiler to create that server-side trace definition script for you (doing it manually, from scratch, is a major hassle)
but then, to execute - you don't use SQL Server Profiler (that's putting too much load on your server), but you just create and run the trace on the SQL Server