# AZURE SQL Database : Unable to build DB connection string during continua CI server setup

**URL:** <https://www.finalbuilder.com/forums/t/azure-sql-database-unable-to-build-db-connection-string-during-continua-ci-server-setup/5300>\
**Category:** Discussion\
**Created:** [January 8, 2015, 11:02am UTC](https://www.finalbuilder.com/forums/t/azure-sql-database-unable-to-build-db-connection-string-during-continua-ci-server-setup/5300 "2015-01-08T11:02:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pravins](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/p/5daacb/32.png) [@pravins](https://www.finalbuilder.com/forums/u/pravins)\
**Post date:** [January 8, 2015, 11:02am UTC](https://www.finalbuilder.com/forums/t/azure-sql-database-unable-to-build-db-connection-string-during-continua-ci-server-setup/5300/1 "2015-01-08T11:02:34Z")

</div>

Hi,  
  
We are trying to setup continua CI on virtual machine and our SQL database is on azure server. But we are facing problem while building connection string during continua CI server setup.  
  
we are unable to test provided connection string even after passing correct credentials. So Is it due do to permission issue or Are there any other steps we need to follow to connect azure SQL database.  
  
  
Thanks,  
PRavin

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [January 9, 2015, 12:10pm UTC](https://www.finalbuilder.com/forums/t/azure-sql-database-unable-to-build-db-connection-string-during-continua-ci-server-setup/5300/2 "2015-01-09T12:10:53Z")

</div>

Hi Pravin,  
  
We have not tested Continua with Azure SQL Database and therefore it is not supported at the moment.   
  
The installer uses the&nbsp;SQLOLEDB provider to test the database connection and I understand that Azure SQL does not support this, which is the likely reason for your issue.   
  
You could try installing with a local database string then editing the connection.connection\_string property in Continua.Server.Service.exe.config (under&nbsp;&nbsp;hibernate-configuration/session-factory) to point to your Azure database. We cannot say whether the server willl run without error as Azure SQL does not include all the features of SQL Server.  
  
We do plan to investigate supporting&nbsp;Azure SQL Database&nbsp;in the future.

---

<div class="post-metadata">

**Author:** ![moonriver](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/moonriver/32/128_2.png) [@moonriver](https://www.finalbuilder.com/forums/u/moonriver)\
**Post date:** [February 16, 2016, 7:26am UTC](https://www.finalbuilder.com/forums/t/azure-sql-database-unable-to-build-db-connection-string-during-continua-ci-server-setup/5300/3 "2016-02-16T07:26:12Z")

</div>

It’s been over a year since this was posted. Is Azure SQL supported yet or no?

---

<div class="post-metadata">

**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\
**Post date:** [February 16, 2016, 10:09am UTC](https://www.finalbuilder.com/forums/t/azure-sql-database-unable-to-build-db-connection-string-during-continua-ci-server-setup/5300/4 "2016-02-16T10:09:47Z")

</div>

Hi Mike   
  
 We do still hope to add azure sql support eventually, unfortunately the drivers we need to use (for nhibernate) require .net 4.5, and we are still supporting Server 2003(which is not supported by .net 4.5). For 2.0 we will be dropping server 2003 support so will make the jump to 4.6.1.   
  
 We have a branch in dev that has been converted to .net 4.6.1 and are working through some breaking issues (like wcf certificate support being broken), and we have yet to complete the planned 2.0 features so I don’t have a timeframe. As soon as we have a usable 2.0 installer we’ll get into azure testing. We also do not know what sql features we might be using that may not be supported on azure, so it’s not guaranteed to work without change.
