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 - 2004-01-07 : 08:06:14
|
| Trackster writes "For SQL Server 2000, WinXP Pro:I have a custom App, can't access the source code & therefore can't alter the app except by working with the backend db. The app issues a select query for a particular user action. No procedures, no insert, no update, no delete - I checked with Profiler. The Select is my only "hook" to increase functionality. My method is to save results from a profile trace to a table in the db, then trigger off that table. It works, but it's round-about & not robust because it is easy to turn off the trace.I tried scripting the trace - extra question - is there a way to script it to save to a table? Profiler wouldn't script saving to a table.And is there a better way for me to accomplish this, via a trigger direct from the select query maybe?" |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2004-01-07 : 10:17:50
|
| There is no SELECT event for a Trigger..Having profiler on all the time is not a good idea...resources, the fact that someone can (and will) turn it off (because it's not a good idea)And script the trace to a file and bcp it in to a table if you want to use it...But you don't mention what you're trying to extend?What is it about a SELECT that would cause some event to "fire"Brett8-) |
 |
|
|
|
|
|