Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
vuacorona
Starting Member
8 Posts |
 Posted - 2011-09-15 : 17:23:25
|
| Hello ALL:I am running SQL Server Profiler and often received error "Failed to read trace data". Everytime it raise error and stop, then I have to re-run the profiler again.Server: Windows 2008SQL Server 2008 enterpriseSQL Collation: Latin1_General_BIN (case sensitive)Please advise how to fix this problem.Thanks in advance.vuacorona |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
vuacorona
Starting Member
8 Posts |
Posted - 2011-09-15 : 17:31:44
|
Oh NO.... I am not running the trace on the database server.I am running the profiler from a client computer and automatically save to a trace file on local computer.quote:
Originally posted by tkizer
You are adding a load to your system due to profiler, and probably causing it too slow down so much that it fails. Are you tracing to a file and on a separate machine? Have you considered instead using a server-side trace?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog
|
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
vuacorona
Starting Member
8 Posts |
Posted - 2011-09-15 : 17:49:42
|
| I checked the log and all it said"SQL Trace stopped. Trace ID = '2'. Login name = 'sa'.Checked in the app log and found nothing. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
vuacorona
Starting Member
8 Posts |
Posted - 2011-09-15 : 18:40:49
|
| Thanks Tara for all your promptly replies.My last option is open the case with Microsoft, and I know they will said "you need to apply SP1 to SQL Server 2008". |
|
|
|
|
|
|
Failed to read trace data.