Azure
Allow New-AzSqlDatabaseImport to create a vCore-based database
Currently, New-AzSqlDatabaseImport accepts -Edition <DatabaseEdition> and -ServiceObjectiveName <String>, which allow you to create a DTU-based SQL Database. However, I want to create a vCore-based SQL Database.
I'd like to see new optional parameters added.
- -Edition would be the General Purpose/Business Critical/Hyperscale tier
- -Vcore would be the number of vCores assigned
- -ComputeGeneration would be Gen5, F-Series, etc.
This is in line with the parameters for New-AzSqlDatabase.
This is the code I'd like to run:
New-AzSqlDatabaseImport
-DatabaseName $SQLDB
-Edition $DBEdition
-Vcore $Vcore
-ComputeGeneration $Gen
-DatabaseMaxSizeBytes $DBSize
-ServerName $SqlServerName
-StorageKeyType 'StorageAccessKey'
-StorageKey $StorageAcctKey
-StorageUri $StorageUri
-AdministratorLogin $SqlAdminUser
-AdministratorLoginPassword $SqlAdminPass
-ResourceGroupName $RGName
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.
Is there any update on adding the vcore parameter option? I too am running into this problem when creating a database from a bacpac file.
I've tried to test this with different combinations of -Edition and -ServiceObjectiveName, with no success. Please let us know when the option to use vCore will be available. The work to create a DTU database then convert to a vCore database is unnecessary.
Any updates on this matter Microsoft? I just spend several hours debugging on this, just to realize its a known limitation for several years. Its not ideal to have, to import it as a DTU database, and then change it afterwards.
Hello, just adding my voice in here to ask if this is ever going to be implemented? Seems like a big oversight. We should also be able to create the imported database in an elastic pool.
