Re: Trace To Table Error MSG 568

From: David Gugick (davidg-nospam_at_imceda.com)
Date: 01/08/05 

Date: Sat, 8 Jan 2005 02:30:08 -0500

Joseph wrote:
> David,
>
> I get the same error for the two scenarios you described. I don't get
> the error if I limit my select to top 10000 but it bombs out if I go
> to 20000 rows. I tried stopping the trace but that did not help.
> Thanks,
> Joseph
>

It sounds like you are using rollover files. You didn't answer my
question if you are using Profiler for this. If you are, I believe
Profiler created rollover files are not compatible with
fn_trace_gettable. You'll need to use a server-side trace (manually run
from T-SQL code). The reason your TOP 10,000 works is because you are
limiting the query to rows that are in the first rollover file. You just
can't read past the rollover point from a Profiler created file. I don't
really know why the bug is still there and I haven't seen a fix in the
upcoming SP4. In any case, if you didn't know, running a trace to a flat
file from the Profiler client actually creates and runs two separate
traces on the server, which is just more load than the server needs.
You'll have better control using a server-side trace. You can have
Profiler script one for you using the Script option on the file menu. 

-- 
David Gugick
Imceda Software
www.imceda.com

Relevant Pages
Loading