New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS SQL Connector #1642

Open
marktani opened this Issue Jan 16, 2018 · 26 comments

Comments

Projects
None yet
@marktani
Copy link
Contributor

marktani commented Jan 16, 2018

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

@SebaBoler

This comment has been minimized.

Copy link

SebaBoler commented Jan 30, 2018

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

@iamgmd

This comment has been minimized.

Copy link

iamgmd commented Jan 31, 2018

I need this too

@marktani

This comment has been minimized.

Copy link
Contributor

marktani commented Jan 31, 2018

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

This comment has been minimized.

Copy link

jakenuts commented Feb 17, 2018

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

This comment has been minimized.

Copy link

Sawtaytoes commented Feb 21, 2018

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

@nadilas

This comment was marked as off-topic.

Copy link

nadilas commented Mar 18, 2018

+1

1 similar comment
@jurby

This comment was marked as off-topic.

Copy link

jurby commented Mar 18, 2018

+1

@boverdrive

This comment has been minimized.

Copy link

boverdrive commented Mar 19, 2018

I waiting for this

@eabassey

This comment has been minimized.

Copy link

eabassey commented Apr 11, 2018

I need this badly

@marktani

This comment has been minimized.

Copy link
Contributor

marktani commented Apr 11, 2018

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

This comment has been minimized.

Copy link

edenprairie commented Apr 16, 2018

I really need this! Please make this happen!

@felixti

This comment was marked as off-topic.

Copy link

felixti commented Apr 23, 2018

+1

2 similar comments
@albangiroux

This comment was marked as off-topic.

Copy link

albangiroux commented Apr 24, 2018

+1

@killjoy2013

This comment was marked as off-topic.

Copy link

killjoy2013 commented May 15, 2018

+1

@develomark

This comment has been minimized.

Copy link
Contributor

develomark commented May 17, 2018

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

This comment has been minimized.

Copy link

BrianLondon commented May 17, 2018

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

@playerx

This comment has been minimized.

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

This comment has been minimized.

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

This comment has been minimized.

Copy link

sytpb commented Aug 6, 2018

hope this .

@Gary-Shurgin

This comment was marked as off-topic.

Copy link

Gary-Shurgin commented Aug 29, 2018

When I execute 'prisma deploy' to a local MySQL instance, I get this error.
What am I missing?

TypeError: Cannot read property 'name' of undefined
at Socket. (C:\Users\Owner\AppData\Roaming\npm\node_modules\prisma\node_modules\pg\lib\connection.js:123:21)

@iamgmd

This comment has been minimized.

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.

@Patrick-Spiegel

This comment has been minimized.

Copy link

Patrick-Spiegel commented Sep 6, 2018

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

This comment has been minimized.

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.

@Ibrahim-Islam

This comment has been minimized.

Copy link

Ibrahim-Islam 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

This comment has been minimized.

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),

@Verikon

This comment has been minimized.

Copy link

Verikon commented Jan 18, 2019

I notice there's some development on the JDBC connector. Having not worked on MSSQL for a long time, I have to ask if the JDBC connector allows use of MSSQL? Azure SQL?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment