SSMS ecosystem


The content of this page is for guidance only. Red Gate reserves the right to change the rules and terms of the Ecosystem Project at any time.

What is the Red Gate Ecosystem Project?

The Red Gate Ecosystem Project (currently in beta) exists to enhance the SQL Server Management Studio experience for developers and DBAs by encouraging a tighter integration of existing SQL Server tooling to SSMS, as well as supporting the development of new functionality for the platform.

At this time the project is still very much in a beta validation stage. This means that at any time the APIs might change, and there is always the possibility that the project will be discontinued. Please email should you have any concerns or questions.

I'm a tools vendor. What's in it for me?

If you have a SQL Server tool, or are thinking of developing one, integrating it with the Red Gate Ecosystem Project provides the following benefits:

  1. Red Gate will provide APIs for easier SQL Server Management Studio integration
  2. Red Gate will use its considerable marketing reach, which includes both its user base as well as its community sites, to promote the Ecosystem and the tools within it

What do I have to do to integrate my tool into the Ecosystem Project?

  1. Implement the Shared Interface and have a minimum level of SSMS integration. If your tool is standalone, you can use our API to integrate it via a launch button or Object Explorer context menu. Further information is available in the Writing an add-in page. 
  2. At this moment Red Gate does not have the facility to transact the sale of your tool on your behalf, so unless your tool is free, your landing page should provide its own purchasing functionality.
  3. Email when your tool is ready so we can include it on the Ecosystem page listing.

How will my tool be promoted?

Red Gate doesn't guarantee a minimum level of tool promotion. However, these are the mechanisms that may be used to promote the Ecosystem and the tools within it:

  • a listing on the Ecosystem page
  • tool reviews promoted on Database Weekly newsletters
  • tool reviews posted on SQL Server Central, a community with over 1.6 million members
  • mentions on Red Gate's own customer newsletter
  • mentions on social media, such as Twitter, Facebook, LinkedIn, etc
  • promoting press releases using the above channels

Can I withdraw my tool from the Ecosystem Project?

Yes. There's no contractual obligation implied by being a part Ecosystem Project. If you feel that your tool is not benefiting from being a part of the Ecosystem, you can request it be withdrawn from the listing at any time.

Who is responsible for the quality and support of the Ecosystem tools?

The vendors are fully responsible for ensuring the quality of their respective tools, as well as the pre- and post-sales support. If issues in the tool are deemed by Red Gate to be damaging to the Ecosystem Project brand, Red Gate reserves the right to withdraw the tool until the issues are remedied.

Issues can fall under a number of categories. Some include:

  • functionality bugs
  • causing instability in SQL Server Management Studio
  • incompatibility with other Ecosystem tools
  • usability and look-and-feel issues
  • the quality of the customer support provided by the vendor is damaging the Ecosystem brand

What if Red Gate makes changes to the terms of the Ecosystem Project?

Red Gate reserves the right to make changes to the terms. This may be necessary to ensure that the necessary mechanics are in place to sustain and nurture a thriving Ecosystem.

Examples of such changes may be:

  • (breaking) changes to the API
  • deprecation of API features
  • different minimum quality standards
  • changes to the means with which tools are promoted within the Ecosystem
  • imposing a revenue cut for tools that are part of the Ecosystem

How should I link to the ecosystem project pages?

We have a few URL redirects set up so if we move or rename our pages URLs will still work. You should use:

Didn't find what you were looking for?