Database Properties

The following describes new or changed properties in the property editor and related information.

EDITION (New)

Specifies the edition of the database, either web for Web Edition or business for Business Edition.

When EDITION is specified but MAXSIZE is not specified, MAXSIZE will be set to the most restrictive size that the edition supports (1 GB for Web Edition and 10 GB for Business Edition).

MAXSIZE (New)

Specifies the maximum size of the database. MAXSIZE must be valid for the specified EDITION. For Web Edition, valid values of MAXSIZE are: 1GB or 5GB. For Business Edition, valid values are: 10GB, 20GB, 30GB, 40GB, or 50GB.

If MAXSIZE is set to a value of 1GB or 5GB, and EDITION is not specified, the database edition is automatically set to Web Edition.

If MAXSIZE is set to a value of 10GB, 20GB, 30GB, 40GB, or 50GB, and EDITION is not specified, the database edition is automatically set to Business Edition.

If neither MAXSIZE or EDITION are specified, a Web Edition database of size 1GB is created.

AS COPY OF [source_server_name.]source_database_name (New)

Copies a database to the same or different SQL Azure server.

Notes:

  • AS COPY OF cannot be used with any other CREATE DATABASE arguments.

    source_server_name

    Specifies the name of the SQL Azure server where the source database is located. This parameter is optional when the source database and the destination database are located on the same SQL Azure server.

  • The AS COPY OF argument does not support fully-qualified unique domain names. In other words, if your server's fully-qualified domain name is serverName.database.windows.net, use only serverName during database copy.

    source_database_name

    Specifies the name of the database that will be copied. This monitors the copy process by querying the sys.databases and sys.dm_database_copies views on the destination server.

    Notes:

    While copying is in progress, the state_desc column of the sys.databases view for the new database will read COPYING.

    If the copying fails, the state_desc column of the sys.databases view for the new database will read SUSPECT. In this case, execute the DROP statement on the new database and try again later.

    If the copying succeeds, the state_desc column of the sys.databases view for the new database will read ONLINE. In this case, the copying is complete and the new database is a regular database, able to be changed independent of the source database.

  • SQL Azure does not support the following options with the CREATE DATABASE statement:
    • All Parameters related to the physical placement of the file, such as <filespec> and <filegroup>
    • COLLATE on a user database
    • External access options, such as DB_CHAINING and TRUSTWORTHY
    • Attaching a database
    • Service broker options, such as ENABLE_BROKER, NEW_BROKER, and ERROR_BROKER_CONVERSATIONS
    • Database snapshot
  • SQL Azure does not support the following options with the ALTER DATABASE statement:
    • COLLATE
    • <file_and_filegroup_options>
    • <add_or_modify_files>
    • <filespec>
    • <add_or_modify_filegroups>
    • <filegroup_updatability_option>
    • <set_database_options>
    • <optionspec>
    • <auto_option>
    • <change_tracking_option>
    • <cursor_option>
    • <database_mirroring_option>
    • <date_correlation_optimization_option>
    • <db_encryption_option>
    • <db_state_option>
    • <db_update_option>
    • <db_user_access_option>
    • <external_access_option>
    • <parameterization_option>
    • <recovery_option>
    • <service_broker_option>
    • <snapshot_option>
    • <sql_option>
  • GRANT Database Permissions - SQL Azure does not support the following options with the GRANT statement:
    • <database_principal> options:
      • Application_role
      • Database_user_mapped_to_Windows_User
      • Database_user_mapped_to_Windows_Group
      • Database_user_mapped_to_certificate
      • Database_user_mapped_to_asymmetric_key
  • GRANT Database Principal Permissions grants permissions on a database user, database role, or application role. SQL Azure does not support the following arguments and options when using the GRANT statement:
    • GRANT ON APPLICATION ROLE
    • <database_principal> options:
      • Application_role
      • Database_user_mapped_to_Windows_User
      • Database_user_mapped_to_Windows_Group
      • Database_user_mapped_to_certificate
      • Database_user_mapped_to_asymmetric_key

The following describes the impacts on the SQL Azure Database Editor as compared to the SQL Server 2008 Database Editor:

  • All properties on General, File, and Options tabs are invalid.
  • In the Navigation Grid, Database Type, Compatibility Level, and Collation are unavailable.