For Azure SQL databases, you can use the conventional method of database creation, using ODBC DSNs, as detailed for the other supported database types; but due to the Azure architecture, it is preferable to create the databases ahead of time, using an SQL script file.
dbfhadmin -script -type:region -provider:az -name:<es-name> -file:<script-name.sql>
where <es-name> is the name of the intended enterprise server region.
Parameter | Value |
---|---|
EDITION | standard |
MAXSIZE | 1GB |
SERVICE_OBJECTIVE | S0 |
If you require the database to be created with different characteristics, you must edit the script directly.
dbfhadmin -script -type:crossregion -provider:az -file:<script-name.sql>
dbfhadmin -createdb tcp:<database-address> -file:<script-name.sql> -type:region -provider:az -name:<ES-name> -userid=<user> -password=<pass>
where <database-address> is the fully qualified database and server name (for example: mydbinst.database.windows.net), <script-name.sql> is the name of the script file that was created in an earlier step, <ES-name> is the name of the enterprise server region to operate as the region database, and <user> and <pass> are valid logon credentials for the database.
dbfhadmin -createdb tcp:<database-address> -provider:az -type:crossregion -file:<script-name.sql> -userid=<user> -password=<pass>
see previous command for descriptions.
Next, you must create or edit a configuration file, so that it contains entries to the region and the cross-region databases.