Feat: add mssql and sqlserver as aliases of the TSQL dialect

[georgesittas]

No description provided.

[barakalon]

What's the reason here?

[georgesittas]

What's the reason here?

Seems like it's common for folks to use MSSQL, T-SQL and SQL Server interchangeably to refer to the same dialect (relevant SO thread). In SQLMesh we refer to the engine as MSSQL but since the dialect here is called TSQL, you can't do stuff like sqlmesh init mssql.

You could argue that the dialect is tsql though, so this isn't necessarily needed. Just a quality-of-life type of thing. Thought I'd just put this up for discussion, happy to close if y' all disagree.

[VaggelisD]

LGTM, I also think it's a nice-to-have UX feature e.g Postgres could also have psql as an alias etc, up to Toby & Barak to decide

[barakalon]

The dialect names are unique identifiers.
If this is a UX concern for sqlmesh, maybe sqlmesh should handle normalizing dialect names?

[barakalon]

I just worry this adds as much complexity/confusion as it does convenience.
And it doesn't really solve the discovery problem for sqlglot users, since the list of dialects doesn't include mssql or sqlserver. So users still need to know about tsql? I.e., I don't think we support users just guessing the names of dialects in sqlglot haha

[georgesittas]

I'm persuaded 👍
@tobymao agrees this shouldn't go in here as well, fwiw.

Thanks for taking a look!