Be the change

My day had a wonderful start…hot yoga at 6AM with one of my favorite instructors. Homemade cinnamon rolls for breakfast.  Great progress made with some client work. Then I read the email from Tom LaRock and the post from Wendy Pastrick regarding a harassment issue at this year’s PASS Summit. My heart is heavy.

I’ve read both texts multiple times. This line from Wendy keeps sticking in my head, “I declined, telling him I was fine.”

I understand. I’ve been there. And it’s an awful place. Any person who has been harassed knows this. Whether the harassment was physical – having someone grab your ass (or part of your body) is never funny, whether it was verbal – a sly comment with a lewd look that makes you go “ew”, doesn’t matter. The emotional response that comes with it is the indicator that you are not fine, and that you need to do something.

Very often we are taught to not “rock the boat.” Pull up your boots, put it behind you, and move on. It’s as if there is shame in experiencing that discomfort, and we must wholeheartedly deny that. If we do not, when we do NOT call out the offender, we let the offense continue. That person does it to someone else, who may or may not speak up, and the cycle continues.

I applaud Wendy for realizing that she was not fine, and for reporting it. For anyone who might think she over-reacted, I’ll strongly tell you to sit down and just stop. If you have ever experienced that feeling of discomfort, where your body temperature rises and you feel embarrassed – EVEN THOUGH YOU DID NOTHING WRONG – then you have been harassed. And if shame or fear has stopped you from saying anything, then I ask you – not encourage you, but implore you – to act differently if it occurs again. Do not wrap up those feelings inside a blanket and hide in a corner. Be brave and step forward.

I believe in going to any event with someone you trust – particularly events at the PASS Summit because there are so many people and because it’s a city where you probably don’t live. That person that goes with you is your wingman. You have his/her back, he/she has yours. You never, ever leave your wingman (if that sounds familiar, yes I’m quoting Top Gun…those pilots are on to something). If what happened to Wendy happens to you, you go right to your wingman. Do not say that you are fine. Let your wingman help you figure out next steps. One of those steps is reporting the event to PASS (or the proper governing body – HR, another Board – depending on the event) because this behavior will not change unless we begin to speak out and condemn it.

I leave you with this:

Be the change you wish to see in the world.

Be the change you wish to see in the world.

It starts with each one of us. Wendy has taken that path. In the unfortunate event that this happens to you, I hope you will follow.


With Thanksgiving just around the corner, I wanted to write about the appreciation I have for some colleagues I’ve had throughout the years, as well as several that I have now.  We often take time at the end of November to think about the things for which we are thankful.  And while that’s a very good thing, my goal this year is to take it one step further and make sure I tell the people in my life that I am grateful for them, and why.

This week at our Immersion Event, I went running on Wednesday morning with a few attendees. One of them mentioned that he had three daughters, and wondered whether it was worth encouraging them to go into IT as he noticed that in the Immersion Event classes the ratio of women to men was pretty low. He suggested that perhaps IT wasn’t a great place for women. I immediately said that I would absolutely recommend it. There may not be a lot of women in IT, but that doesn’t mean that it’s not a good place for them and won’t continue to be.  And things are always changing.  Getting women into IT, and retaining them, is a continual conversation we have, particularly in the SQL Server community.  Perhaps I’m unique, but I don’t need to work with a large percentage of women or majority of women, to feel comfortable with my team. Perhaps that’s because I’ve never encountered some of the issues that I’ve heard from other women in technology.  The issues where a male colleagues was not supportive, perhaps purposely kept a female colleague out of the loop, was very negative, or maybe even avoided or ignored female teammates entirely.  I don’t know if I’ve been lucky, or if, when I’ve encountered those men, didn’t take it personally, figured that person was just a jerk, and just figured out how to work through it.  There are jerks everywhere – within IT and out of it – and those jerks can be men or women.

I have been fortunate to have supportive individuals, both male and female, in every job I’ve ever had, in both leadership and peer roles.  Maybe I’m unique, maybe not. But I’d like to take a minute to thank the individuals who supported me, and who continue support and stand up for me and for other women in IT, and in their lives. To those of you who have daughters…my unsolicited advice is to absolutely encourage them to go into IT if that is something in which they are interested. And I would encourage fathers and mothers to reach out to women and men in the field already to ask for guidance and mentorship. Most people are happy to provide their experience and any insight they have, you just need to ask.

I won’t list all of the colleagues to whom I am grateful, there are just so many and I’m afraid I might miss someone.  But if I’ve ever looked at you and said “thank you”, or given you a handshake or a hug with a “thank you”, or sent you an email or tweet with those words, or mentioned you in a post here or a post on Facebook, then YOU are one of those people who I appreciate, who I value, and for whom I am grateful to have in my circle.  Thank you, and Happy Thanksgiving.

Filtering Events in Trace/Profiler and Extended Events

It seems very wrong to write a post that talks about Trace, after all I’ve done to advocate that everyone start using Extended Events (XE). However, I know there are a lot of you who still use Trace because you’re running SQL Server 2008R2 and earlier, so you all get a free pass. Until you upgrade. If you’re running SQL Server 2012 or higher, I strongly recommend that you use XE. But that’s the not the main point of this post. What I really want to do is step through filtering a .trc or .xel file to remove selected events.


Now, if you’ve worked with Trace for a long time, you may be wondering why you would ever filter events because, let’s be honest, you might not know you can do that (I didn’t for ages).  You can! The Profiler UI isn’t where you typically perform data analysis, but one reason you might filter out events is if you’re using Distributed Replay and you need to remove events to avoid generating errors during the reply. To do this, open the .trc file in the Profiler UI, then select File | Properties… Within the Trace File Properties window, go to the Events Selection tab, then select Column Filters… Within the Edit Filter window, you can chose a column (or multiple columns) on which to filter your data. If I want to remove all events before a specific time, I would edit the EndTime:

EndTime filter in Trace

EndTime filter in Trace

This removes all events before 11:31PM on November 12, 2015. After you have removed the events, you can save the remaining data as a new .trc file through File | Save As | Trace File…

Extended Events

Filtering events from an Extended Events file is even easier. Open the .xel file within Management Studio, then select Extended Events | Filters (you can also select the Filters icon in the Extended Events toolbar). Within the Filters window, you can choose to filter on time, and/or any of the other fields captured for the events:

Date and logical_reads filter in Extended Events

Date and logical_reads filter in Extended Events

Once you select Apply, all events before 11:31PM will be removed, as well as those with less than 1000 logical_reads. The remaining events can again be saved to a new file (Extended Events | Export to | XEL File…), or you can just run analysis against the filtered data. You can remove the filter at any time by going back to the Filters window and selecting Clear All.


Hopefully this helps if you ever need to remove events from a .trc or .xel file.  Note that I always save the filtered data as a new file – I prefer to keep the original just in case I need all the events for some reason.