SQL Server in Windows Azure Virtual Machines

Welcome to the feature voting forum for SQL Server in Windows Azure Virtual Machines. Please either vote for a feature already in the list or add a new entry. We really value your feedback as it will help us better prioritize updates to the service.

Background Information:
In June 2012, we announced some exciting new features in Windows Azure that are available for preview now, including Windows Azure Virtual Machines (VM). During preview, customers can evaluate running SQL server in virtual machines in two ways:
(1) Deploy a Windows Virtual Machine with a SQL Server 2012 Evaluation copy from the image gallery on instance sizes of medium or larger.
(2) If you are a Microsoft Volume Licensing customer with Software Assurance agreement, you can build your own Hyper-V virtual machines, install SQL Server on them, and upload them to the Windows Azure Virtual Machine. You can find licensing details here

Additional details on running SQL server in Windows Azure Virtual Machines is available here

How can we improve SQL Server in Windows Azure Virtual Machines?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can vote and comment on it.

If it doesn't exist, you can post your idea so others can vote on it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Make the C drive bigger and don't use it for the default location for DB files

    When installing a VM on Windows Azure using the SQL Server 2012 template, the server is provisioned to use the C: drive for the database directories. On a 30GB C: drive, this leaves only 7 GB available for any databases if someone is not paying attention. The directories for the database data, log and backup files should at least default to the D drive. In addition, the setup files which look like that take around 6GB should also be on the D: drive so that the C: drive doesn't fill up too fast.

    6 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Forgot password?
      Create a password
      I agree to the terms of service
      Signed in as (Sign out)
      Close
      Close
      You have left! (?) (thinking…)
      1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    • Don't see your idea?

    SQL Server in Windows Azure Virtual Machines

    Feedback and Knowledge Base

    (thinking…)