From 737041200732e2d1885693e5d6c0114280e4673d Mon Sep 17 00:00:00 2001 From: Jared Moore Date: Mon, 24 Jul 2017 16:08:36 -0700 Subject: [PATCH] Fixed/suppressed most linter warnings/errors for Microsoft.Sql (#1441) * Validation baseline * Fixed legit TrackedResourceListByImmediateParent warnings. * Fixed ARM resource model warnings. Microsoft.Sql has some resource types that do not contain "type" property. We had modeled these as "SubResource". However since "type" is not required in the ProxyResource definition, we can use ProxyResource instead, which fixed various resource model related warnings. * Removed "kind" enums. These are not real enums because they are actually semicolon-separated lists. e.g. server kind can be "v12.0;user". * Add example for Databases_FailoverReplicationLinkAllowDataLoss * Added missing import/export description * Normalize operation ids. In some cases we are not specifically following the ARM guidelines for operation ids. This change fixes most of the inconsistent cases. SDK breaking change. * Added restore points examples * Fixed model validation warnings * Added override-info to sql readme so .net generate succeeds. * Removed validation progress helper files --- .../Microsoft.Sql/2014-04-01/advisors.json | 6 +- .../backupLongTermRetentionPolicies.json | 4 +- .../backupLongTermRetentionVaults.json | 4 +- .../Microsoft.Sql/2014-04-01/backups.json | 6 +- .../2014-04-01/connectionPolicies.json | 4 +- .../Microsoft.Sql/2014-04-01/dataMasking.json | 8 +- .../databaseSecurityAlertPolicies.json | 6 +- .../Microsoft.Sql/2014-04-01/deprecated.json | 2 +- .../DataWarehouseRestorePointsList.json | 61 ++++++++++++++ .../examples/DatabaseRestorePointsList.json | 28 +++++++ .../DatabaseUpdateImportMaxSasKey.json | 5 +- .../DatabaseUpdateImportMaxStorageKey.json | 5 +- .../DatabaseUpdateImportMinSasKey.json | 1 + .../DatabaseUpdateImportMinStorageKey.json | 1 + .../examples/DatabaseUpdateMax.json | 84 ------------------- .../examples/DatabaseUpdateMin.json | 1 - .../examples/ServerAdminCreateUpdate.json | 1 + .../examples/ServerAdminDelete.json | 5 +- .../2014-04-01/examples/ServerAdminGet.json | 1 + .../2014-04-01/firewallRules.json | 42 ++++++---- .../2014-04-01/geoBackupPolicies.json | 6 +- .../2014-04-01/importExport.json | 3 +- .../Microsoft.Sql/2014-04-01/metrics.json | 51 ++++++----- .../2014-04-01/replicationLinks.json | 55 +++++++----- .../serverAzureADAdministrators.json | 60 ++++++++----- .../2014-04-01/serviceObjectives.json | 44 ++++++---- .../Microsoft.Sql/2014-04-01/sql.core.json | 57 ++++++------- .../Microsoft.Sql/2014-04-01/usages.json | 60 ++++++++----- .../2015-05-01-preview/advisors.json | 58 ++++++------- .../blobAuditingPolicies.json | 12 +-- .../encryptionProtectors.json | 24 +++--- .../2015-05-01-preview/failoverGroups.json | 16 ++-- .../2015-05-01-preview/serverKeys.json | 12 ++- specification/sql/resource-manager/readme.md | 30 +++++-- 34 files changed, 435 insertions(+), 328 deletions(-) create mode 100644 specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DataWarehouseRestorePointsList.json create mode 100644 specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseRestorePointsList.json delete mode 100644 specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMax.json diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/advisors.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/advisors.json index 190c822e0ff..76aaa12b711 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/advisors.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/advisors.json @@ -22,7 +22,7 @@ "DatabaseAdvisors" ], "description": "Returns a list of database advisors.", - "operationId": "Databases_ListAdvisors", + "operationId": "DatabaseAdvisors_ListByDatabase", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -61,7 +61,7 @@ "DatabaseAdvisors" ], "description": "Returns details of a Database Advisor.", - "operationId": "Databases_GetAdvisor", + "operationId": "DatabaseAdvisors_Get", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -101,7 +101,7 @@ "DatabaseAdvisors" ], "description": "Creates or updates a database advisor.", - "operationId": "Databases_CreateOrUpdateAdvisor", + "operationId": "DatabaseAdvisors_CreateOrUpdate", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionPolicies.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionPolicies.json index d76cdaa3ae5..94397f324cc 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionPolicies.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionPolicies.json @@ -21,7 +21,7 @@ "tags": [ "BackupLongTermRetentionPolicies" ], - "operationId": "Databases_GetBackupLongTermRetentionPolicy", + "operationId": "BackupLongTermRetentionPolicies_Get", "description": "Returns a database backup long term retention policy", "x-ms-examples": { "Get backup long term retention policy": { @@ -76,7 +76,7 @@ "tags": [ "BackupLongTermRetentionPolicies" ], - "operationId": "Databases_CreateOrUpdateLongTermRetentionPolicy", + "operationId": "BackupLongTermRetentionPolicies_CreateOrUpdate", "description": "Creates or updates a database backup long term retention policy", "x-ms-examples": { "Update backup long term retention policy": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionVaults.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionVaults.json index bb017cb4fee..1c6657e5f6f 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionVaults.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backupLongTermRetentionVaults.json @@ -21,7 +21,7 @@ "tags": [ "BackupLongTermRetentionVaults" ], - "operationId": "Servers_GetBackupLongTermRetentionVault", + "operationId": "BackupLongTermRetentionVaults_Get", "description": "Gets a server backup long term retention vault", "x-ms-examples": { "Get backup long term retention vault": { @@ -69,7 +69,7 @@ "tags": [ "BackupLongTermRetentionVaults" ], - "operationId": "Servers_CreateBackupLongTermRetentionVault", + "operationId": "BackupLongTermRetentionVaults_CreateOrUpdate", "description": "Updates a server backup long term retention vault", "x-ms-examples": { "Update backup long term retention vault": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backups.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backups.json index 123ae3a0632..a79c3bd1742 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backups.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/backups.json @@ -21,8 +21,12 @@ "tags": [ "DatabaseBackup" ], - "operationId": "Databases_ListRestorePoints", + "operationId": "RestorePoints_ListByDatabase", "description": "Gets a list of database restore points.", + "x-ms-examples": { + "Get a database's restore points" : { "$ref": "./examples/DatabaseRestorePointsList.json" }, + "Get a data warehouse's restore points" : { "$ref": "./examples/DataWarehouseRestorePointsList.json" } + }, "parameters": [ { "$ref": "#/parameters/ApiVersionParameter" diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/connectionPolicies.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/connectionPolicies.json index 2a8694edff2..c3a4f3e9497 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/connectionPolicies.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/connectionPolicies.json @@ -21,7 +21,7 @@ "tags": [ "ConnectionPolicies" ], - "operationId": "Servers_CreateOrUpdateConnectionPolicy", + "operationId": "ServerConnectionPolicies_CreateOrUpdate", "description": "Creates or updates the server's connection policy.", "x-ms-examples": { "Create or update a server's secure connection policy": { "$ref": "./examples/ServerConnectionPolicyCreateOrUpdate.json" } @@ -71,7 +71,7 @@ "tags": [ "ConnectionPolicies" ], - "operationId": "Servers_GetConnectionPolicy", + "operationId": "ServerConnectionPolicies_Get", "description": "Gets the server's secure connection policy.", "x-ms-examples": { "Get a server's secure connection policy": { "$ref": "./examples/ServerConnectionPolicyGet.json" } diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/dataMasking.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/dataMasking.json index 08b288202a0..5295dab97b9 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/dataMasking.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/dataMasking.json @@ -21,7 +21,7 @@ "tags": [ "DataMaskingPolicies" ], - "operationId": "Databases_CreateOrUpdateDataMaskingPolicy", + "operationId": "DataMaskingPolicies_CreateOrUpdate", "description": "Creates or updates a database data masking policy", "x-ms-examples": { "Create or update data masking policy max": { "$ref": "./examples/DataMaskingPolicyCreateOrUpdateMax.json" }, @@ -69,7 +69,7 @@ "tags": [ "DataMaskingPolicies" ], - "operationId": "Databases_GetDataMaskingPolicy", + "operationId": "DataMaskingPolicies_Get", "description": "Gets a database data masking policy.", "x-ms-examples": { "Get data masking policy": { "$ref": "./examples/DataMaskingPolicyGet.json" } @@ -109,7 +109,7 @@ "tags": [ "DataMaskingRules" ], - "operationId": "Databases_CreateOrUpdateDataMaskingRule", + "operationId": "DataMaskingRules_CreateOrUpdate", "description": "Creates or updates a database data masking rule.", "x-ms-examples": { "Create/Update data masking rule for text": { "$ref": "./examples/DataMaskingRuleCreateOrUpdateText.json" }, @@ -174,7 +174,7 @@ "tags": [ "DataMaskingRules" ], - "operationId": "Databases_ListDataMaskingRules", + "operationId": "DataMaskingRules_ListByDatabase", "description": "Gets a list of database data masking rules.", "x-ms-examples": { "List data masking rules": { "$ref": "./examples/DataMaskingRuleList.json" } diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/databaseSecurityAlertPolicies.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/databaseSecurityAlertPolicies.json index dcabe4c681f..909a308ff2b 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/databaseSecurityAlertPolicies.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/databaseSecurityAlertPolicies.json @@ -22,7 +22,7 @@ "SecurityAlert" ], "description": "Gets a database's threat detection policy.", - "operationId": "Databases_GetThreatDetectionPolicy", + "operationId": "DatabaseThreatDetectionPolicies_Get", "x-ms-examples": { "Get database security alert policy": { "$ref": "./examples/DatabaseSecurityAlertGet.json" } }, @@ -76,7 +76,7 @@ "SecurityAlert" ], "description": "Creates or updates a database's threat detection policy.", - "operationId": "Databases_CreateOrUpdateThreatDetectionPolicy", + "operationId": "DatabaseThreatDetectionPolicies_CreateOrUpdate", "x-ms-examples": { "Create database security alert policy min": { "$ref": "./examples/DatabaseSecurityAlertCreateMin.json" }, "Create database security alert policy max": { "$ref": "./examples/DatabaseSecurityAlertCreateMax.json" } @@ -344,4 +344,4 @@ } } } -} +} diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/deprecated.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/deprecated.json index 437aa18f10c..ef66229f172 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/deprecated.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/deprecated.json @@ -21,7 +21,7 @@ "tags": [ "TransparentDataEncryption" ], - "operationId": "Databases_ListTransparentDataEncryptionConfigurations", + "operationId": "TransparentDataEncryptionConfigurations_ListByDatabase", "description": "Gets a list of a database's transparent data encryption configurations. There is only ever one element, named 'current', so GetTransparentDataEncryptionConfiguration should be used instead.", "deprecated": true, "x-ms-examples": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DataWarehouseRestorePointsList.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DataWarehouseRestorePointsList.json new file mode 100644 index 00000000000..8b8590d6b0d --- /dev/null +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DataWarehouseRestorePointsList.json @@ -0,0 +1,61 @@ +{ + "parameters":{ + "subscriptionId":"00000000-1111-2222-3333-444444444444", + "resourceGroupName":"sqlcrudtest-6730", + "serverName":"sqlcrudtest-9007", + "databaseName":"3481", + "api-version":"2014-04-01" + }, + "responses":{ + "200":{ + "body":{ + "value":[ + { + "id":"/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-6730/providers/Microsoft.Sql/servers/9007/databases/3481/restorepoints/131448209670000000", + "name":"131448209670000000", + "location":"West US", + "type":"Microsoft.Sql/servers/databases/restorePoints", + "properties":{ + "restorePointType":"DISCRETE", + "earliestRestoreDate":null, + "restorePointCreationDate":"2017-07-18T03:09:27Z" + } + }, + { + "id":"/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-6730/providers/Microsoft.Sql/servers/9007/databases/3481/restorepoints/131448353660000000", + "name":"131448353660000000", + "location":"West US", + "type":"Microsoft.Sql/servers/databases/restorePoints", + "properties":{ + "restorePointType":"DISCRETE", + "earliestRestoreDate":null, + "restorePointCreationDate":"2017-07-18T07:09:26Z" + } + }, + { + "id":"/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-6730/providers/Microsoft.Sql/servers/9007/databases/3481/restorepoints/131448497660000000", + "name":"131448497660000000", + "location":"West US", + "type":"Microsoft.Sql/servers/databases/restorePoints", + "properties":{ + "restorePointType":"DISCRETE", + "earliestRestoreDate":null, + "restorePointCreationDate":"2017-07-18T11:09:26Z" + } + }, + { + "id":"/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-6730/providers/Microsoft.Sql/servers/9007/databases/3481/restorepoints/131448641650000000", + "name":"131448641650000000", + "location":"West US", + "type":"Microsoft.Sql/servers/databases/restorePoints", + "properties":{ + "restorePointType":"DISCRETE", + "earliestRestoreDate":null, + "restorePointCreationDate":"2017-07-18T15:09:25Z" + } + } + ] + } + } + } +} \ No newline at end of file diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseRestorePointsList.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseRestorePointsList.json new file mode 100644 index 00000000000..823fc44c78b --- /dev/null +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseRestorePointsList.json @@ -0,0 +1,28 @@ +{ + "parameters":{ + "subscriptionId":"00000000-1111-2222-3333-444444444444", + "resourceGroupName":"sqlcrudtest-6730", + "serverName":"sqlcrudtest-9007", + "databaseName":"3481", + "api-version":"2014-04-01" + }, + "responses":{ + "200":{ + "body":{ + "value":[ + { + "id":"/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-6730/providers/Microsoft.Sql/servers/sqlcrudtest-9007/databases/3481/restorepoints/ContinuousRestorePoint", + "name":"ContinuousRestorePoint", + "location":"West US", + "type":"Microsoft.Sql/servers/databases/restorePoints", + "properties":{ + "restorePointType":"CONTINUOUS", + "earliestRestoreDate":"2017-06-12T00:00:00Z", + "restorePointCreationDate":null + } + } + ] + } + } + } +} \ No newline at end of file diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxSasKey.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxSasKey.json index c811c3bfcd0..032335ee9e7 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxSasKey.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxSasKey.json @@ -4,10 +4,11 @@ "resourceGroupName": "sqlcrudtest-4799", "serverName": "sqlcrudtest-5961", "databaseName": "testdb", + "extensionName": "import", "api-version": "2014-04-01", "parameters": { - "name": "Import", - "type": "Microsoft.Sql/servers/databases/extensions", + "name": "Import", + "type": "Microsoft.Sql/servers/databases/extensions", "properties": { "operationMode": "Import", "storageKeyType":"SharedAccessKey", diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxStorageKey.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxStorageKey.json index 2ca02c767e8..0f2dd94966c 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxStorageKey.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMaxStorageKey.json @@ -4,10 +4,11 @@ "resourceGroupName": "sqlcrudtest-4799", "serverName": "sqlcrudtest-5961", "databaseName": "testdb", + "extensionName": "import", "api-version": "2014-04-01", "parameters": { - "name": "Import", - "type": "Microsoft.Sql/servers/databases/extensions", + "name": "Import", + "type": "Microsoft.Sql/servers/databases/extensions", "properties": { "operationMode": "Import", "storageKeyType": "StorageAccessKey", diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinSasKey.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinSasKey.json index 334c760e70b..fb1a1c9e2c3 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinSasKey.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinSasKey.json @@ -4,6 +4,7 @@ "resourceGroupName": "sqlcrudtest-4799", "serverName": "sqlcrudtest-5961", "databaseName": "testdb", + "extensionName": "import", "api-version": "2014-04-01", "parameters": { "properties": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinStorageKey.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinStorageKey.json index 812baaa5ad4..c82911133d9 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinStorageKey.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateImportMinStorageKey.json @@ -4,6 +4,7 @@ "resourceGroupName": "sqlcrudtest-4799", "serverName": "sqlcrudtest-5961", "databaseName": "testdb", + "extensionName": "import", "api-version": "2014-04-01", "parameters": { "properties": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMax.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMax.json deleted file mode 100644 index 4e3068a48a8..00000000000 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMax.json +++ /dev/null @@ -1,84 +0,0 @@ -{ - "parameters": { - "subscriptionId": "00000000-1111-2222-3333-444444444444", - "resourceGroupName": "sqlcrudtest-4799", - "serverName": "sqlcrudtest-5961", - "databaseName": "testdb", - "api-version": "2014-04-01", - "parameters": { - "location": "Japan East", - "properties": { - "edition": "Standard", - "status": "Online", - "createMode": "Default", - "serviceLevelObjective": "S0", - "collation": "SQL_Latin1_General_CP1_CI_AS", - "maxSizeBytes": "268435456000", - "currentServiceObjectiveId": "f1173c43-91bd-4aaa-973c-54e79e15235b", - "requestedServiceObjectiveId": "f1173c43-91bd-4aaa-973c-54e79e15235b", - "requestedServiceObjectiveName": "S0", - "defaultSecondaryLocation": "Japan West", - "earliestRestoreDate": "2017-02-10T01:52:52.923Z", - "containmentState": 2, - "readScale": "Disabled" - } - } - }, - "responses": { - "200": { - "body": { - "id": "/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-4799/providers/Microsoft.Sql/servers/sqlcrudtest-5961/databases/testdb", - "name": "testdb", - "type": "Microsoft.Sql/servers/databases", - "location": "Japan East", - "kind": "v12.0,user", - "properties": { - "edition": "Standard", - "status": "Online", - "serviceLevelObjective": "S0", - "collation": "SQL_Latin1_General_CP1_CI_AS", - "creationDate": "2017-02-24T22:39:46.547Z", - "maxSizeBytes": "268435456000", - "currentServiceObjectiveId": "f1173c43-91bd-4aaa-973c-54e79e15235b", - "requestedServiceObjectiveId": "f1173c43-91bd-4aaa-973c-54e79e15235b", - "requestedServiceObjectiveName": "S0", - "sampleName": null, - "defaultSecondaryLocation": "Japan West", - "earliestRestoreDate": "2017-02-10T01:52:52.923Z", - "elasticPoolName": null, - "containmentState": 2, - "readScale": "Disabled", - "failoverGroupId": null - } - } - }, - "201": { - "body": { - "id": "/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-4799/providers/Microsoft.Sql/servers/sqlcrudtest-5961/databases/testdb", - "name": "testdb", - "type": "Microsoft.Sql/servers/databases", - "location": "Japan East", - "kind": "v12.0,user", - "properties": { - "edition": "Standard", - "status": "Online", - "serviceLevelObjective": "S0", - "collation": "SQL_Latin1_General_CP1_CI_AS", - "creationDate": "2017-02-24T22:39:46.547Z", - "maxSizeBytes": "268435456000", - "currentServiceObjectiveId": "f1173c43-91bd-4aaa-973c-54e79e15235b", - "requestedServiceObjectiveId": "f1173c43-91bd-4aaa-973c-54e79e15235b", - "requestedServiceObjectiveName": "S0", - "sampleName": null, - "defaultSecondaryLocation": "Japan West", - "earliestRestoreDate": "2017-02-10T01:52:52.923Z", - "elasticPoolName": null, - "containmentState": 2, - "readScale": "Disabled", - "failoverGroupId": null - } - } - }, - "202": {} - } -} \ No newline at end of file diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMin.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMin.json index 18f9e0362c2..62d2a39a241 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMin.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/DatabaseUpdateMin.json @@ -6,7 +6,6 @@ "databaseName": "testdb", "api-version": "2014-04-01", "parameters": { - "location": "Japan East" } }, "responses": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminCreateUpdate.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminCreateUpdate.json index 187d99369a7..692c6c60d9c 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminCreateUpdate.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminCreateUpdate.json @@ -3,6 +3,7 @@ "subscriptionId": "00000000-1111-2222-3333-444444444444", "resourceGroupName": "sqlcrudtest-4799", "serverName": "sqlcrudtest-6440", + "administratorName": "activeDirectory", "api-version": "2014-04-01", "properties": { "id": "/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/sqlcrudtest-4799/providers/Microsoft.Sql/servers/sqlcrudtest-6440/administrators/activeDirectory", diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminDelete.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminDelete.json index 36f927b5328..4404d34132d 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminDelete.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminDelete.json @@ -2,8 +2,9 @@ "parameters": { "subscriptionId": "00000000-1111-2222-3333-444444444444", "resourceGroupName": "sqlcrudtest-4799", - "serverName": "sqlcrudtest-6440", - "api-version": "2014-04-01" + "serverName": "sqlcrudtest-6440", + "administratorName": "activeDirectory", + "api-version": "2014-04-01" }, "responses": { "200": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminGet.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminGet.json index 63fce20dd44..a039d842259 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminGet.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/examples/ServerAdminGet.json @@ -3,6 +3,7 @@ "subscriptionId": "00000000-1111-2222-3333-444444444444", "resourceGroupName": "sqlcrudtest-4799", "serverName": "sqlcrudtest-6440", + "administratorName": "activeDirectory", "api-version": "2014-04-01" }, "responses": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/firewallRules.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/firewallRules.json index e99be07c969..de19a56c3c6 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/firewallRules.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/firewallRules.json @@ -190,20 +190,34 @@ } }, "definitions": { - "SubResource": { - "description": "Subresource properties", - "properties": { - "name": { - "readOnly": true, - "type": "string", - "description": "Resource name" + "Resource":{ + "description":"ARM resource.", + "properties":{ + "id":{ + "readOnly":true, + "type":"string", + "description":"Resource ID." }, - "id": { - "readOnly": true, - "type": "string", - "description": "The resource ID." + "name":{ + "readOnly":true, + "type":"string", + "description":"Resource name." + }, + "type":{ + "readOnly":true, + "type":"string", + "description":"Resource type." } - } + }, + "x-ms-azure-resource": true + }, + "ProxyResource":{ + "description":"ARM proxy resource.", + "allOf":[ + { + "$ref":"#/definitions/Resource" + } + ] }, "FirewallRuleProperties": { "properties": { @@ -244,7 +258,7 @@ }, "allOf": [ { - "$ref": "#/definitions/SubResource" + "$ref": "#/definitions/ProxyResource" } ], "description": "Represents a server firewall rule." @@ -305,4 +319,4 @@ } } } -} +} diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/geoBackupPolicies.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/geoBackupPolicies.json index 6e9e81e412c..2d0d5201cbb 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/geoBackupPolicies.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/geoBackupPolicies.json @@ -21,7 +21,7 @@ "tags": [ "GeoBackupPolicies" ], - "operationId": "Databases_CreateOrUpdateGeoBackupPolicy", + "operationId": "GeoBackupPolicies_CreateOrUpdate", "description": "Updates a database geo backup policy.", "x-ms-examples": { "Update geo backup policy": { "$ref": "./examples/GeoBackupPoliciesCreateOrUpdate.json" } @@ -78,7 +78,7 @@ "tags": [ "GeoBackupPolicies" ], - "operationId": "Databases_GetGeoBackupPolicy", + "operationId": "GeoBackupPolicies_Get", "description": "Gets a geo backup policy.", "x-ms-examples": { "Get geo backup policy": { "$ref": "./examples/GeoBackupPoliciesGet.json" } @@ -122,7 +122,7 @@ "tags": [ "GeoBackupPolicies" ], - "operationId": "Databases_ListGeoBackupPolicies", + "operationId": "GeoBackupPolicies_ListByDatabase", "description": "Returns a list of geo backup policies.", "x-ms-examples": { "List geo backup policies": { "$ref": "./examples/GeoBackupPoliciesList.json" } diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/importExport.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/importExport.json index e63d6e353fd..f169e2dc8e8 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/importExport.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/importExport.json @@ -298,7 +298,8 @@ "properties": { "$ref": "#/definitions/ImportExportResponseProperties", - "x-ms-client-flatten": true + "x-ms-client-flatten": true, + "description": "The import/export operation properties." } }, "allOf": [{ diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/metrics.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/metrics.json index b7710bf76c4..409f6f5f5c8 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/metrics.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/metrics.json @@ -208,6 +208,35 @@ } }, "definitions": { + "Resource":{ + "description":"ARM resource.", + "properties":{ + "id":{ + "readOnly":true, + "type":"string", + "description":"Resource ID." + }, + "name":{ + "readOnly":true, + "type":"string", + "description":"Resource name." + }, + "type":{ + "readOnly":true, + "type":"string", + "description":"Resource type." + } + }, + "x-ms-azure-resource": true + }, + "ProxyResource":{ + "description":"ARM proxy resource.", + "allOf":[ + { + "$ref":"#/definitions/Resource" + } + ] + }, "MetricValue": { "properties": { "count": { @@ -247,12 +276,7 @@ "description": "The total value of the metric." } }, - "description": "Represents database metrics.", - "allOf": [ - { - "$ref": "#/definitions/SubResource" - } - ] + "description": "Represents database metrics." }, "MetricName": { "properties": { @@ -397,21 +421,6 @@ }, "required": ["value"], "description": "The response to a list database metric definitions request." - }, - "SubResource": { - "description": "Subresource properties", - "properties": { - "name": { - "readOnly": true, - "type": "string", - "description": "Resource name" - }, - "id": { - "readOnly": true, - "type": "string", - "description": "The resource ID." - } - } } }, "parameters": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/replicationLinks.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/replicationLinks.json index a9fed96c49d..bdafeb30103 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/replicationLinks.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/replicationLinks.json @@ -21,7 +21,7 @@ "tags": [ "DatabaseReplicationLinks" ], - "operationId": "Databases_DeleteReplicationLink", + "operationId": "ReplicationLinks_Delete", "description": "Deletes a database replication link. Cannot be done during failover.", "x-ms-examples": { "Delete a replication link": { "$ref": "./examples/ReplicationLinkDelete.json" } @@ -67,7 +67,7 @@ "tags": [ "DatabaseReplicationLinks" ], - "operationId": "Databases_GetReplicationLink", + "operationId": "ReplicationLinks_Get", "description": "Gets a database replication link.", "x-ms-examples": { "Get a replication link": { "$ref": "./examples/ReplicationLinkGet.json" } @@ -115,7 +115,7 @@ "tags": [ "DatabaseReplicationLinks" ], - "operationId": "Databases_FailoverReplicationLink", + "operationId": "ReplicationLinks_Failover", "description": "Sets which replica database is primary by failing over from the current primary replica database.", "x-ms-examples": { "Failover a replication link": { "$ref": "./examples/ReplicationLinkFailover.json" } @@ -164,8 +164,11 @@ "tags": [ "DatabaseReplicationLinks" ], - "operationId": "Databases_FailoverReplicationLinkAllowDataLoss", + "operationId": "ReplicationLinks_FailoverAllowDataLoss", "description": "Sets which replica database is primary by failing over from the current primary replica database. This operation might result in data loss.", + "x-ms-examples": { + "Failover a replication link": { "$ref": "./examples/ReplicationLinkFailover.json" } + }, "parameters": [ { "$ref": "#/parameters/ApiVersionParameter" @@ -210,7 +213,7 @@ "tags": [ "DatabaseReplicationLinks" ], - "operationId": "Databases_ListReplicationLinks", + "operationId": "ReplicationLinks_ListByDatabase", "description": "Lists a database's replication links.", "x-ms-examples": { "List Replication links": { "$ref": "./examples/ReplicationLinkList.json" } @@ -251,20 +254,34 @@ } }, "definitions": { - "SubResource": { - "description": "Subresource properties", - "properties": { - "name": { - "readOnly": true, - "type": "string", - "description": "Resource name" + "Resource":{ + "description":"ARM resource.", + "properties":{ + "id":{ + "readOnly":true, + "type":"string", + "description":"Resource ID." }, - "id": { - "readOnly": true, - "type": "string", - "description": "The resource ID." + "name":{ + "readOnly":true, + "type":"string", + "description":"Resource name." + }, + "type":{ + "readOnly":true, + "type":"string", + "description":"Resource type." } - } + }, + "x-ms-azure-resource": true + }, + "ProxyResource":{ + "description":"ARM proxy resource.", + "allOf":[ + { + "$ref":"#/definitions/Resource" + } + ] }, "ReplicationLinkProperties": { "properties": { @@ -373,7 +390,7 @@ }, "allOf": [ { - "$ref": "#/definitions/SubResource" + "$ref": "#/definitions/ProxyResource" } ], "description": "Represents a database replication link." @@ -434,4 +451,4 @@ } } } -} +} diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serverAzureADAdministrators.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serverAzureADAdministrators.json index f3aae044ca8..b02250f591a 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serverAzureADAdministrators.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serverAzureADAdministrators.json @@ -23,8 +23,8 @@ ], "operationId":"ServerAzureADAdministrators_CreateOrUpdate", "description":"Creates a new Server Active Directory Administrator or updates an existing server Active Directory Administrator.", - "x-ms-examples":{ - "Create/Update a server administrator":{ + "x-ms-examples":{ + "Create/Update a server administrator":{ "$ref":"./examples/ServerAdminCreateUpdate.json" } }, @@ -82,8 +82,8 @@ ], "operationId":"ServerAzureADAdministrators_Delete", "description":"Deletes an existing server Active Directory Administrator.", - "x-ms-examples":{ - "Delete a server administrator":{ + "x-ms-examples":{ + "Delete a server administrator":{ "$ref":"./examples/ServerAdminDelete.json" } }, @@ -132,8 +132,8 @@ ], "operationId":"ServerAzureADAdministrators_Get", "description":"Returns an server Administrator.", - "x-ms-examples":{ - "Get the Active Directory Administrator":{ + "x-ms-examples":{ + "Get the Active Directory Administrator":{ "$ref":"./examples/ServerAdminGet.json" } }, @@ -169,7 +169,7 @@ "tags":[ "ServerAdministrators" ], - "operationId":"ServerAzureADAdministrators_List", + "operationId":"ServerAzureADAdministrators_ListByServer", "description":"Returns a list of server Administrators.", "x-ms-examples":{ "get a list of server administrators":{ @@ -205,6 +205,35 @@ } }, "definitions":{ + "Resource":{ + "description":"ARM resource.", + "properties":{ + "id":{ + "readOnly":true, + "type":"string", + "description":"Resource ID." + }, + "name":{ + "readOnly":true, + "type":"string", + "description":"Resource name." + }, + "type":{ + "readOnly":true, + "type":"string", + "description":"Resource type." + } + }, + "x-ms-azure-resource": true + }, + "ProxyResource":{ + "description":"ARM proxy resource.", + "allOf":[ + { + "$ref":"#/definitions/Resource" + } + ] + }, "ServerAdministratorProperties":{ "properties":{ "administratorType":{ @@ -250,7 +279,7 @@ }, "allOf":[ { - "$ref":"#/definitions/SqlSubResource" + "$ref":"#/definitions/ProxyResource" } ], "description":"An server Active Directory Administrator." @@ -266,21 +295,6 @@ } }, "description":"The response to a list Active Directory Administrators request." - }, - "SqlSubResource":{ - "description":"Subresource properties", - "properties":{ - "name":{ - "readOnly":true, - "type":"string", - "description":"Resource name" - }, - "id":{ - "readOnly":true, - "type":"string", - "description":"Resource Id" - } - } } }, "parameters":{ diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serviceObjectives.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serviceObjectives.json index f5ec4de412c..42be84471fb 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serviceObjectives.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/serviceObjectives.json @@ -21,7 +21,7 @@ "tags": [ "ServiceObjectives" ], - "operationId": "Servers_GetServiceObjective", + "operationId": "ServiceObjectives_Get", "description": "Gets a database service objective.", "x-ms-examples":{ "Get a service objective": { "$ref": "./examples/ServiceObjectiveGet.json" } @@ -62,7 +62,7 @@ "tags": [ "ServiceObjectives" ], - "operationId": "Servers_ListServiceObjectives", + "operationId": "ServiceObjectives_ListByServer", "description": "Returns database service objectives.", "x-ms-examples":{ "List service objectives": { "$ref": "./examples/ServiceObjectiveList.json" } @@ -96,20 +96,34 @@ } }, "definitions": { - "SubResource": { - "description": "Subresource properties", - "properties": { - "name": { - "readOnly": true, - "type": "string", - "description": "Resource name" + "Resource":{ + "description":"ARM resource.", + "properties":{ + "id":{ + "readOnly":true, + "type":"string", + "description":"Resource ID." }, - "id": { - "readOnly": true, - "type": "string", - "description": "The resource ID." + "name":{ + "readOnly":true, + "type":"string", + "description":"Resource name." + }, + "type":{ + "readOnly":true, + "type":"string", + "description":"Resource type." } - } + }, + "x-ms-azure-resource": true + }, + "ProxyResource":{ + "description":"ARM proxy resource.", + "allOf":[ + { + "$ref":"#/definitions/Resource" + } + ] }, "ServiceObjective": { "properties": { @@ -121,7 +135,7 @@ }, "allOf": [ { - "$ref": "#/definitions/SubResource" + "$ref": "#/definitions/ProxyResource" } ], "description": "Represents a database service objective." diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/sql.core.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/sql.core.json index 4ad40e8a0c7..f97f4c930a4 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/sql.core.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/sql.core.json @@ -620,7 +620,7 @@ "tags": [ "ElasticPools" ], - "operationId": "ElasticPools_ListActivity", + "operationId": "ElasticPoolActivities_ListByElasticPool", "description": "Returns elastic pool activities.", "x-ms-examples":{ "List Elastic pool activity": { "$ref": "./examples/ElasticPoolActivityList.json" } @@ -664,7 +664,7 @@ "tags": [ "ElasticPools" ], - "operationId": "ElasticPools_ListDatabaseActivity", + "operationId": "ElasticPoolDatabaseActivities_ListByElasticPool", "description": "Returns activity on databases inside of an elastic pool.", "x-ms-examples":{ "List elastic pool database activity": { "$ref": "./examples/ElasticPoolDatabaseActivityList.json" } @@ -708,7 +708,7 @@ "tags": [ "ElasticPools" ], - "operationId": "ElasticPools_GetDatabase", + "operationId": "Databases_GetByElasticPool", "description": "Gets a database inside of an elastic pool.", "parameters": [ { @@ -751,9 +751,9 @@ "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/elasticPools/{elasticPoolName}/databases": { "get": { "tags": [ - "ElasticPools" + "Databases" ], - "operationId": "ElasticPools_ListDatabases", + "operationId": "Databases_ListByElasticPool", "description": "Returns a list of databases in an elastic pool.", "parameters": [ { @@ -830,9 +830,9 @@ "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/recommendedElasticPools/{recommendedElasticPoolName}/databases/{databaseName}": { "get": { "tags": [ - "RecommendedElasticPools" + "Databases" ], - "operationId": "RecommendedElasticPools_GetDatabases", + "operationId": "Databases_GetByRecommendedElasticPool", "description": "Gets a database inside of a recommented elastic pool.", "parameters": [ { @@ -909,9 +909,9 @@ "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/recommendedElasticPools/{recommendedElasticPoolName}/databases": { "get": { "tags": [ - "RecommendedElasticPools" + "Databases" ], - "operationId": "RecommendedElasticPools_ListDatabases", + "operationId": "Databases_ListByRecommendedElasticPool", "description": "Returns a list of databases inside a recommented elastic pool.", "parameters": [ { @@ -993,7 +993,7 @@ "tags": [ "ServiceTierAdvisors" ], - "operationId": "Databases_GetServiceTierAdvisor", + "operationId": "ServiceTierAdvisors_Get", "description": "Gets a service tier advisor.", "parameters": [ { @@ -1038,7 +1038,7 @@ "tags": [ "ServiceTierAdvisors" ], - "operationId": "Databases_ListServiceTierAdvisors", + "operationId": "ServiceTierAdvisors_ListByDatabase", "description": "Returns service tier advisors for specified database.", "parameters": [ { @@ -1079,7 +1079,7 @@ "tags": [ "TransparentDataEncryption" ], - "operationId": "Databases_CreateOrUpdateTransparentDataEncryptionConfiguration", + "operationId": "TransparentDataEncryptionConfigurations_CreateOrUpdate", "description": "Creates or updates a database's transparent data encryption configuration.", "parameters": [ { @@ -1133,8 +1133,11 @@ "tags": [ "TransparentDataEncryption" ], - "operationId": "Databases_GetTransparentDataEncryptionConfiguration", + "operationId": "TransparentDataEncryptionConfigurations_Get", "description": "Gets a database's transparent data encryption configuration.", + "x-ms-examples": { + "Get a database's transparent data encryption configurations": { "$ref": "./examples/DatabaseTransparentDataEncryptionGet.json" } + }, "parameters": [ { "$ref": "#/parameters/ApiVersionParameter" @@ -1174,7 +1177,7 @@ "tags": [ "TransparentDataEncryption" ], - "operationId": "Databases_ListTransparentDataEncryptionActivity", + "operationId": "TransparentDataEncryptionActivities_ListByConfiguration", "description": "Returns a database's transparent data encryption operation result.", "parameters": [ { @@ -2008,6 +2011,11 @@ }, "TransparentDataEncryption": { "properties": { + "location": { + "type":"string", + "readOnly": true, + "description":"Resource location." + }, "properties": { "x-ms-client-flatten": true, "$ref": "#/definitions/TransparentDataEncryptionProperties", @@ -2016,7 +2024,7 @@ }, "allOf": [ { - "$ref": "#/definitions/SubResource" + "$ref": "#/definitions/ProxyResource" } ], "description": "Represents a database transparent data encryption configuration." @@ -2431,7 +2439,7 @@ }, "allOf": [ { - "$ref": "#/definitions/SubResource" + "$ref": "#/definitions/ProxyResource" } ], "description": "Represents a Service Tier Advisor." @@ -2555,7 +2563,7 @@ }, "allOf": [ { - "$ref": "#/definitions/SubResource" + "$ref": "#/definitions/ProxyResource" } ], "description": "Represents a database transparent data encryption Scan." @@ -2572,21 +2580,6 @@ }, "required": ["value"], "description": "Represents the response to a list database transparent data encryption activity request." - }, - "SubResource": { - "description": "Subresource properties", - "properties": { - "name": { - "readOnly": true, - "type": "string", - "description": "Resource name" - }, - "id": { - "readOnly": true, - "type": "string", - "description": "The resource ID." - } - } } }, "parameters": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/usages.json b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/usages.json index 7c9b34600df..0b224c180ef 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/usages.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2014-04-01/usages.json @@ -21,7 +21,7 @@ "tags": [ "Servers" ], - "operationId": "Servers_ListUsages", + "operationId": "ServerUsages_ListByServer", "description": "Returns server usages.", "x-ms-examples":{ "List servers usages": { "$ref": "./examples/ServerUsageMetricsList.json" } @@ -58,7 +58,7 @@ "tags": [ "Databases" ], - "operationId": "Databases_ListUsages", + "operationId": "DatabaseUsages_ListByDatabase", "description": "Returns database usages.", "x-ms-examples": { "List database usage metrics": { "$ref": "./examples/DatabaseUsageMetricsList.json" } @@ -99,6 +99,35 @@ } }, "definitions": { + "Resource":{ + "description":"ARM resource.", + "properties":{ + "id":{ + "readOnly":true, + "type":"string", + "description":"Resource ID." + }, + "name":{ + "readOnly":true, + "type":"string", + "description":"Resource name." + }, + "type":{ + "readOnly":true, + "type":"string", + "description":"Resource type." + } + }, + "x-ms-azure-resource": true + }, + "ProxyResource":{ + "description":"ARM proxy resource.", + "allOf":[ + { + "$ref":"#/definitions/Resource" + } + ] + }, "ServerUsage": { "properties": { "name": { @@ -157,6 +186,11 @@ }, "DatabaseUsage": { "properties": { + "name": { + "readOnly": true, + "type": "string", + "description": "The name of the usage metric." + }, "resourceName": { "readOnly": true, "type": "string", @@ -191,12 +225,7 @@ "description": "The next reset time for the usage metric (ISO8601 format)." } }, - "description": "The database usages.", - "allOf": [ - { - "$ref": "#/definitions/SubResource" - } - ] + "description": "The database usages." }, "DatabaseUsageListResult": { "properties": { @@ -210,21 +239,6 @@ }, "required": ["value"], "description": "The response to a list database metrics request." - }, - "SubResource": { - "description": "Subresource properties", - "properties": { - "name": { - "readOnly": true, - "type": "string", - "description": "Resource name" - }, - "id": { - "readOnly": true, - "type": "string", - "description": "The resource ID." - } - } } }, "parameters": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/advisors.json b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/advisors.json index 36ba0022abd..551024a77dc 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/advisors.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/advisors.json @@ -21,8 +21,8 @@ "tags": [ "DatabaseAdvisors" ], - "description": "Returns a list of database advisors.", - "operationId": "Databases_ListAdvisors", + "description": "Gets a list of database advisors.", + "operationId": "DatabaseAdvisors_ListByDatabase", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -51,15 +51,15 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { - "List of database advisors": { - "$ref": "./examples/DatabaseAdvisorList.json" - }, "List of database recommended actions for all advisors": { "$ref": "./examples/DatabaseRecommendedActionListExpand.json" + }, + "List of database advisors": { + "$ref": "./examples/DatabaseAdvisorList.json" } } } @@ -69,8 +69,8 @@ "tags": [ "DatabaseAdvisors" ], - "description": "Returns details of a Database Advisor.", - "operationId": "Databases_GetAdvisor", + "description": "Gets a database advisor.", + "operationId": "DatabaseAdvisors_Get", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -103,7 +103,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { @@ -116,8 +116,8 @@ "tags": [ "DatabaseAdvisors" ], - "description": "Updates a Database Advisor.", - "operationId": "Databases_UpdateAdvisor", + "description": "Updates a database advisor.", + "operationId": "DatabaseAdvisors_Update", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -159,7 +159,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidAdvisorUpsertRequest - The update advisor request body does not exist or has no properties object.\n\n * 400 InvalidAdvisorAutoExecuteStatus - Specified auto-execute status for the advisor is not allowed.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidAdvisorUpsertRequest - The update advisor request body does not exist or has no properties object.\n\n * 400 InvalidAdvisorAutoExecuteStatus - Specified auto-execute status for the advisor is not allowed.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { @@ -175,7 +175,7 @@ "DatabaseRecommendedActions" ], "description": "Gets list of Database Recommended Actions.", - "operationId": "Databases_ListRecommendedActions", + "operationId": "DatabaseRecommendedActions_ListByDatabaseAdvisor", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -211,7 +211,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { @@ -226,8 +226,8 @@ "tags": [ "DatabaseRecommendedActions" ], - "description": "Returns details of a Database Recommended Action.", - "operationId": "Databases_GetRecommendedAction", + "description": "Gets a database recommended action.", + "operationId": "DatabaseRecommendedActions_Get", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -267,7 +267,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { @@ -280,8 +280,8 @@ "tags": [ "DatabaseRecommendedActions" ], - "description": "Updates a Database Recommended Action.", - "operationId": "Databases_UpdateRecommendedAction", + "description": "Updates a database recommended action.", + "operationId": "DatabaseRecommendedActions_Update", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -330,7 +330,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidRecommendedActionUpsertRequest - The update recommended action request body does not exist or has no properties or state object.\n\n * 400 InvalidRecommendedActionState - The specified state for recommended action is invalid\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidRecommendedActionUpsertRequest - The update recommended action request body does not exist or has no properties or state object.\n\n * 400 InvalidRecommendedActionState - The specified state for recommended action is invalid\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 404 RecommendedActionNotFound - The requested recommended action was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { @@ -345,8 +345,8 @@ "tags": [ "ServerAdvisors" ], - "description": "Gets list of server advisors.", - "operationId": "Servers_ListAdvisors", + "description": "Gets a list of server advisors.", + "operationId": "ServerAdvisors_ListByServer", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -372,7 +372,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { @@ -390,8 +390,8 @@ "tags": [ "ServerAdvisors" ], - "description": "Returns details of a Server Advisor.", - "operationId": "Servers_GetAdvisor", + "description": "Gets a server advisor.", + "operationId": "ServerAdvisors_Get", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -421,7 +421,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { @@ -434,8 +434,8 @@ "tags": [ "ServerAdvisors" ], - "description": "Updates a Server Advisor.", - "operationId": "Servers_UpdateAdvisor", + "description": "Updates a server advisor.", + "operationId": "ServerAdvisors_Update", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -474,7 +474,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidAdvisorUpsertRequest - The update advisor request body does not exist or has no properties object.\n\n * 400 InvalidAdvisorAutoExecuteStatus - Specified auto-execute status for the advisor is not allowed.\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." + "description": "*** Error Responses: ***\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidAdvisorUpsertRequest - The update advisor request body does not exist or has no properties object.\n\n * 400 InvalidAdvisorAutoExecuteStatus - Specified auto-execute status for the advisor is not allowed.\n\n * 404 SubscriptionDoesNotHaveServer - The requested server was not found\n\n * 404 DatabaseDoesNotExist - The requested database was not found\n\n * 404 SubscriptionDoesNotHaveElasticPool - The requested elastic pool was not found\n\n * 404 AdvisorNotFound - The requested advisor was not found.\n\n * 405 NotSupported - This functionality is not supported.\n\n * 409 Conflict - Request could not be processed because of conflict in the request.\n\n * 503 ServiceTemporarilyUnavailable - Feature temporarily unavailable." } }, "x-ms-examples": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/blobAuditingPolicies.json b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/blobAuditingPolicies.json index 589a438e9f2..92b1c570230 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/blobAuditingPolicies.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/blobAuditingPolicies.json @@ -22,7 +22,7 @@ "BlobAuditing" ], "description": "Gets a database's blob auditing policy.", - "operationId": "Databases_GetBlobAuditingPolicy", + "operationId": "DatabaseBlobAuditingPolicies_Get", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -80,7 +80,7 @@ "BlobAuditing" ], "description": "Creates or updates a database's blob auditing policy.", - "operationId": "Databases_CreateOrUpdateBlobAuditingPolicy", + "operationId": "DatabaseBlobAuditingPolicies_CreateOrUpdate", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -143,11 +143,11 @@ } }, "x-ms-examples": { - "Create or update a database's blob auditing policy with minimal parameters": { - "$ref": "./examples/DatabaseBlobAuditingCreateMin.json" - }, "Create or update a database's blob auditing policy with all parameters": { "$ref": "./examples/DatabaseBlobAuditingCreateMax.json" + }, + "Create or update a database's blob auditing policy with minimal parameters": { + "$ref": "./examples/DatabaseBlobAuditingCreateMin.json" } } } @@ -315,4 +315,4 @@ } } } -} +} \ No newline at end of file diff --git a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/encryptionProtectors.json b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/encryptionProtectors.json index f2092b07f15..2222dfcc353 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/encryptionProtectors.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/encryptionProtectors.json @@ -21,8 +21,8 @@ "tags": [ "EncryptionProtectors" ], - "description": "Returns a list of the server encryption protectors", - "operationId": "Servers_ListEncryptionProtectors", + "description": "Gets a list of server encryption protectors", + "operationId": "EncryptionProtectors_ListByServer", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -63,8 +63,8 @@ "tags": [ "EncryptionProtectors" ], - "description": "Returns the server encryption protector.", - "operationId": "Servers_GetEncryptionProtector", + "description": "Gets a server encryption protector.", + "operationId": "EncryptionProtectors_Get", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -115,7 +115,7 @@ "EncryptionProtectors" ], "description": "Updates an existing encryption protector.", - "operationId": "Servers_CreateOrUpdateEncryptionProtector", + "operationId": "EncryptionProtectors_CreateOrUpdate", "parameters": [ { "$ref": "#/parameters/ResourceGroupParameter" @@ -169,11 +169,11 @@ }, "x-ms-long-running-operation": true, "x-ms-examples": { - "Update the encryption protector to service managed": { - "$ref": "./examples/EncryptionProtectorCreateOrUpdateServiceManaged.json" - }, "Update the encryption protector to key vault": { "$ref": "./examples/EncryptionProtectorCreateOrUpdateKeyVault.json" + }, + "Update the encryption protector to service managed": { + "$ref": "./examples/EncryptionProtectorCreateOrUpdateServiceManaged.json" } } } @@ -201,6 +201,9 @@ }, "EncryptionProtectorProperties": { "description": "Properties for an encryption protector execution.", + "required": [ + "serverKeyType" + ], "type": "object", "properties": { "subregion": { @@ -279,11 +282,6 @@ "properties": { "kind": { "description": "Kind of encryption protector. This is metadata used for the Azure portal experience.", - "enum": [ - "", - "azurekeyvault", - "servicemanaged" - ], "type": "string" }, "location": { diff --git a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/failoverGroups.json b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/failoverGroups.json index 5fb0012f4ea..24826b21de6 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/failoverGroups.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/failoverGroups.json @@ -56,7 +56,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." + "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 TokenTooLong - The provided token is too long.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation.\n\n * 400 InvalidServerName - Invalid server name specified.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." } }, "x-ms-examples": { @@ -113,7 +113,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 400 FailoverGroupCreateOrUpdatePartiallySucceeded - Some databases could not be added or removed.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 409 FailoverGroupUnableToPerformGroupOperationOnDatabases - The list of databases to add/remove to/from Failover Group contains errors that are preventing operation to complete.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." + "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 TokenTooLong - The provided token is too long.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation.\n\n * 400 InvalidServerName - Invalid server name specified.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 400 FailoverGroupCreateOrUpdatePartiallySucceeded - Some databases could not be added or removed.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 409 FailoverGroupUnableToPerformGroupOperationOnDatabases - The list of databases to add/remove to/from Failover Group contains errors that are preventing operation to complete.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." }, "202": { "description": "Accepted" @@ -168,7 +168,7 @@ "description": "Successfully deleted the failover group." }, "default": { - "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." + "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 TokenTooLong - The provided token is too long.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation.\n\n * 400 InvalidServerName - Invalid server name specified.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." }, "202": { "description": "Accepted" @@ -232,7 +232,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 400 FailoverGroupCreateOrUpdatePartiallySucceeded - Some databases could not be added or removed.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 409 FailoverGroupUnableToPerformGroupOperationOnDatabases - The list of databases to add/remove to/from Failover Group contains errors that are preventing operation to complete.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." + "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 TokenTooLong - The provided token is too long.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation.\n\n * 400 InvalidServerName - Invalid server name specified.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 400 FailoverGroupCreateOrUpdatePartiallySucceeded - Some databases could not be added or removed.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 409 FailoverGroupUnableToPerformGroupOperationOnDatabases - The list of databases to add/remove to/from Failover Group contains errors that are preventing operation to complete.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." }, "202": { "description": "Accepted" @@ -279,7 +279,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." + "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 TokenTooLong - The provided token is too long.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation.\n\n * 400 InvalidServerName - Invalid server name specified.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." } }, "x-ms-pageable": { @@ -332,7 +332,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." + "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 TokenTooLong - The provided token is too long.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation.\n\n * 400 InvalidServerName - Invalid server name specified.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." }, "202": { "description": "Accepted" @@ -386,7 +386,7 @@ } }, "default": { - "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." + "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 TokenTooLong - The provided token is too long.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation.\n\n * 400 InvalidServerName - Invalid server name specified.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout." }, "202": { "description": "Accepted" @@ -654,4 +654,4 @@ } } } -} +} \ No newline at end of file diff --git a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/serverKeys.json b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/serverKeys.json index a19ca02b008..7496e64c061 100644 --- a/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/serverKeys.json +++ b/specification/sql/resource-manager/Microsoft.Sql/2015-05-01-preview/serverKeys.json @@ -21,7 +21,7 @@ "tags": [ "ServerKeys" ], - "description": "Returns a list of server keys.", + "description": "Gets a list of server keys.", "operationId": "ServerKeys_ListByServer", "parameters": [ { @@ -63,7 +63,7 @@ "tags": [ "ServerKeys" ], - "description": "Returns a server key.", + "description": "Gets a server key.", "operationId": "ServerKeys_Get", "parameters": [ { @@ -238,6 +238,9 @@ }, "ServerKeyProperties": { "description": "Properties for a server key execution.", + "required": [ + "serverKeyType" + ], "type": "object", "properties": { "subregion": { @@ -315,11 +318,6 @@ "properties": { "kind": { "description": "Kind of encryption protector. This is metadata used for the Azure portal experience.", - "enum": [ - "", - "azurekeyvault", - "servicemanaged" - ], "type": "string" }, "location": { diff --git a/specification/sql/resource-manager/readme.md b/specification/sql/resource-manager/readme.md index d2ca807a110..5fc0ebbd3af 100644 --- a/specification/sql/resource-manager/readme.md +++ b/specification/sql/resource-manager/readme.md @@ -1,5 +1,5 @@ # Sql - + > see https://aka.ms/autorest This is the AutoRest configuration file for Sql. @@ -7,7 +7,7 @@ This is the AutoRest configuration file for Sql. --- -## Getting Started +## Getting Started To build the SDK for Sql, simply [Install AutoRest](https://aka.ms/autorest/install) and in this folder, run: > `autorest` @@ -21,7 +21,7 @@ To see additional help and options, run: -### Basic Information +### Basic Information These are the global settings for the Sql API. ``` yaml @@ -62,8 +62,12 @@ input-file: - Microsoft.Sql/2015-05-01-preview/serverKeys.json - Microsoft.Sql/2015-05-01-preview/servers.json - Microsoft.Sql/2015-05-01-preview/virtualNetworkRules.json + +# Needed when there is more than one input file +override-info: + title: SqlManagementClient ``` - + ### Tag: package-2014-04 These settings apply only when `--tag=package-2014-04` is specified on the command line. @@ -75,6 +79,10 @@ input-file: - Microsoft.Sql/2014-04-01/replicationLinks.json - Microsoft.Sql/2014-04-01/sql.core.json - Microsoft.Sql/2014-04-01/databaseSecurityAlertPolicies.json + +# Needed when there is more than one input file +override-info: + title: SqlManagementClient ``` @@ -82,7 +90,7 @@ input-file: # Code Generation -## C# +## C# These settings apply only when `--csharp` is specified on the command line. Please also specify `--csharp-sdks-folder=`. @@ -109,3 +117,15 @@ python: payload-flattening-threshold: 2 namespace: azure.mgmt.sql ``` + +# Validation + +``` yaml +directive: + - suppress: TrackedResourceListByImmediateParent + reason: This warning gives many false positives for proxy resources. + - suppress: GuidUsage + reason: This warning gives many positives for existing APIs that cannot be changed. + - suppress: EnumInsteadOfBoolean + reason: This warning gives many positives for existing APIs that cannot be changed. +```