Databases Reference
In-Depth Information
Security
Chapter 3 covers security in depth, but the following list summarizes important security considerations before you
deploy your SQL Database instances. From a security standpoint, you need to consider the following constraints:
•
Encryption.
Although SQL Database uses SSL for data transfers, it doesn't support the data-
encryption functions available in SQL Server. However, SQL Database provides support for
hashing functions.
•
SSPI authentication.
SQL Database only supports database logins. As a result, network logins
using Security Support Provider Interface (SSPI) aren't supported.
•
Connection constraints.
In certain cases, the database connection is closed for one of the
following reasons:
•
Excessive resource usage
•
Long-running query
•
Long-running single transaction
•
Idle connection
•
Failover due to server failure
•
Disallowed user names.
Certain user names can't be created, for security reasons:
•
sa
•
admin
•
administrator
•
guest
•
root
•
Login name.
In certain cases, you may need to append the server name to the login name
to correctly log in, in this format: [loginName]@[servername]. So, avoid using the arrobas
character (@) in login names.
•
TCP port 1433.
Only TCP Port 1433 is allowed. It isn't possible to define another listening port
for SQL Database.
Backups
Backing up your SQL Database instance is somewhat different from backing up traditional SQL Server databases. You
can't back up a SQL Database instances in the traditional sense, nor can you restore a SQL Server database in SQL
Database. You do, however, have the ability to create a transactionally consistent clone of a SQL Database instance
before you export/import your data. You can expect the following regarding backups:
•
Backup/Restore operations.
These operations aren't available. In addition, you may not
attach or detach a SQL Database instance.
•
Clone operations.
You may create a clone of a SQL Database instance into another one using
the
CREATE DATABASE
statement.
•
Log files.
You can't access the database log files, nor can you create a log backup.
