June 28, 2010 at 8:10 am
My HeartFelt Thanks to everyone.
I learnt a number of new things (server trace, Transaction, statements etc)..
Now I am clear that i dont need transactions, i need the number of calls made to a DB... got some clarity... many of my doubts cleared...
Thanks for everyone.
June 30, 2010 at 6:27 am
Is the default trace (which is in Log folder) also available in SQL 2000?
If so, then what is the equivalent of fn_trace_getinfo?
June 30, 2010 at 7:13 am
balasach82 (6/30/2010)
Is the default trace (which is in Log folder) also available in SQL 2000?
No.
If so, then what is the equivalent of fn_trace_getinfo?
fn_trace_getinfo works on SQL 2000, for traces you create yourself. You just have to prefix with ::
SELECT * FROM ::fn_trace_getinfo(0)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 30, 2010 at 7:15 am
balasach82 (6/30/2010)
Is the default trace (which is in Log folder) also available in SQL 2000?If so, then what is the equivalent of fn_trace_getinfo?
You could get a much wider audience if you asked this as a new question in the forum. The only people who will see this right now are those who are subscribed to the original question.
There is a similar function called the black box trace in 2000, but it's not turned on by default and fn_trace_getinfo is the same. This isn't used only for the default trace. It's used for any trace file.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 1, 2010 at 3:45 am
Ok, will start as a new thread.
am insering the trace records into a table. The problem is there is nothing in the TextData field other than those run from the server itself. It has not captured any query from the front end which we are using.. any idea why?
July 1, 2010 at 6:00 am
balasach82 (7/1/2010)
Ok, will start as a new thread.am insering the trace records into a table. The problem is there is nothing in the TextData field other than those run from the server itself. It has not captured any query from the front end which we are using.. any idea why?
Not without knowing a lot more about how your trace events are set up... unless you mean the default trace. Then, it's only meant to capture certain server changes and DDL changes, not DML from the client.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 1, 2010 at 6:47 am
yes, its default trace. But even "select" is not being captured( front end mostly only retrives and less updates)
July 1, 2010 at 6:57 am
balasach82 (7/1/2010)
yes, its default trace. But even "select" is not being captured( front end mostly only retrives and less updates)
SELECTs won't be captured in the default trace. The default trace is a light-weight trace with a very limited set of events. Mostly DDL and some security events.
If you want to trace selects, create your own trace and run it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2010 at 7:10 am
In that case, which is the best trace template (standard,TSQL etc) to capture all (or those which can be captured) queries.
July 1, 2010 at 7:14 am
Why don't you start a new thread and ask that?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2010 at 7:33 am
yes done that
😀
Viewing 11 posts - 31 through 40 (of 40 total)
You must be logged in to reply to this topic. Login to reply