Re: fn_trace_gettable threatening my sanity
From: Paul Connelly (connelly_at_darc.org)
Date: 03/14/04
- Next message: Teo Chee Yang: "Impact of migration on Windows authenticated SQL user account"
- Previous message: John Bell: "Re: Impact of AD Migration on Windows authenticated SQL user account"
- In reply to: Paul Connelly: "fn_trace_gettable threatening my sanity"
- Next in thread: Jasper Smith: "Re: fn_trace_gettable threatening my sanity"
- Reply: Jasper Smith: "Re: fn_trace_gettable threatening my sanity"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 14 Mar 2004 11:52:30 -0500
Just to follow up in case anyone else runs into this, the apparent
solution is so ridiculous as to be unbelievable: my stored procedure
was retrieving the trace file name from a table where it was inserted
by the procedure that created the trace. The file name stored was
something like 'D:\Trace\Trace1.TRC', with the file type added by the
procedure (since you're not supposed to include the file type when
specifying the file on the trace create). When the file type was
changed to lowercase as in 'D:\Trace\Trace1.trc', everything worked.
You could alternate the two fn_trace_gettable selects, one with
uppercase and one with lowercase to see the problem behavior and
desired behavior quite readily and repeatably.
Is there some kind of case sensitive file system thing going on in XP
2003, or is this just a bizarre SQL bug?
- thanks,
csm
- Next message: Teo Chee Yang: "Impact of migration on Windows authenticated SQL user account"
- Previous message: John Bell: "Re: Impact of AD Migration on Windows authenticated SQL user account"
- In reply to: Paul Connelly: "fn_trace_gettable threatening my sanity"
- Next in thread: Jasper Smith: "Re: fn_trace_gettable threatening my sanity"
- Reply: Jasper Smith: "Re: fn_trace_gettable threatening my sanity"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
