How to trace trigger execution in SQL Profiler?

When I try to trace some SQL statement executions inside a Trigger by using 2005 SQL Profiler, I found even the trigger is fired, there's no any trace about it in SQL Profiler. How can I trace trigger execution in 2005 SQL Profiler?Hi,

have a look here: http://groups.google.de/group/microsoft.public.sqlserver.server/browse_frm/thread/c87621996c73012b

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

how to trace table update?

Hi,
I know using sql profiler can trace table update, can
someone teach me how to do so? Thanks
regards,
florenceYou need to start SQL Profiler and then create a connection to your server.
Then, create a new trace and accept all defaults. This should help you trace
the statements that go to SQL Server. If you need to do more esoteric
things, refer to the BOL for more information.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"florence" <florence@.visualsolutions.com.my> wrote in message
news:0d0701c3a918$23033d70$a301280a@.phx.gbl...
> Hi,
> I know using sql profiler can trace table update, can
> someone teach me how to do so? Thanks
> regards,
> florence

How to trace sp_addlogin

Dear all,
I have been trying to use SQL Profiler to trace login
creation. Can someone tell me how do I get the login names
that were created? Trace did not display the detail info
of sp_addlogin.
Thanks,
Joe
You can't get it from Profiler. If it sees password in the text it won't
display it.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Joe" <anonymous@.discussions.microsoft.com> wrote in message
news:c61d01c47a41$709fcbc0$a501280a@.phx.gbl...
> Dear all,
> I have been trying to use SQL Profiler to trace login
> creation. Can someone tell me how do I get the login names
> that were created? Trace did not display the detail info
> of sp_addlogin.
> Thanks,
> Joe
|||Other than SQL profiler, is there any work around? I only
want to prove the new login creation.
Thanks in advance
>--Original Message--
>You can't get it from Profiler. If it sees password in
the text it won't
>display it.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>http://www.sqldbatips.com
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Joe" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:c61d01c47a41$709fcbc0$a501280a@.phx.gbl...
names
>
>.
>
|||Execute sp_helplogins or query the master..syslogins table.
-Sue
On Thu, 5 Aug 2004 06:24:29 -0700, "Joe"
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Other than SQL profiler, is there any work around? I only
>want to prove the new login creation.
>Thanks in advance
>the text it won't
>message
>names
|||Not poossible with the current set of tools.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Joe" <anonymous@.discussions.microsoft.com> wrote in message
news:c61d01c47a41$709fcbc0$a501280a@.phx.gbl...
> Dear all,
> I have been trying to use SQL Profiler to trace login
> creation. Can someone tell me how do I get the login names
> that were created? Trace did not display the detail info
> of sp_addlogin.
> Thanks,
> Joe
|||Try using sp_trace_setevent and use event number 104 Audit Add/Drop Login
"Occurs when a SQL Server Login is added or removed; for sp_addlogin and
sp_droplogin. Also check out Microsoft article "SQL Server 2000 Auditing".
It details how to use Profiler to audit SQL Server.
Thanks,
Val
"Joe" <anonymous@.discussions.microsoft.com> wrote in message
news:c61d01c47a41$709fcbc0$a501280a@.phx.gbl...
> Dear all,
> I have been trying to use SQL Profiler to trace login
> creation. Can someone tell me how do I get the login names
> that were created? Trace did not display the detail info
> of sp_addlogin.
> Thanks,
> Joe

How to stop a trace

Hi there,
I have a fairly simple question. How do you stop a trace in
SQL Profiler (2000 on XP)? When you click the stop button, the toolbar
changes and looks as though the trace has stopped but events are still being
added to the list, and when you try and exit the application, you get a
message about the trace still running. If you try to exit the application
hangs.
Waldy wrote:
> Hi there,
> I have a fairly simple question. How do you stop a
> trace in SQL Profiler (2000 on XP)? When you click the stop button,
> the toolbar changes and looks as though the trace has stopped but
> events are still being added to the list, and when you try and exit
> the application, you get a message about the trace still running. If
> you try to exit the application hangs.
You'll should wait until all events are processed. Maybe you have no
filter or a filter that is not very selective and thus get a large amount
of events. So it may take some time from pressing the button until all
events until then are processed (i.e. displayed).
Kind regards
robert
|||"Robert Klemme" <bob.news@.gmx.net> wrote in message
news:%232FhgwHtFHA.3864@.TK2MSFTNGP12.phx.gbl...
> You'll should wait until all events are processed. Maybe you have no
> filter or a filter that is not very selective and thus get a large amount
> of events.
I am only tracing one event on one database. How many hours do you suggest
I wait?
|||Waldy wrote:
> "Robert Klemme" <bob.news@.gmx.net> wrote in message
> news:%232FhgwHtFHA.3864@.TK2MSFTNGP12.phx.gbl...
> I am only tracing one event on one database. How many hours do you
> suggest I wait?
Dunno. Are you sure that the single event doesn't produce a lot of
entries? Otherwise I'm at a loss here, too. Sounds strange.
robert
|||Waldy wrote:
> Hi there,
> I have a fairly simple question. How do you stop a
> trace in SQL Profiler (2000 on XP)? When you click the stop button,
> the toolbar changes and looks as though the trace has stopped but
> events are still being added to the list, and when you try and exit
> the application, you get a message about the trace still running. If
> you try to exit the application hangs.
This can sometimes happen when using Profiler on a very busy server that
produces a lot of rowset information. Is your server under high load?
What event are you capturing and how much information is being returned
(you can see a rowcount in the status bar of the Profiler client).
In general, if you experience this problem, or are looking for a more
robust tracing method, you should use server-side tracing. A server-side
trace likely won't exhibit these problems. You can have Profiler script
the t-sql necessary to start the trace from the File - Script Trace menu
option. You need to roll your own code to stop the trace. You can open
the trace file directly in Profiler once the trace is stopped.
David Gugick
Quest Software
www.imceda.com
www.quest.com