Cannot copy a source database in an elastic pool to another server with no elastic pool

I need to copy a SQL Database in an elastic pool on one server to another server without an elastic pool. However, the following code fails, noting that the elastic pool name of the source database does not exist on the target server.

let copyDatabase =
    targetSqlServer.Databases.Define(target.Name)
        //.WithServiceObjective("P1") // Using 1.4.0
        //.WithStandardEdition(SqlDatabasePremiumServiceObjective.P1)  // Using 1.8.0
        .WithSourceDatabase(sourceDatabase)
        .WithMode(CreateMode.Copy)
        .Create()

As you can see above, I tried to work around this by using the WithStandardEdition (also tried the WithServiceObjective) method. However, these return an interface that is not compatible with then specifying a source database. New-AzureRmSqlDatabaseCopy allows specifying either a target service objective or elastic pool, so I expected the .NET Azure libraries would allow this as well.

This issue exists in versions 1.4.0 and 1.8.0.

[milismsft]

Hi @panesofglass the Azure SQL management service is inconsistent in regards to when setting a service objective while copying a database is allowed and when is not. I was able to successfully copy a SQL database within a premium Elastic Pool to a different SQL server also setting the service objective if the Elastic Pool edition is Premium. Any other edition settings seems to trigger a service error when invoking the createOrUpdate(). Having this inconsistency makes it difficult to model it in the Fluent .NET SDK. I can suggest an work around for now while I will try to see what can be done for v1.9:

var tempStage = sqlServer.Databases.Define("dbCopyName")
    .WithServiceObjective(ServiceObjectiveName.P1);

var dbCopyResult = ((Microsoft.Azure.Management.Sql.Fluent.SqlDatabaseOperations.Definition.IWithAllDifferentOptions)tempStage)
    .WithSourceDatabase(dbSource)
    .WithMode(CreateMode.Copy)
    .Create();

[roofiq]

Hello, is there any known compatibility issue between database in elastic pools and standalone server? I have issue when migrating one database in that way and it fails when updating.

Here is description: https://github.com/MicrosoftDocs/azure-docs/issues/51784