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

ConnectionConfig for Microsoft SqlServer #78

Closed
iamkelllly opened this issue Nov 17, 2021 · 1 comment · Fixed by #151
Closed

ConnectionConfig for Microsoft SqlServer #78

iamkelllly opened this issue Nov 17, 2021 · 1 comment · Fixed by #151
Assignees
Labels
enhancement New feature or request

Comments

@iamkelllly
Copy link
Contributor

Fidesops must support connecting to a SqlServer instance. Test connection details can be found by contacting @iamkelllly

This issue represents just the connection, query building for SqlServer will come in a subsequent issue.

@iamkelllly iamkelllly added the enhancement New feature or request label Nov 17, 2021
@iamkelllly iamkelllly added this to the Roadmap milestone Nov 17, 2021
@iamkelllly iamkelllly modified the milestones: Roadmap, Fidesops 1.2.0 Nov 30, 2021
@pattisdr pattisdr removed their assignment Dec 14, 2021
@pattisdr pattisdr self-assigned this Dec 14, 2021
@pattisdr
Copy link
Contributor

foundation started on branch fidesops_78_microsoft_sql_server. Ran into issues with MSSQL not yet being supported on M1 architecture, but there are suggestions to use an Azure SQL Edge image instead, although the differences between these may matter.

There are also some questions about which SQLAlchemy dialect/DBAPI to use, ran into early M1 issues with PyODBC and pymssql (issues building wheels, but maybe not worth pursuing because sqlalchemy docs say it is unmaintained).

Plan is that I'm just going to stop investigation and a non-m1 chip user will take over.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants