SQL Azure encrypted connection
Options
If I set the Encrypted=True parameter into the advanced dialog it does not work. It is needful if "SECURITY ENABLED ACCESS" is enabled.
Comments
-
When I check "Use SSL" in the advanced connections dialog on a SQL Azure connection, and then run the following query:
this.Connection.ConnectionString
the output ends with ";Encrypt=true". AFAIK, this is the correct way to specify encryption with SQL Azure connections.
Can you be more specific? -
If you see here http://azure.microsoft.com/en-us/documentation/articles/sql-database-auditing-get-started/#subheading-4, you must use this connection string to connect to SQL Azure if the "SECURITY ENABLED ACCESS" is enabled:
Server={server},1433;Database={Db};User ID={user@server};Password={password};Trusted_Connection=False;Encrypt=True;Connection Timeout=30;
So the extra parameter is Encrypt=True. -
Under the tab "Auditing & Security features":
use Security Enabled Connection Strings
If the security option is enabled is not possible to connect to the DB from LINQPad.
Do you need a screenshot? -
What I'm saying is that LINQPad *does* put "Encrypt=true" into SQL Azure connection strings if you check the 'Use SSL' box. It always has.
You can verify this by dumping the connection string. -
Yes, I saw, but it does not connect, I think it depends from the format of the connection string (for example the @ between server and username).
If you can try to enable the option on Azure you will see that you cannot connect with LINQPad. -
You can enter "user@server" into the user name box in LINQPad's connection dialog if you think it will help. Whatever you type into this box ends up in the connection string.
-
You see that there are other differences:
1. Server instead DataSource
2. port in the DataSource
3. Database instead Initial Catalog
4. Trusted_Connection=False missing
5. @ in the username
Is difficult to make tests, cannot you allow to insert a custom connection string in another textbox? -
Joe, finally I discovered the difference between the connections
The server name is:
tcp:{your}.database.secure.windows.net, so there is .secure. into.
Sorry for the confusion.
