Server=tcp:servername.database.windows.net,1433; Database=TestDB; UserID=username; Password=myPassword; Encrypt=True; TrustServerCertificate=False Driver={SQL Server Native Client 11.0};Server=tcp:servername.database.windows.net,1433; Database=TestDB; Uid=username; Pwd=myPassword; Encrypt=Yes; TrustServerCertificate=No $connectionInfo = array("Database"=>$dbName, "UID"=>$userName, "PWD"=>$userPassword, "Encrypt"=>true, "TrustServerCertificate"=>false);

Provides some protection again Denial-of-Service attacks Blocks IP addresses at multiple levels (db, server, service) for up to 5 minutes Detects repeated bad connection attempts

From Internet

Server is just a logical and administrative container for databases Two fixed administrative roles dbmanager loginmanager Server Admin (aka “server-level principal”) is like ‘sa’ Database-level permissions and roles essentially same as SQL Server Normal Logins cannot change own password by default No server permissions or user-defined server roles

sys.all_columnssys.foreign_key_columnssys.synonymssys.tables sys.all_objectssys.foreign_keyssys.system_columns sys.database_principals sys.all_parameterssys.identity_columnssys.system_objects sys.database_permissions sys.proceduressys.index_columnssys.system_parameters sys.databases sys.all_viewssys.indexessys.system_sql_modules sys.event_log sys.check_constraintssys.key_constraintssys.system_views sys.firewall_rules sys.columnssys.objectssys.table_types sys.database_firewall_rules

SQL and Windows Authen- tication Fixed password policy Idle connection timeout No native data-at-rest encryption Auditing performed by application or through triggers Integration with Windows password policy No native idle connection timeout Database and cell- level encryption

Virtual MasterDB with virtual Logins Fixed roles in MasterDB Automatic patching with no down time MasterDB with Login principals User- defined server roles and server- level permissions Manual patching with possible down time

Windows Azure