I would like to deploy packages remotely. Is it possible to use a TCP/IP library with the Dbengine? This is how I've connected normal SF apps to remote db via a vpn. Or is there another way? I'm cautious about installing an app on a production db server.

SQL Server fully supports TCP/IP as does the DDT.  If the specified host name or IP can be resolved and the SQL Server accessed and authenticated, then the DDT can deploy to it.

I knew that SQL server supports TCP/IP, as I've been using it for a couple of years with my app



I'm glad DDT supports it too



Now, how? I've attempted to deploy my security db right from DDT to my remote server. It bombs. I know I have a connection to the server, as SQL Server Management Studio is connected, via TCP/IP (and I've deployed a number of other changes to the db through it). I tried the server name, the IP and the IP:port. All failed, reporting that a connection to SQL server couldn't be established, and to try my settings again.

At what point does it "bomb" and how are you attempting to deploy it?  Are you using the DatabaseMigrator class or deploying through the DDT?  Also, what type of connection is this?  If there is a VPN then there should be no issue, but if these are just exposed ports then there could be some issue there in the connection.

We use SMO (the same thing as SQL Server Management Studio) to actually connect to the server.  We authenticate the connection first before doing anything else.

When authenticating, on page with server name and authentication information.









Using the deploy database wizard directly in the DDT









I have access to port 1433 and terminal services on port 3389.







Whenever I connect to the db, I have to indicate the network library to use and also use the IP. This is how I connected to it within SQL Server Management Studio.

More than likely there is a port that you do not have access to.  Have you tried to put a packet sniffer on the network to see what ports are trying to be accessed?  This is how we figure out those types of issues.

Well, I did some sniffing....and it worked. The DDT had no problem connecting. I'm guessing I probably fubared typing in the password, or used a non-server admin account or something stupid like that. Thanks for the help and sorry for the trouble.

Well, I didn't think it made any sense   I am glad you got it working.