Databases Reference
In-Depth Information
2.
In the Data Source Properties dialog, you define the type of connection and the
connection properties. Select the “Embedded connection” option, and then click the Type
down arrow. You read earlier that beginning with SQL Server 2008 R2 a SQL Database-
specific provider was included, and this is where you find it, along with other data source
types. As shown in Figure
6-8
, select the new data provider for SQL Database, called
Microsoft SQL Azure (what else are they going to call it?).
Figure 6-8.
The Data Source Properties dialog
When you select this provider, the Connection String text box defaults to
Encrypt=True;TrustServerCertificate=False
These two parameters and associated values are defaulted for you. It's recommended that you not change
them. The
Encrypt
parameter indicates that SQL Server will use SSL encryption for all data sent between the
server and client if the server has a cert installed. The
TrustServerCertificate
property tells the transport layer
to use SSL to encrypt the channel and bypass walking the cert chain to validate trust. When both
Encrypt
and
TrustServerCertificate
are set to
True
, the encryption level specified
on the server
is used even if the value of the
Encrypt
parameter in this connection string is set to
False
.
However, even with this default string set, you still need to add the SQL Database connection information.
3.
Click the Edit button to open the Connection Properties dialog, shown in Figure
6-9
. Enter
your SQL Database instance name, username, and password. You should know by now
that you can't use Windows Authentication with SQL Database, so make sure you enter the
SQL Database account username and password.
