What would be the most cost effective way of spinning up an instance of SQL Server in Azure in order to restore a small SQL Server database from a .bak file to Copy Data to the Data Lake?

Amie Barkes 41 Reputation points

What do you think would be the most cost effective way of spinning up an instance of SQL Server in azure in order to restore a small database from a .bak file (note we only have .bak file so this excludes the possibility of using Azure SQL Database which requires a bacpac file). Ultimately the goal is to extract the data from the 40 tables and copy to the Azure Data Lake.
The frequency of data transfer required would be to repeat this process every day so this should be a consideration in the cost calculation.

Azure SQL Database
Azure Data Lake Storage
Azure Data Lake Storage
An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
1,364 questions
{count} votes

1 answer

Sort by: Most helpful
  1. BhargavaGunnam-MSFT 27,081 Reputation points Microsoft Employee

    Hello @Amie Barkes ,

    Thanks for more details.
    If you want to develop, test, or build a proof of concept, use the freely licensed SQL Server Developer edition. This edition has all the features of SQL Server Enterprise edition, allowing you to build and test any type of application. A SQL Server Developer edition VM only incurs charges for the cost of the VM, because there are no associated SQL Server licensing costs.

    Based on your needs, there are multiple options available. Here are the latest and greatest versions. You can go with one of the SQL VM.

    SQL Server 2019 developer on Windows Server 2019 - gen2
    SQL Server 2019 developer on Windows Server 2022 - gen2
    SQL Server 2017 developer on Windows Server 2019
    SQL Server 2017 developer on Windows Server 2016

    And regarding the VM size, DS1_V2 is the most popular VM for smaller workloads. Also, please see the below screenshot for other popular VMs and their associated cost.


    Also, SQL on VM is available on Linux operating systems too.


    For paid SQL versions, you can use Bring your own license (BYOL)

    The BYOL images are currently only available for Windows virtual machines.

    If you go with the licensed version, Choose a VM size that matches your expected CPU, memory, storage, and I/O bandwidth needs. The licensing cost of SQL Server is directly related to the number of vCPUs.

    To reduce cost, shut down your VM when possible.
    If you are using any workloads that do not run continuously, consider shutting down the virtual machine during the inactive periods. You only pay for what you use.

    To use BYOL with a SQL Server VM, you must have a license for SQL Server Standard or Enterprise and Software Assurance, a required option through some volume licensing programs and an optional purchase with others.

    Please see the below document for SQL on VM pricing guidelines.


    Please let me know if you have any further questions.

    • Please don't forget to click on 130616-image.png or upvote 130671-image.png button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
    • Want a reminder to come back and check responses? Here is how to subscribe to a notification
    • If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators
    1 person found this answer helpful.