# Support for Microsoft SQL Server? **URL:** \ **Category:** Rancher 1.x\ **Created:** [March 31, 2016, 6:59pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255 "2016-03-31T18:59:56Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![JohnRudolfLewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/johnrudolflewis/32/1129_2.png) [@JohnRudolfLewis](https://forums.suse.com/u/JohnRudolfLewis)\ **Post date:** [March 31, 2016, 6:59pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/1 "2016-03-31T18:59:56Z")
Can rancher server use a Microsoft SQL Server? I’d have to manage a mysql cluster, backups, etc myself. If I could point rancher at a MSSQL database that is fully managed for me, my life would be easier. ---
**Author:** ![jlaswell](https://avatars.discourse-cdn.com/v4/letter/j/c2a13f/32.png) [@jlaswell](https://forums.suse.com/u/jlaswell)\ **Post date:** [March 31, 2016, 7:17pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/2 "2016-03-31T19:17:33Z")
iirc from the last meetup, I believe that MySQL is the only supported database. I did a quick search through the [rancher/rancher](https://github.com/rancher/rancher) repo and couldn’t find any mention of MSSQL. ---
**Author:** ![demarant](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/demarant/32/497_2.png) [@demarant](https://forums.suse.com/u/demarant)\ **Post date:** [March 31, 2016, 10:07pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/3 "2016-03-31T22:07:37Z")
hi, you don’t need to manage the mysql cluster…the mysql is inside the rancher server container and it is quite minimal. You just need to backit up now and than. I have used a very simple and elegant docker image [deitch/mysql-backup](https://hub.docker.com/r/deitch/mysql-backup/) that does the job well. Below an example of the use of the mysql-backup in a docker-compose I created at my work to deploy rancher: > ---
**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\ **Post date:** [March 31, 2016, 10:17pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/4 "2016-03-31T22:17:55Z")
All the queries are theoretically database-agnostic, but MySQL & variants are the only supported database (and H2 for integration testing). We have no immediate plans, but if we were to add another it would probably be Postrgres. ---
**Author:** ![edevil](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/edevil/32/1103_2.png) [@edevil](https://forums.suse.com/u/edevil)\ **Post date:** [April 1, 2016, 9:53am UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/5 "2016-04-01T09:53:17Z")
It’s a shame MSSQL is not supported. For us Azure folks this is the only managed DB available. ---
**Author:** ![ColtonProvias](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/coltonprovias/32/504_2.png) [@ColtonProvias](https://forums.suse.com/u/ColtonProvias)\ **Post date:** [April 5, 2016, 4:24pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/6 "2016-04-05T16:24:51Z")
It shouldn’t be that hard to add MSSQL into the mix. There is a MSSQL package available for Go that should be able to slip in in-place of MySQL’s client bindings easily with only a few changes to the code. Just a quick search turned up [https://github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb). Pre-packaging it, however, requires a little bit more work. But I don’t see it being more than just some light hacking to make it work on Azure! ---
**Author:** ![mlandi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mlandi/32/2061_2.png) [@mlandi](https://forums.suse.com/u/mlandi)\ **Post date:** [January 18, 2017, 4:46pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/7 "2017-01-18T16:46:05Z")
This would be a great option for those of in corporate environments that already have HA Microsoft SQL Server setups. It makes it a much easier “sell” to management. ---
**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\ **Post date:** [January 18, 2017, 7:37pm UTC](https://forums.suse.com/t/support-for-microsoft-sql-server/2255/8 "2017-01-18T19:37:16Z")
The practicality of this is it’s effectively a “PRs accepted” kind of feature. If someone wants to write it we’ll take a PR for it. For example, experimental Postgres support was added by a community member and merged into 1.2. But it is not practical for us (as a company) to be spending a bunch of time building support for a DB that is of no use to us personally, without a customer that wants to pay for development and ongoing testing of officially supporting it.