January 12, 2017 at 10:31 am
Hi all
I'm trying to run a trace on my production environment that will allow me to replay the trace against a replica of the server using the ostress functionality of RML Utilites. The script provided with RML to create the trace captures data from all databases on the server. I'd like to restrict this to a single database to limit the impact of the trace but when I try adding in a database filter using sp_trace_setfilter it is ignored.
Has anyone else come across this issue?
Thanks
Mike
January 13, 2017 at 7:45 am
Just modify the capture script to include a filter for the database. You can modify it in that fashion.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 13, 2017 at 8:00 am
Grant Fritchey - Friday, January 13, 2017 7:45 AMJust modify the capture script to include a filter for the database. You can modify it in that fashion.
Thanks Grant, just had another look at the sp_trace_setfilter parameters. There were a couple of filters and I had the @logical_operator set to 1 (OR) instead of 0 (AND). It's working now!
cheers
Mike
January 13, 2017 at 8:04 am
SilentMike - Friday, January 13, 2017 8:00 AMGrant Fritchey - Friday, January 13, 2017 7:45 AMJust modify the capture script to include a filter for the database. You can modify it in that fashion.Thanks Grant, just had another look at the sp_trace_setfilter parameters. There were a couple of filters and I had the @logical_operator set to 1 (OR) instead of 0 (AND). It's working now!
cheers
Mike
Excellent. Good to know.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply