to know more about sql server in bulid default trace
-
Hi after installation of sql server there is inbulid trace which is enabled automatically.Is it very helpfull.
or should i disabled it get another trace that are avaliable on net.
second this trace file are created in at default location in log folder where error log is stored.
Is there any way to move this trace file to other location.i donot want to move error log file
Thanks and regards
Anoop Pandey
-
I would not suggest turning it off, no. You can add additional traces if you need them, but the default trace captures a basic set of information about what's happening on your system. Here's a great article on it at Simple Talk[/url].
To my knowledge you can't change the location of it. It's going where the error logs go.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore RooseveltAuthor of:
SQL Server Execution Plans
SQL Server Query Performance Tuning -
Grant Fritchey (10/5/2013)
I would not suggest turning it off, no. You can add additional traces if you need them, but the default trace captures a basic set of information about what's happening on your system. Here's a great article on it at Simple Talk[/url].To my knowledge you can't change the location of it. It's going where the error logs go.
Hi Grant thanks for your reply
suppose i start another custom made trace apart from default trace will it have performance issue
-
Depends what events you put in the trace and how you configure it. Keep traces lightweight and probably not.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
What Gail said.
But, if you really want to avoid adding too much additional overhead to the system, then instead of a trace, I'd look at extended events. They're much more efficient and can return the same data as a trace.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore RooseveltAuthor of:
SQL Server Execution Plans
SQL Server Query Performance Tuning -
Grant Fritchey (10/7/2013)
What Gail said.But, if you really want to avoid adding too much additional overhead to the system, then instead of a trace, I'd look at extended events. They're much more efficient and can return the same data as a trace.
hi Grant thanks for your rely
Can u more specific about events . can u provide any links for it
Thanks
Anoop
-
Jonathan Kehayias has written the best blog series about extended events
-
Yep, Jonathan's blog and the Microsoft documentation are the way to go. Between the two you'll learn most of what you need.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore RooseveltAuthor of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply