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 |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2005-12-13 : 07:39:34
|
Ferg writes "Our SOX auditors want traces on all production servers (Win 2000, SQL 2000, SP3) monitoring failed logins and failed object access. We don't want them to have EM on their machines. Is there anyway to view the trace output without profiler." |
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-12-13 : 09:36:01
|
You can dump the data into a table and then BCP it out... Then they can look at it in whatever they wish (MS Access, Excel, WordPad, ...)Daniel, MCP, A+SQL Server DBAwww.dallasteam.com |
 |
|
Kristen
Test
22859 Posts |
Posted - 2005-12-13 : 09:51:45
|
And then you could have a trigger that adjusted it on INSERT, in case any of your own data was a bit suspect ... Kristen |
 |
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2005-12-13 : 10:49:25
|
You can also setup a trace to load the data into a SQL Server table directly, so that you do no have to load it from a file. quote: Orginally posted by SQLServerDBA_Dan You can dump the data into a table and then BCP it out... Then they can look at it in whatever they wish (MS Access, Excel, WordPad, ...)Daniel, MCP, A+SQL Server DBAwww.dallasteam.com
CODO ERGO SUM |
 |
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2005-12-15 : 09:37:32
|
Or you could use good old fn_trace_gettable. Example select * from ::fn_trace_gettable('c:\my_trace.trc', default). You could set that up as a query directly from whatever front end they like.Jon-Like a kidney stone, this too shall pass.http://www.sqljunkies.com/weblog/outerjoin |
 |
|
|
|
|
|
|