Uploaded October 2012 | Updated September 2026, 2 weeks ago
Subscribe to our channel here for notifications on new video trainings. For more videos on technology, visit our website at http://www.techytube.com.
By jayanth.kurup@techytube, for more from this author visit:
techytube.com/author/jayanth.kurup
In this video we explore how to create a server side trace using the inbuilt stored procedures available within MS SQL Server. We explore how to make this job easy by creating a trace template using the profiler tool and then implementing this within SQL Server. We will also explore how to get the details on which traces are running on a server as well as how to query data from within a trace file. A server side trace is a great tool for DBAs who do not want to implement profiler because of the huge resource requirements it has on the network especially when collecting large volumes of data. Stored procedures give a more fine grained control over when the trace starts and stops especially when scheduled via SQL Server agent. These and many other advantages make server side trace the preferred option for most DBAs.
Subscribe to our channel here for notifications on new video trainings. For more videos on technology, visit our website at http://www.techytube.com.
By jayanth.kurup@techytube, for more from this author visit:
techytube.com/author/jayanth.kurup
In this video we explore how to create a server side trace using the inbuilt stored procedures available within MS SQL Server. We explore how to make this job easy by creating a trace template using the profiler tool and then implementing this within SQL Server. We will also explore how to get the details on which traces are running on a server as well as how to query data from within a trace file. A server side trace is a great tool for DBAs who do not want to implement profiler because of the huge resource requirements it has on the network especially when collecting large volumes of data. Stored procedures give a more fine grained control over when the trace starts and stops especially when scheduled via SQL Server agent. These and many other advantages make server side trace the preferred option for most DBAs.
