4

How can I restart my SQL Azure Server ?

Is this possible ?

Improve this question
10
  • My first interaction with the sql genius MrDenny and he is telling me I'm dumb... #sadface
    – Robotsushi
    Aug 23, 2012 at 17:32
  • Maybe you should mention what the problem is, or why you want to restart it... there are other ways to skin a cat.
    – HopelessN00b
    Aug 23, 2012 at 23:45
  • 1
    @mrdenny is calling you no such thing. Windows Azure SQL Database is a shared resource, multi-tenant database service. You are provided with a connection string and full access to the database(s) that you provision, along with server- and database-level firewall settings, and the service takes care of everything else. Hence... no reason you'd need to restart the server (which equates to multiple physical servers: You don't have physical access to the servers directly.
    – David Makogon
    Aug 27, 2012 at 18:25
  • 1
    The issue was installation of vs2012 side by side with vs2010 on win7. My unit tests were failing because of a communication issue caused by this setup. It really had nothing to do with SQL Azure
    – Robotsushi
    Nov 2, 2012 at 17:15
  • 1
    stackoverflow.com/questions/21262001/… According to this it's possible.
    – carles
    Nov 15, 2017 at 16:15

1 Answer 1

Reset to default
3

This isn't possible. There is no reason that you'd need to restart the SQL Azure instance.

Improve this answer
4
  • 5
    Unless attempts to execute queries do not respond and do not time out. I'm sitting with a db that backs a website, attempts to update tables in the db with SSMS and with the web-based portal are spinning and spinning and not accomplishing anything. with on-prem I'd boot the sql instance and, failing that, re-boot the server and go about my day. Long-time azure user and this is a first.
    – justSteve
    Jul 24, 2014 at 20:44
  • 2
    And to follow up with resolution - closing down SSMS released enough /whatevers\ resources to return to operational state. SELECT statements worked fine - UPDATE statements locked the session when executed via CLI, while website-based UPDATE statements executed correctly.
    – justSteve
    Jul 25, 2014 at 3:28
  • Yes, we also had a slow queries problem and restarting the database was the only way to fix it.
    – carles
    Nov 15, 2017 at 16:13
  • 3
    The second part of this answer is unnecessary and presumptuous, and the first part is not very helpful.
    – Joshua Drake
    Nov 27, 2017 at 18:16

Not the answer you're looking for? Browse other questions tagged .