Comments on: SQL SERVER – Introduction to SQL Server 2008 Profiler http://blog.sqlauthority.com/2009/08/03/sql-server-introduction-to-sql-server-2008-profiler-2/ Notes of a SQL Server MVP and Database Administrator Sun, 21 Mar 2010 03:48:32 +0000 http://wordpress.com/ hourly 1 By: SUKHMEET http://blog.sqlauthority.com/2009/08/03/sql-server-introduction-to-sql-server-2008-profiler-2/#comment-56188 SUKHMEET Sat, 26 Sep 2009 12:24:13 +0000 http://blog.sqlauthority.com/?p=6230#comment-56188 thanks sir, you are doing a great job.thanks once again for your information. thanks sir,
you are doing a great job.thanks once again for your information.

]]> By: Suhas http://blog.sqlauthority.com/2009/08/03/sql-server-introduction-to-sql-server-2008-profiler-2/#comment-55700 Suhas Tue, 08 Sep 2009 10:54:27 +0000 http://blog.sqlauthority.com/?p=6230#comment-55700 Hello sir, Nice post thanks Hello sir,

Nice post thanks

]]> By: anand http://blog.sqlauthority.com/2009/08/03/sql-server-introduction-to-sql-server-2008-profiler-2/#comment-55270 anand Wed, 26 Aug 2009 19:18:07 +0000 http://blog.sqlauthority.com/?p=6230#comment-55270 In template definition, you mentioned "SQL Server 2009" Did I read it correct or it's a typo. In template definition, you mentioned “SQL Server 2009″

Did I read it correct or it’s a typo.

]]> By: Jacob Sebastian http://blog.sqlauthority.com/2009/08/03/sql-server-introduction-to-sql-server-2008-profiler-2/#comment-54510 Jacob Sebastian Thu, 06 Aug 2009 08:20:00 +0000 http://blog.sqlauthority.com/?p=6230#comment-54510 As pinal said, traces are good and bad. They are good and useful if used correctly and they can be very bad if not correctly used. I was playing with a SQL Server monitoring tool recently (to check the health of one of the servers) and the tool installed a trace silently, and gave us some trouble. I think the problem was that it installed a trace that captured ALL the events/activities and that added quite a lot of load on the server. So it is very important that when running a trace on a production server, you need to make sure that only those events that are 'necessary' are captured in your trace. As pinal said, traces are good and bad. They are good and useful if used correctly and they can be very bad if not correctly used.

I was playing with a SQL Server monitoring tool recently (to check the health of one of the servers) and the tool installed a trace silently, and gave us some trouble. I think the problem was that it installed a trace that captured ALL the events/activities and that added quite a lot of load on the server.

So it is very important that when running a trace on a production server, you need to make sure that only those events that are ‘necessary’ are captured in your trace.

]]> By: Krunal http://blog.sqlauthority.com/2009/08/03/sql-server-introduction-to-sql-server-2008-profiler-2/#comment-54390 Krunal Mon, 03 Aug 2009 13:42:16 +0000 http://blog.sqlauthority.com/?p=6230#comment-54390 Really Really Nice post..... Really Really Nice post…..

]]> By: Ramdas http://blog.sqlauthority.com/2009/08/03/sql-server-introduction-to-sql-server-2008-profiler-2/#comment-54389 Ramdas Mon, 03 Aug 2009 13:40:48 +0000 http://blog.sqlauthority.com/?p=6230#comment-54389 Hi Pinal, Good one, I have found SQL Profiler to be very useful, used it in OLTP,SSRS environments a lot. I was recently introduced to SQL Server Profiler events which were specific to Analysis services, apparently these can be used to figure out How cube caches data and also check out performance of the cube. In the initial drop down for server type one would choose analysis services. Hi Pinal,
Good one, I have found SQL Profiler to be very useful, used it in OLTP,SSRS environments a lot. I was recently introduced to SQL Server Profiler events which were specific to Analysis services, apparently these can be used to figure out How cube caches data and also check out performance of the cube. In the initial drop down for server type one would choose analysis services.

]]>