Azure Pricing, SQL Server seems pretty high?

  • Hi, I'm really new to this and I think I've got this wrong, wondering if you can help me.

    I've got an SQL database I'm wanting to put in Azure. It's 32gb and would be accessed by maybe thirty staff avg 20 times a day during normal working hours by a locally installed program. What kind of price should I expect on a monthly basis? If we went for this set up we could sign in for up to 3 years. Looking at the calculator it's giving me figures of over £12k a year which is going to be a hard sell given we've already got it up and running on local servers.

  • Are you looking at servers, VMs, or are you looking at Azure SQL Database? How big are the VMs you're looking at, memory, cpu, disk, etc? For such a small system as you're describing, I'd skip over the VMs and go for the SQL Database. Guarantee, it'll be cheaper.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

  • keven11 wrote:

    I've got an SQL database I'm wanting to put in Azure.

    WHY?  What problem are you trying to solve and why do you think Azure is going to help?

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • Heh... I get that same response (none) to that question a whole lot. 😀

     

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • This was removed by the editor as SPAM

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply