Re: Getting Recent Search Terms
From: Hilary Cotter (hilaryk_at_att.net)
Date: 07/24/04
- Previous message: John Kane: "Re: Getting Recent Search Terms"
- In reply to: John Kane: "Re: Getting Recent Search Terms"
- Next in thread: John Kane: "Re: Getting Recent Search Terms"
- Reply: John Kane: "Re: Getting Recent Search Terms"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 24 Jul 2004 11:26:39 -0400
Strange, I can't get your trace to work. By chance are you filtering on an
application with a name like contains or CONTAINS? ;)
-- Hilary Cotter Looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html "John Kane" <jt-kane@comcast.net> wrote in message news:u1D1KqYcEHA.1000@TK2MSFTNGP12.phx.gbl... > Hilary, > I only said that this can be done using SQL Profiler vs. "there is no way" > to do this... I didn't say that I would recommend this method over using the > query log approach or visa versa, nor did I say that I would recommend using > the SQL Profiler GUI in production environments. In fact, I agree that using > the SQL Profiler GUI tool to monitor production environment can adversely > affect production performance and that is why I provided the server-side > script. This script or any other profiler server-side script can be executed > is such a way (say, only for 4 minutes periods, executed randomly over a > specified time period, approx. 1 hr.) that will have minimum impact on a > production SQL Server environment. > > Actually, I've run SQL Profiler server-side traces at very large customer > (>1TB databases) sites as well as at smaller customer sites with minimal > impact. Additionally, the current SQL Server Magazine has a very good > article entitled "9 Steps to an Automated Trace" at > http://www.winnetmag.com/SQLServer/Article/ArticleID/43014/43014.html that > almost exactly describes what I've done at large customer sites and I would > recommend using scheduled server-side Profiler traces to get "all the recent > search terms passed through Full text search" over using the SQL Profiler > GUI for large/active production sites. > > Finally, I did ask PShaw to provide more details on what he is looking for, > as there are viable solutions to this issue, and if we had more info on what > he is specifically looking for we could provide more and better solutions. > > Regards, > John > > > > > "Hilary Cotter" <hilaryk@att.net> wrote in message > news:OQze#UYcEHA.2408@tk2msftngp13.phx.gbl... > > yes this is a possibility, but in my tests running profiler in a > production > > environment causes a 10 to 30% performance hit which will exacerbate > locking > > to a point where it really is unusable. > > > > Your experience may vary, but my experience is that it is unacceptable. > > > > "John Kane" <jt-kane@comcast.net> wrote in message > > news:%23oVoFIUcEHA.644@tk2msftngp13.phx.gbl... > > > Hilary, > > > Actually, there is a way to do this via SQL Profiler, either > interactively > > > using the SQL Profiler GUI tool or via server-side tracing, for example: > > > > > > -- Filename: FTS_Trace.sql > > > -- Modified: 4:30 PM 2/19/2003 > > > declare @rc int > > > declare @TraceID int > > > declare @maxfilesize bigint > > > set @maxfilesize = 5 > > > exec @rc = sp_trace_create @TraceID output, 0, N'D:\FTS_Activity_Trace', > > > @maxfilesize, NULL > > > if (@rc != 0) goto error > > > -- Set the events > > > declare @on bit > > > set @on = 1 > > > exec sp_trace_setevent @TraceID, 12, 1, @on > > > exec sp_trace_setevent @TraceID, 12, 12, @on > > > -- Set the Filters > > > declare @intfilter int > > > declare @bigintfilter bigint > > > exec sp_trace_setfilter @TraceID, 10, 0, 7, N'SQL Profiler' > > > exec sp_trace_setfilter @TraceID, 10, 1, 6, N'CONTAINS' > > > exec sp_trace_setfilter @TraceID, 10, 1, 6, N'contains' > > > -- Set the trace status to start > > > exec sp_trace_setstatus @TraceID, 1 > > > -- display trace id for future references > > > select TraceID=@TraceID > > > goto finish > > > error: > > > select ErrorCode=@rc > > > finish: > > > go > > > > > > > > > PShah, you can also setup a query log table and when you accept the > user's > > > input and then pass it to the Contains* or Freetext* query, you can log > > the > > > input to a Query log table for further review. If you provide more > details > > > on what you are looking for, I can provide more specific solutions. > > > > > > Regards, > > > John > > > > > > > > > > > > > > > > > > > > > "Hilary Cotter" <hilaryk@att.net> wrote in message > > > news:uaqRqiRcEHA.3012@tk2msftngp13.phx.gbl... > > > > no, there is no way. On most search projects I have worked on we > > > > asynchronously scrape the web logs for the search terms. > > > > > > > > "PShah" <piyush13@gmail.com> wrote in message > > > > news:fc5b927d.0407231122.495d5ee@posting.google.com... > > > > > Hi, > > > > > I dont know if this post has been repeated before. Is there a way to > > > > > get all the recent search terms passed through Full text search? > > > > > Thanks, > > > > > P > > > > > > > > > > > > > > > > > > > >
- Previous message: John Kane: "Re: Getting Recent Search Terms"
- In reply to: John Kane: "Re: Getting Recent Search Terms"
- Next in thread: John Kane: "Re: Getting Recent Search Terms"
- Reply: John Kane: "Re: Getting Recent Search Terms"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
