Community and support

Ask in the open. Get help from the people who wrote it.

Questions and ideas go in GitHub Discussions, where answers help the next person too. Retainer customers get direct help from the TTS team through our help desk.

EVERYONE

GitHub Discussions

Ask how to do something, share a check you've written, or suggest a feature. Search first: your question may already be answered.

Open Discussions
EVERYONE

GitHub Issues

Found a bug? Open an issue with your SQL Server version, what you expected, what happened, and any error text.

Report a bug
PAID SUPPORT

Help desk

Support retainer customers open and follow requests at our help desk.

Open the help desk

Getting a good answer

Help people help you.

SQLBeat runs in very different environments. A few details up front save a round of questions.

  • VersionsThe SQL Server version and edition of the SQLBeat server, and of the server being monitored.
  • What you ranThe procedure or job involved, and the parameters.
  • What happenedThe full error text, or the rows you got and what you expected.
  • Leave outPasswords, server names you'd rather not share, and customer data. Discussions are public.

Contributing

Improvements welcome.

If you've fixed a bug or written a check others would use, open a pull request. Small, focused changes with a note on how you tested them are easiest to review.

By contributing, you agree your changes can be distributed under SQLBeat's license.

Talk to us directly