Azuredatastudio: Support other types of databases

[atrauzzi]

Primarily postgres (with GIS extensions), redis, azure cosmos and mariadb.

---

STOP!

Don't scroll down!

Want your favourite database supported??

• Click the 👍 icon
• Wait
• Please do not add a comment with _"+1"_ in the message!

_I repeat_, please just upvote this initial problem-description. Do not add a comment as it's harder for the maintainers to track and +1 comments create clutter for any detailed discussion.

CLICK THIS!!
👇

[carwyn]

SQLite would be good too.

[nurettin]

This would be great for some folks who still use informix.

[VaclavElias]

I was about to open this suggestion.
+1 MySQL / MariaDb, +1 PostgreSQL

[chrisramakers]

+1 postgres

[irufus]

Is this considered out of scope?

[mikeball]

+1 postgres

[IvanPudev]

+1 postgres

[pedrozoalencar]

+1 DB2

[atrauzzi]

@irufus - Based on community interest, nope! And it shouldn't be.

[Raymonf]

@irufus Well, the program is called "SQL Operations Studio", not "SQL Server Operations Studio".

[b5n]

It makes sense to support Sqlite due to dotnet core. MySql and Postgres support will bolster both Azure DB and sqlops adoption.

[atrauzzi]

@welkie - Totally agree. And the only alternative on Windows is DataGrip by JetBrains. Still leaves me wanting for something prettier and more direct.

[alfeg]

+1 for postgres

@welkie there is awesome dbeaver app to manage

[insinfo]

+1 postgres

[AlexTroshkin]

+1 postgres

[carwyn]

Convention on Github seems to be to add a thumbs up rather than a +1 as it creates less clutter and less email.

[MikeElghali]

+1 MySQL & MariaDB

[insinfo]

@b5n @welkie @atrauzzi @MikeElghali I totally agree, you took the words out of my mouth.

[kokes]

It's been said, but it apparently needs repeating. Please stop with all that "+1". Use thumbs up/down emojis to express (dis)agreement and stop flooding what's supposed to be an issue tracker.

Thank you.

[fellow99]

+1 mysql

[outwitevil]

+1 postgres

[willembressers]

DB2

[KISSMonX]

666, 希望支持 MySQL 和 PostgreSQL, sqlite3 也不错.

[styfle]

Want your favorite database supported??

1. Click here: https://github.com/Microsoft/sqlopsstudio/issues/56#issue-274488474
2. Click the :+1: icon.
3. Wait.

Why? Because https://github.com/Microsoft/sqlopsstudio/issues/56#issuecomment-345460923 and https://github.com/Microsoft/sqlopsstudio/issues/56#issuecomment-345786041

[b5n]

+1 @styfle

[talley]

+1 postgres

[talley]

+1 MongoDB

[eajardini]

+1 Postgres

[29e7e280-0d1c-4bba-98fe-f7cd3ca7500a]

+mysql

[gatspy]

+1 postgres
+1 mysql
+1 sqlite
+1 mongo

[bystro]

+1 mysql

[MathRobin]

@bystro why not just click on icon : +1 instead of commenting again and again for the same thing... And spamming everybody

[VaclavElias]

I guess many guys are not simply aware of that feature / "policy" / good practise / convention and they are not doing it on purpose.

Maybe @atrauzzi could update his initial post with @styfle reworded comment? Maybe that would reduce a few emails?

[carwyn]

The issue could probably be locked now as I think the point has been made.

[atrauzzi]

@VaclavElias - Done.
@carwyn - I prefer not to see issues locked as it silences the opportunity for any potentially good points.

[VaclavElias]

@atrauzzi great and nicely reworded, let's see what fish will slip through the net :)

[JiyongShi]

+1 mysql

[carloshm]

Multi Database Support (No-SQL, SQL, Graph, etc.), I would recommend to talk to Cosmos DB team for sharing multi-model api support
o https://docs.microsoft.com/en-us/azure/cosmos-db/mongodb-introduction
o https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-introduction
o https://docs.microsoft.com/en-us/azure/cosmos-db/table-introduction
o https://docs.microsoft.com/en-us/azure/cosmos-db/graph-introduction
o https://docs.microsoft.com/en-us/azure/cosmos-db/cassandra-introduction

[LiceRewis]

Oracle support would be super useful at work right now...

[stephanebarbey]

+1 PostgreSQL

[drowa]

I think a fork for each system would be more appropriate.

• SQL Operations Studio for SQL Server
• SQL Operations Studio for SQLLite
• SQL Operations Studio for DB2
• etc.

In this way experts of each system don't need to worry about other systems.

[L0stLink]

I disagree with the idea of having forks for different flavors of SQL, this should be a X-platform database management tool which supports multiple SQL dialects. Forking will not only fragment the community around this product, but will also take away its somewhat unique selling point, there is also the added complexity of maintaining feature parity between all the forks with the divided development force.

[drowa]

@L0stLink: I don't think it is a good idea to have both breadth and depth under the same project; SQL platforms are very complex and diverse.

For features that can be shared by multiple projects, we use modularisation.

[thecotne]

@drowa so you think there should be

sublime text for html
sublime text for css
sublime text for php
sublime text for javascript
sublime text for python
sublime text for sql
sublime text for plain text 🤣

and not one sublime text with support for many languages

[L0stLink]

If support for different SQL dialects is implemented through extensions contributed by the community and/or the sqlops team, the modularity can still be maintained without the need of forking the entire code base. In my opinion, this is a 'best of both worlds' solution and vscode is proof that such a solution can be successful. I am quite sure that this is the direction the team is taking.

[DrSensor]

I wonder why not just load JDBC driver for each SQL based database? (I think dbweaver use this approach)

also is there a need for something like language-server-protocol? Maybe dblang-server-protocol?

[drowa]

@thecotne: you are comparing apples and oranges.

Take a look on how many dialog boxes SSMS has.

[atrauzzi]

@drowa - What you're suggesting ends up being frustrating. There's no reason to assume that a combination of all the dialects would be confusing. You can simply choose a mode if it's even applicable. DataGrip does this and it works just fine.

[chandusekhar]

+1 Oracle

[brunocerecetto]

+1 mysql

[styfle]

@welkie Unfortunately, locking the thread also locks the reaction emojis too 😞

We should delete these 2 comments so that @atrauzzi is the last comment in this thread 😄

[regs01]

FirebirdSQL would be good to be listed as well

[VaclavElias]

Is it art of reading or art of seeing?

:)

[regs01]

Is it art of reading or art of seeing?

sure, i went down all the thread and it wasn't mentioned, so it's not +1

[yhvicey]

Can this feature achieved by extensions? So you can enjoy light-weight and flexibility at the same time.

[traceless0929]

+1 MySQL

[ringods]

Dear SQLOpsStudio Team,

Can you please install this Github app to prevent the +1 reactions?
https://github.com/apps/reaction

[thomaslevesque]

Why just relational databases? Why not CosmosDB, Mongo... ?
Frankly, from the name "Azure Data Studio", I would definitely have expected CosmosDB to be supported.

[atrauzzi]

@thomaslevesque - Haha, I made that one too: https://github.com/Microsoft/azuredatastudio/issues/124

I totally agree, with the new name, this should support everything and anything. Cosmos, redis, etc...

[yualan]

Welcome to Postgres! :)

Help us retweet: https://twitter.com/AzureDataStudio/status/1107726496213327872
Azure Blog: https://azure.microsoft.com/en-us/blog/azure-data-studio-an-open-source-gui-editor-for-postgres/
SQL Server Blog: https://cloudblogs.microsoft.com/sqlserver/2019/03/18/the-march-release-of-azure-data-studio-is-now-available/

[29e7e280-0d1c-4bba-98fe-f7cd3ca7500a]

@yualan Dear sir, would you please add mysql/mariadb support for us ? nice to see postgres, but mysql was more popular and use widely .

[ryan-rushton]

Is anyone looking into doing an oracle extension? We use oracle and mssql at work so I might look into this if someone has started work on it. Considering there is prior art now in the posgres extension I would follow the pattern that sets.

[yualan]

Hi Everyone, thank you for contributing to our # 1 most requested feature by far for Azure Data Studio. Love seeing the engagement in this thread.

Now that PostgreSQL support is in Azure Data Studio, we are now a multi-database tool. Thus, we plan to close this issue and re-open individual tracking issues for each database request.

Please upvote the following issues:

• MySQL
• SQLite
• Azure Cosmos DB
• VistaDB
• MariaDB
• Redis

I will close this issue by the end of this week and update this comment with the the appropriate official tracking issues.

If you would like to request a new DB, please add [Database Support] to the front of the issue. I will choose the main tracking issue to help consolidate. Once the official issue is up, feel free to advocate community to upvote.

[thomaslevesque]

@yualan thanks. I created the issue for Cosmos DB, could you please add the link in your comment?

[anubischpc]

Oracle! +1

[atrauzzi]

STOP!

Are you here to show your interest in having a specific database back end supported?

GREAT!

This issue is closed now and has been replaced by individual ones for each type of DB desired!

• Find the link to the github issue for DB you want supported
• Go to it
• Click the 👍 icon on the original dsecription
• Wait
• Do not add a comment with _"+1"_ in the message!

---

• Redis
• MariaDB
• Azure Cosmos DB
• VistaDB
• SQLite
• MySQL

---

STOP!

This issue is dead!

[kburtram]

I'll lock the conversation on this issue now. Please see @atrauzzi's comment above with links to specific relational database types that can be individually upvoted. Thanks for all the great feedback.