I don’t see a way to make a reverse engineering connection to SQL Server 2008r2 with an encrypted connection. Anybody got advice? We are moving the server to Sql Server 2012 soon if that makes any difference. We will have a server that requires encrypted connections. Thanks!
There is currently no specific option for encrypted connections to SQL Server databases. We will look into this and see if we can come up with solution or workaround to your issue. In the meantime, thank you for reaching out.
Could you tell us what happens exactly when you try to connect to your server via TDM? Does any error appear?
While Native Connection currently doesn’t support encrypted connection, you might want to try Connection via ADO.
Once you choose Connection via ADO in Reverse Engineering Wizard, choose Data Link Properties | Build, select a provider in Provider Tab (e.g. Microsoft OLE DB Provider for SQL Server) and in All Tab look for property Use Encryption for Data or Trust Server Certificate. Set it to true and then fill in the rest of connection details.
Let us know if this method works for you.
Thanks, Lukas! This works for connecting to Sql Server 2008 R2 with data encrypted !
We have also learned that Native Connection should be encrypted and work with a SQL Server that requires encrypted connections. If a server does not require an encrypted connection, the Native Connection does not use it and there is currently no way to force it (but we plan to implement this option in future).
Basically, you should have no problems using Native Connection with your new SQL Server 2012 that requires encryption. But if you encounter any problems, please let us know.