Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

MS SQL Connector #1642

Closed
marktani opened this issue Jan 16, 2018 · 71 comments
Closed

MS SQL Connector #1642

marktani opened this issue Jan 16, 2018 · 71 comments

Comments

@marktani
Copy link
Contributor

This feature requests serves as a central place to discuss development and progress for the MS SQL connector.

@SebaBoler
Copy link

When you can expect a working connector to Ms SQL ??

@iamgmd
Copy link

iamgmd commented Jan 31, 2018

I need this too

@marktani
Copy link
Contributor Author

Hey @SebaBoler and @iamgmd, thanks a lot for your interest in the MS SQL connector 🙂
I would love to hear your thoughts on specific use cases you'd like to be covered, and an initial suggestion for the SDL syntax and exposed capabilities.

You can read more contributing to a DB connector here.

@jakenuts
Copy link

Super excited about this, though I will probably fall back on the hosted platform as I'm getting tired of managing everything - the NET community is ~desperate for a GraphQL API interface to SQL Server.

@Sawtaytoes
Copy link

I noticed MS SQL was missing on the main README: https://github.com/graphcool/prisma.

@nadilas

This comment has been minimized.

1 similar comment
@jurby

This comment has been minimized.

@boverdrive
Copy link

I waiting for this

@eabassey
Copy link

I need this badly

@marktani
Copy link
Contributor Author

Thanks a lot for your feedback everyone 🙂

If you have any thoughts in the spirit of what I mentioned above, I'd be happy to hear it!
If you want to express your desire in this feature, please use Github reactions on the original post. Thanks! 🙌

@edenprairie
Copy link

I really need this! Please make this happen!

@felixti

This comment has been minimized.

2 similar comments
@albangiroux

This comment has been minimized.

@killjoy2013

This comment has been minimized.

@develomark
Copy link
Contributor

There is a huge .NET community - by supporting MSSQL and writing some how-to's on deploying onto Azure I think you will capture some massive traction in the enterprise space - especially financial services.

@BrianLondon
Copy link

Big +1 on this. Regarding features even just reproducing the pgsql functionality would solve 90% of users needs.

@playerx
Copy link

playerx commented May 29, 2018

This is important because there are lots of enterprise organizations as @develomark mentioned, which use MS SQL and they will be able to start using Prisma (I'll be one who will suggest them to try), hope it will happen soon :) Also I'll take a look current connectors and I'll try to share something valuable about that.

One note here, if you will support azure sql, ms sql will be supported also, because azure sql is limited version of ms sql, but those limits will not have any effects for Prisma.

@vuchl
Copy link

vuchl commented Jun 18, 2018

I also would like to take a vote for a MSSQL connector to

  1. push Prisma/GraphQL to enterprise environments
  2. broaden the availabitly and compatibility of Prisma

Since I have become a user of MSSQL I must say it's a great DBMS and I would like to start a GraphQL project with some of our customers. Therefore I would like to have a solid development library that fits with SQL Server and is capable of using some more of the TSQL features and is not limited to a a really small subset of the SQL standard.

One could say to go with .NET/.NET Core but making Prisma available as a JavaScript solution to the market would propably also accell the need and use of full stack JS developers that could create products for big enterprise customers.

@sytpb
Copy link

sytpb commented Aug 6, 2018

hope this .

@Gary-Shurgin

This comment has been minimized.

@iamgmd
Copy link

iamgmd commented Aug 29, 2018

@Gary-Shurgin Not sure if your post is relevant in this thread as this one is related to wanting MS SQL in Prisma, nothing to do with MySQL.

@Popeye4242
Copy link

This connector should be shipped by default as soon as possible.
Supported should be

  • Tables (of course)
  • Views
  • Stored Procedures (including result selection)
  • Table- and Scalarfunctions
  • Table Types

@mycaule
Copy link

mycaule commented Sep 7, 2018

I think you can add support to this through the Microsoft SQLServer JDBC library ?

Code should be similar to what you have done with MySQL and PostgreSQL.

You might also need to consider supporting different versions :
https://docs.microsoft.com/fr-fr/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix

Microsoft team has also been open-sourcing lot of stuff related to SQL Server lately, may be we can ask their help. Check out the Linux tools they have released:

I am using these tool at work in a Linux / Scala environment with connection to Windows / SQL Server backends. But not using GraphQL for the moment.

@mii9000
Copy link

mii9000 commented Sep 10, 2018

Would like to know whether the work on this has started or not? Dont see a branch for it either.

@PJCAfonso
Copy link

PJCAfonso commented Nov 28, 2018

I need this so badly, at this moment I use TypeORM because of this, if we have MS SQL Server Connector, for sure I change for Prisma.
Other project I develop I used PostgreSQL and MariaDB (MySQL),

@angad777
Copy link

Do we have any timelines for this? Keen to see or contribute to this as it will greatly help when building for enterprises that work only with MS SQL due to legacy implementations.

@AlexSun98
Copy link

I need it badly too. any update yet?

@AndryHTC
Copy link

I don't understand why no one reply. I understand that actually there aren't any intention of doing some efforts; but I don't understand why no one is explicitly saying this.

@AlexSun98
Copy link

Typeorm or sequenlize could be alternatives solution. But they are not designed for gql specifically.

@AndryHTC
Copy link

This is annoying. MS Sql is still in the top 3 most used DBs world wide, double more used than Postgres that already has the connector.

Also if it not deserves a connector yet, I think may deserves a reply at least

@JesseHenson
Copy link

Is this due to the different type of connection. I see on W3 that you simply import mysql and connect, where as a msSql database needs an odbc connection. It would make sense then that a connection like this might take longer and work differently with the infrustructure.

It would be a cool feature to have. Is there a way to use a node server as a middleware for this. Could we use a node server connecting through odbc then pass that to prisma directly from the query response?

https://www.tutorialsteacher.com/nodejs/access-sql-server-in-nodejs

@AndryHTC
Copy link

@JesseHenson
All the kind of reasons would be accepted. A "This feature is postponed due to technical issues" would be great also...

The silence NO.

@AlexSun98
Copy link

if you really need sth for mssql database connector badly. There is another open source library called sql datasource, it’s been recommended by Apollo offical document(you should be able to find it y reading doc of Apollo-datasource-rest)You can find it from Github(https://github.com/cvburgess/SQLDataSource/blob/master/README.md#sqldatasource). It’s based on knex and Apollo-datasource. It provides huge flexibility to build a ms sql server based datasource connector at gql server, it has some good features such as batching, transactions and simple syntax. Try it with dataloader would be a way to go if you can’t wait prisma’s new release. Hope it helps.

@LocalRoast8080
Copy link

Has there been any progress on this? Is there any way to contribute? A MSSQL connector is in much demand!

Its possible to build a GraphQL solution with Apollo and MSSQL. Its still not as elegant as using Prisma and would love to see a connector built for it.

I used this article as a starting point: https://medium.com/infocentric/setup-a-graphql-api-with-apollo-2-0-sequelize-and-express-js-608d1365d776

Installed tedious instead of mysql2. Hope this helps.

I have done this and it is not that difficult If anyone wants to see a SOLID implementation check out the "The road to graphql" by Robin Wieruch

Full walk though

@muloka
Copy link

muloka commented Sep 5, 2019

Prisma 2 is currently being rewritten using Rust instead of Scala.

Are any more DB connectors being written for Prisma 1? Or is the plan to wait until Prisma 2 is out before any more are written? And at that point we may expect to have a SQL Server DB connector?

@AndryHTC
Copy link

Is it a good day to ask about ETA? Or even to ask about EST?
I've seen a lot of good feature proposal for Prisma 2! 😄

But... it's a shame that most of the people are cut off because of the lack of connectors

@toddtarsi
Copy link

Hey, for anyone trying to help out here, but hitting that 404:

It's not too bad to correct the link. Just change 'graphcool' to 'prisma' and the link will work. That will help, because the next link is full of links that 404 too 😆

@muloka
Copy link

muloka commented Oct 26, 2019

@AndryHTC

But... it's a shame that most of the people are cut off because of the lack of connectors

What problem are you trying to solve? Is it that you want to do GraphQL with SQL Server or is it that you want to specifically use Prisma with SQL Server?

@AndryHTC
Copy link

AndryHTC commented Oct 28, 2019

The final target

@AndryHTC

But... it's a shame that most of the people are cut off because of the lack of connectors

What problem are you trying to solve? Is it that you want to do GraphQL with SQL Server or is it that you want to specifically use Prisma with SQL Server?

The final target is obtaining a GraphQL with SQL Server, with subscriptions, schema migrations and all the good stuff of PRISMA. So, probably... The final target is obtaining PRISMA for SQL Server?

I've seen another great tool, also that only for Postgres Hasura

@AndryHTC
Copy link

Sorry, but everything is a mess... Do we need to wait here the connector even for Prisma 2, Prisma Framework or Photon.js ecc...?

@thesobercoder
Copy link

thesobercoder commented Dec 30, 2019

This will be a game changer and I for one would be more than glad to encourage my team to adopting this. Any ETA would be highly appreciated.

@evanheckert
Copy link

Any insights into where this might fit on the roadmap?

@AndryHTC
Copy link

After 2+ years would be gold :)

@Sureiya
Copy link

Sureiya commented Mar 31, 2020

Is there any way to post a bounty towards this feature?

@chuanqisun
Copy link

Is there any way to post a bounty towards this feature?

Bounty or somehow Microsoft buys prisma 😂

@runar-indico
Copy link

runar-indico commented Apr 24, 2020

For prisma 1, I do not think this will happen. For prisma 2, it will probably happen sometime after it is stable, or somebody starts to write this connector. I am told it is a lot easier than for prisma 1.

@DarkLite1
Copy link

Starting a new project and used typeorm for that. Until I saw a demo of Prisma and fell in love with its simple and clean syntax. God I would love to use it in cooperation with MSSQL. Waiting eagerly ... :)

@AndryHTC
Copy link

Starting a new project and used typeorm for that. Until I saw a demo of Prisma and fell in love with its simple and clean syntax. God I would love to use it in cooperation with MSSQL. Waiting eagerly ... :)

Good luck :)

@muloka
Copy link

muloka commented Jul 1, 2020

Prisma is working on this it seems. They've done a lot work patching this driver:

https://github.com/prisma/tiberius

If anyone knows Rust and wants to contribute their expertise on this then check out this repo.

@seyaobey
Copy link

seyaobey commented Sep 3, 2020

Eagerly waiting on this. Because I need a sql database for my project, I'm currently using MySql and it sucks...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests