Breaking changes in SQL Trace - not happy (mumble, mumble...)
We're upgrading our SQL Server monitoring toolset - SQLBenchmarkPro - at work at the moment so that it can monitor SQL 2000 & SQL 2005 instances concurrently. We hit a couple of snags recently which might be worth noting if you're into scripting SQL Trace.
Microsoft have changed the sp_trace_create API, so that log file names can't end in the format "_nnn" any more. This broke our monitoring tool as we "version" our log files using this naming convention when they're changed (events / columns being added / removed) via our GUI. This will require days of planning, development & testing for us to work around. )c:
I looked around Books Online documentation to see if this change was documented in any *reasonable* location (ie, in a "what's changed" section), but alas to no avail so far.
We also noticed that the Duration column's measurement unit has also changed from milliseconds to microseconds - also apparently without warning from MS. The SQL Profiler GUI still reports Duration in milliseconds (it's obviously translating whilst rendering), but SQL Trace .trc log files report microseconds.
I've no idea why these breaking changes needed to be made, let alone without any reasonable documentation.
mumble, mumble.... )c: