If a database does not exist at the point that it is required (for example, you attempt to upload a data file to a datastore that has not yet been created in the database instance), 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:datastore -provider:az -name:<datastore-name> [-db|existdb:<database-name>] [-file:<script-name.sql>]
where <database-name> is the name of a new database (-db) or existing database (-existdb) that can house multiple datastores\regions, and a cross-region database - if you omit either option, a new database called <datastore-name> will be created for the datastore; <script-name.sql> is the name of the script file to be created.
| 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.
Once you have created the script files, use the dbfhadmin utility to run them, and create the required databases. Before you run the -createdb command, ensure that the sqlcmd command is on the PATH.
dbfhadmin -createdb <database-address> -provider:az -type:datastore -file:<script-name.sql> -userid=<user> -password=<pass>
where <database-address> is the fully qualified database and server name (for example: tcp:mydbinst.database.windows.net), <script-name.sql> is the name of the script file that was created in an earlier step, and <user> and <pass> are valid logon credentials for the database.
Now that the datastores have been created, you can configure the database configuration file to use them.