Connecting to SQL Azure with SQL Management Studio
Connecting to SQL Azure with SQL Management Studio
Join the DZone community and get the full member experience.
Join For FreeCompliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper
Intro
If you want to manage your SQL Databases in Azure using tools that you’re a little more familiar and comfortable with – for example – SQL Management Studio, how do you go about connecting?
You could read the help article from Microsoft, or you can follow my intuitive screen-based instructions, below:
Assumptions
1. I’m assuming you have a version of SQL Management Studio already installed. I believe you’ll need at least SQL Server 2008 R2’s version or newer
2. I’m further assuming you’ve already created a SQL Database in Azure
Steps to Connect SSMS to SQL Azure
1. Authenticate to the Azure Portal
2. Click on SQL Databases
3. Click on Servers
4. Click on the name of the Server you wish to connect to…
5. Click on Configure…
If not already in place, click on ‘Add to the allowed IP addresses’ to add your current IP address (or specify an address you wish to connect from) and click ‘Save’
6. Open SQL Management Studio and connect to Database services (usually comes up by default)
- Enter the fully qualified server name (<server>.database.windows.net)
- Change to SQL Server Authentication
- Enter the login preferred (if a new database, the username you specified when yuo created the DB server)
- Enter the correct password
7. Hit the Connect button
Troubleshooting
- Ensure you have the appropriate ports open outbound from your local network or connection (typically port 1433)
- Ensure you have allowed the correct public IP address you’re trying to connect from via the Azure Portal (steps 1-5 above)
- Ensure you are using the correct server name and user name
- For SSMS, this is the server name (in step 4) followed by .database.windows.net
- Ensure you are using SQL Server Authentication
- For SSMS the username format is username@servername
- If you forgot the password of your username, you can reset the password in the Azure Portal, in step 4, click on Dashboard:
Lastly…
You can click on the Database (in step 2) to see your connection options:
Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper
Like This Article? Read More From DZone
Published at DZone with permission of Rob Sanders , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}