The February release of Azure Data Studio is now available to download and includes the following key highlights:
- Introducing Admin pack for SQL Server
- Auto-sizing columns in results
- Notebook UI improvements
- Added Profiler filtering
- Added Save as XML
- Added Data-Tier Application Wizard improvements
- Updates to the SQL Server 2019 Preview extension
- Turned on results streaming by default
- Deploy scripts
- Bug fixes
For a list of the complete updates, refer to the release notes.
Download Azure Data Studio now!
At some point or another you may need to move your Azure resources to either another Azure Resource Group or to another Azure Subscription. This is easy to do and is useful when organizing your resources for management or billing scenarios. Before moving any resources it’s best to take a look at the following checklist before moving resources link.
Ok let’s get started. In this example I’ll be moving an Azure Resource Group with a number of services over to another Azure Subscription.
Steps to move resources
Step 1 – Navigate to the resource group you want to move. Go to the Resource groups blade in the Azure portal and then navigate to the particular resource group.
Step 2 – Click on Move button and then select Move to another subscription option.
Step 3 – Next in the resources to move screen, review the resources that are to be moved over which are all automatically selected. Then select the subscription and resource group you want to move target. If the resource group is not already created, you can create it now by clicking on the link to create a new resource group.
Step 4 – Now click on the OK button to start the process. The job will then be validated and then you will see a notification of the movement in progress, followed by a success or failure notification. In the event of a failure, details will be provided on why the resources could not be moved. Usually after working through these issues you can try again.
Step 5 – You should now go to the new resource group you created and verify all the resources are accounted for and that the resources still function as intended.
Step 6 – Finally you want to tidy up and delete the original resource group on the source subscription as it’s now empty and should not be used again. To do this go to the original resource group and click on Delete resource group button. You will be prompted to type in the name of the resource group to confirm you want to continue.
This article covered moving a resource group and all of its resources from one subscription to another. The same process is applicable when moving resources from one resource group to another within the same subscription.
Move resources to new resource group or subscription
Have you ever wanted to find out if a particular Azure service is in preview or generally available? Fellow Azure MVP Barry Luijbregts created a great website which provides up-to-date status of Azure services.
Azure is constantly changing and is sometimes overwhelming to try and keep up with what’s in preview vs generally available. What is awesome about this website is that it’s more up to date than the other Microsoft sites that try to provide this information.
The website is also open source, and you can check out the source code on GitHub: https://github.com/bmaluijb/AzureOverview.
I’ve definitely added this site to my bookmarks and look forward to further enhancements. Thanks Barry!
Last week Microsoft introduced the Azure DevOps Service status portal which provides real-time insights into the current health of Azure DevOps regional feature status and provides additional details on specific events either current or historical.
When you go to the Azure DevOps Service status portal, the main dashboard shows you a 2-dimensional matrix mapping of the feature with geographic regions as shown below.
To see current or historical events, click on the Status History link where you can filter the results by service type, categories, severity and then date range:
Clicking on a particular event log will take you to the event log page which shows all details about the event, what was affected, when it was resolved, and then any workarounds that users can take if needed.
REST APIs will be coming soon for users looking to build automated solutions to watch the service status.
For service health updates relating to Azure’s global services, please refer to the Azure Status page.
For more information on the new Azure DevOps Service status portal, please refer to the Azure DevOps Service Status documentation.
Azure DevOps Service Status portal
Azure DevOps Service Status documentation
This week Azure DevOps finally rolled out one of their most requested feature, a dark theme. I use dark theme for just about any app that supports it, so this is a welcome addition to Azure DevOps. Keep in mind that this is just a preview and is still being refined.
To switch to Dark theme, go to your Azure DevOps portal and click on your user dropdown menu in the top right corner. Then click on Theme menu item.
The theme options pane will then be displayed. Click on the Dark (preview) option to switch to the dark theme.
Voila! DevOps in Dark theme.
Switching to dark theme is a personal choice and is not something that is forced across your organization, which is nice. I recommend you give it a try and see for yourself.
Azure provides a lot of messaging solutions and it can become overwhelming for architects and developers to know when to use which server and for what use case. In this talk, Bahram Banisadr will show real life scenarios, code and discuss architecture patterns for messaging and events using Azure Event Hubs, Service Bus, Event Grid, and Storage Queues.
Watch the session for more details.
BRK3341 – Architect your solution with queues, grids, and hubs: When to use which and for what
Microsoft Ignite 2018
Azure Event Grid
Azure Event Hubs
Azure Service Bus
Azure Storage Queues