Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

How can I restart my SQL Azure Server ?

Is this possible ?

share|improve this question

closed as not a real question by rnxrx, Scott Pack, MDMarra, voretaq7 Nov 10 '12 at 21:48

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

    
My first interaction with the sql genius MrDenny and he is telling me I'm dumb... #sadface –  Robotsushi Aug 23 '12 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 '12 at 23:45
    
Well I can't connect entity framework to a SQL Azure instance. I believe that the issue is VS11 beta. There is a bug report about the exact issue I'm having. I am in the process of uninstalling vs11 beta and .net 4.5. I have high hopes. –  Robotsushi Aug 24 '12 at 16:43
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 '12 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 '12 at 17:15

1 Answer 1

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

share|improve this answer
    
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 at 20:44
    
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 at 3:28

Not the answer you're looking for? Browse other questions tagged or ask your own question.