Hello Jose de Jesus Rodriguez Hernandez,
Welcome to Microsoft Q&A!
I understand you cannot deply your SQL Database, in this case, please try to run the following PowerShell script (Please modify the information for it to match your database):
# Define the SQL command to run
$sqlCommand = new-object System.Data.SqlClient.SqlCommand
$sqlCommand.CommandTimeout = 120
$sqlCommand.Connection = $sqlConnection
Write-Output "Issuing command to scale down database"
# Execute the SQL command
$sqlCommand.CommandText= "ALTER DATABASE [YourDatabase] MODIFY (EDITION = 'Premium', MAXSIZE = 1024 GB, SERVICE_OBJECTIVE = 'P6');"
$result = $sqlCommand.ExecuteNonQuery()
In case it doesn't work here are a few steps you can take to troubleshoot and potentially resolve this issue:
- Ensure that your Azure subscription and resource group have sufficient quotas and limits for the deployment. Sometimes, hitting resource limits can cause timeouts.
- If possible, try increasing the timeout settings for the deployment operation. This can sometimes help if the deployment is taking longer due to resource constraints or network issues.
- Since you mentioned modifying the collation, double-check that the collation setting is valid and supported by Azure SQL Database. An unsupported collation could potentially cause issues.
- Verify that there are no network issues or firewall rules blocking the deployment process. Verify that the necessary ports (e.g., 1433 for SQL Server) are open and accessible.
- Implement retry logic in your deployment script. Azure services can experience transient faults, and retrying the operation after a short delay can often resolve these issues
I hope the information provided was useful!
Regards,
Gao
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".