Looks like we were able to get you up and running (by removing the port…)!
Would also like to point out that if the following steps listed above do not work for others, the solution is typically related to not having the native client installed. This normally is packaged into installations of 2012 or newer, but if using 2008 or any year prior to that…you’ll need to download the native client associated with your specific version of MS SQL Server.
Working on setting up a wiki that will give a bit better instruction.
Yes, they are. I have a document for installation procedures if you’re still stuck but it looks like you’ve made a connection already just not up to performance standards as of yet…
Shoot me that config data and we will go from there.
I am having the same issue. I am able to connect to my SQL Server 2008 R2 through the free hosted service https://dsp-storenmove.cloud.dreamfactory.com but not from my Amazon EC2 instance (Tried both ubuntu and windows server) using Bitnami installer. I have checked the 5 steps but not able to figure out the issue.
Hi @jayp, what is logged in your DSP’s logs when the connection attempt to SQL Server fails? If you are using the dblib driver, you will need to specify the port in your connection string unless your DB is hosted on port 4000 (the default for the dblib driver).
That helped a lot. Once I gave “dblib:host=hostname:1433;dbname=dbname” It worked. This should be documented to help other users. also surprised as port is not required in DSP cloud server but in Bitnami installation.