Announcing Hasura 2.0.0-alpha.11
Tags: releases, graphqlengine, sqlserver
Published: 2021-05-27 08:48:13

---
title: Announcing Hasura 2.0.0-alpha.11
published: true
date: 2021-05-25 15:37:39 UTC
tags: Releases,GraphQLEngine,SQLServer
canonical_url: https://hasura.io/blog/announcing-hasura-2-0-0-alpha-11/
---

![Announcing Hasura 2.0.0-alpha.11](https://hasura.io/blog/content/images/2021/05/2.0.0-alpha.11.png)

We are super excited to announce the final alpha in the 2.0 series with 2.0 alpha 11.

While ‘alpha’ in name, it is not alpha in quality. However, we do use this signifier to denote that it is a work in progress and invite feedback about any problems you may experience.

- [Hasura 2.0.0-alpha.11 docker quickstart](https://hasura.io/docs/latest/graphql/core/getting-started/docker-simple.html)
- [Hasura 2.0.0-alpha.11 changelog](https://github.com/hasura/graphql-engine/releases)
- [Getting Started with Hasura Cloud](https://hasura.io/docs/latest/graphql/cloud/getting-started/index.html)

## A Summary of Releases

As mentioned in recent release posts, we have historically announced our releases via Discord and updates to the GitHub release page. As adoption continues to increase, we believe this is insufficient for the future.

To that end, we will begin to blog for each release (even if it is only small) so that you can track releases via [blog](http://hasura.io/blog), twitter ([@HasuraHQ](http://twitter.com/HasuraHQ)), [Discord](https://discord.com/invite/hasura), and the [Github Release](https://github.com/hasura/graphql-engine/releases) page. In these posts, we will highlight a few specific elements of each release, but the exhaustive list of features and improvements is always in the changelog.

## Overview

### Breaking Change

In this release, the name of the computed field argument has changed from `<function_name>_args` to `<computed_field_name>_<table_name>_args` as the function name is internal detail for a computed field. This change also enables adding a root-level tracked function as a computed field which previously would have thrown input type conflict error.

### Allow tables with the same name in different sources

In previous releases there was a bug that prevented tables with the same name but from multiple sources. If you have the same table names from different contexts, you can now customise one of them to have a different name from the `Modify` page in Hasura console

### SQL Server Explain API

You’ll also now be able to use the explain feature for SQL Server queries and subscriptions.

### And more...

Those are, of course, just the highlights. All other fixes, and there are many, are included in the changelog.

## Conclusion

Please use the docker target `hasura/graphql-engine:v2.0.0-alpha.11`, try it out, let us know what works and what needs improvement. You can find us on Twitter ([@HasuraHQ)](https://twitter.com/hasurahq) and in [Github](https://github.com/hasura/graphql-engine). For ad-hoc conversation, feel free to join us on the [Hasura Community Discord](https://discord.com/invite/hasura).

And, if you want to get started now with the latest stable release, check out the deployment simplicity of [Hasura Cloud](https://cloud.hasura.io/).

## Previous Posts

For previous release announcements in the 2.x series, please review:

- [Announcing Hasura 2.0.0-alpha.8](https://hasura.io/blog/announcing-hasura-2-0-0-alpha-8/)
- [Announcing Hasura 2.0.0-alpha.9](https://hasura.io/blog/announcing-hasura-2-0-0-alpha-9/)
- [Announcing Hasura 2.0.0-alpha.10](https://hasura.io/blog/announcing-hasura-2-0-0-alpha-10/)