If a database does not exist at the point that it is required, it is created on-the-fly; this can be slow for certain RDBMS types, and so we recommended that you create any required databases ahead of time, using SQL scripts.
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> -user:<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> -user:<user> -password:<pass>
see previous command for descriptions.
Next, you must configure your enterprise server region to use the database(s).