Have you ever wanted the opportunity to ask the MSSQLTIGER team about SQL Server? Join the SQL Server Tiger team for a Twitter Chat on Monday, June 27th from 10 -11 AM PST. You can ask anything about Query Performance on SQL Server for our first Twitter chat.
All you need is a Twitter account to participate in the chat. Log on at the time above, make sure to include #AskSQLTiger in every Tweet you make, and you’ll be part of our discussion. Or, follow this link to see the #AskSQLTiger feed. Tools like TweetdDeck, HootSuite can be helpful in following along in a Twitter Chat. Members of the @mssqltiger will be moderating the discussion. Bob (@bobwardms), Pedro (@sqlpto), Parikshit (@talktosavjani), Alexey (@alexey_MSFT) and I (@banerjeeamit) will be answering your questions on Monday, June 27th.
Here are some question ideas for questions:
What tools do Microsoft Engineers use for troubleshooting Query Performance?
How does updating statistics regularly help query performance?
Do fragmented indexes affect query performance?
What are the new features available to troubleshoot Query Performance?
Which Extended Events help in troubleshooting Query Performance?
You can ask us anything about query performance. We are however unable to comment on unreleased features and future plans.
Some quick housekeeping items:
- Be nice: If you disagree, be polite. If not, you will hear us growl!
- Stay on topic
- No spamming and no self-promoting
- Always use the hashtag #AskSQLTiger in your posts to ensure that your post will show up in the conversation.
- Response to other participators: If you want to respond to a certain user, make sure to include their Twitter handle so it’s clear who you’re speaking to.
- Label your posts: If you’re asking a question please number it. For example, put “Q1:” before your question if it’s the first one that’s been asked. If you’re answering a question, put “A1:”.
- No Troubleshooting: While we would love to help you troubleshoot your query performance issues, 140 characters and a Twitter chat might not be appropriate. We have great folks from the community that can help on the #sqlhelp hashtag or have detailed discussion on the forums. And if it's a production issue of time critical nature, we recommend that you open a support incident with Microsoft so that our Customer Support and Services team can assist on appropriately.
To make sure you get the latest updates, follow our account @MSSQLTiger on Twitter.
P.S. It is safe to interact with tigers in a supervised manner during the Twitter chat and we hope you join us live on Monday, June 27th.