You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Azure Monitor Logs extension for Azure Data Studio
3
+
description: This article describes how you can connect and query Log Analytics Workspace IDs with Azure Data Studio.
4
+
ms.prod: azure-data-studio
5
+
ms.technology: azure-data-studio
6
+
ms.topic: conceptual
7
+
author: markingmyname
8
+
ms.author: maghan
9
+
ms.reviewer: jukoesma
10
+
ms.custom:
11
+
ms.date: 08/18/2021
12
+
---
13
+
14
+
# Azure Monitor Logs extension for Azure Data Studio (Preview)
15
+
16
+
The Azure Monitor Logs extension for [Azure Data Studio](../what-is-azure-data-studio.md) enables you to connect and query a [Log Analytics workspace](/azure/azure-monitor/logs/data-platform-logs#log-analytics-workspaces).
17
+
18
+
This extension is currently in preview.
19
+
20
+
## Prerequisites
21
+
22
+
If you don't have an Azure subscription, create a [free Azure account](https://azure.microsoft.com/free/) before you begin.
23
+
24
+
The following prerequisites are also required:
25
+
26
+
-[Azure Data Studio installed](../download-azure-data-studio.md).
For a full list of bug fixes addressed for the July Hotfix 2021 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/milestone/75).
49
+
For a full list of bug fixes addressed for the August 2021 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue+milestone%3A%22August+2021+Release%22+is%3Aclosed).
38
50
39
-
#### Known issues in 1.31.1
51
+
#### Known issues in 1.32.0
40
52
41
53
For a list of the current known issues, visit the [issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue).
42
54
@@ -83,6 +95,27 @@ You can reference [Azure Data Studio feedback](https://github.com/microsoft/azur
83
95
> [!Note]
84
96
> All previous versions of Azure Data Studio are not supported.
85
97
98
+
### July Hotfix 2021
99
+
100
+
Azure Data Studio 1.31.1 is the latest general availability (GA) release.
| Connections | Fixed Connection dropped / is not maintained when saving / opening scripts |
111
+
| Connections | Script file opened from command line does not allow DB connection|
112
+
113
+
For a full list of bug fixes addressed for the July Hotfix 2021 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/milestone/75).
114
+
115
+
#### Known issues in 1.31.1
116
+
117
+
For a list of the current known issues, visit the [issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue).
Copy file name to clipboardExpand all lines: docs/linux/tutorial-sql-server-containers-kubernetes-dh2i.md
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -363,6 +363,36 @@ DxEnterprise is high availability clustering software from DH2i that supports SQ
363
363
364
364
With this, you should have an Always On availability group created and database(s) added to the group supporting high availability.
365
365
366
+
> [!NOTE]
367
+
> You can deploy [basic Always On availability group](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/basic-availability-groups-always-on-availability-groups) with SQL Server standard edition, but as you may be aware, one of the limitations of basic availability groups is that you are limited to only having two replicas and one additional configuration only replica required forsuccessful automatic failover. Refer to the [documentation](https://docs.microsoft.com/sql/linux/sql-server-linux-availability-group-overview#configuration-only-replica-and-quorum) for more information on failover with configuration only replica. You can add configuration only replica for containers as well, and to do so, please refer to the [DH2i documentation](https://dh2i.com/wp-content/uploads/DxEnterprise-v21.0-Supplemental-Guide-for-Availability-Groups-in-Kubernetes.pdf), making sure to pass the availability modein the 'dxcli add-ags-node'command as 'configuration_only'.
368
+
369
+
370
+
## Steps to configure Always On availability group listener: (Optional)
371
+
372
+
You can also configure an Always On availability group listener; to do so, follow the steps below:
373
+
374
+
1. Ensure you've created the AG listener using DxEnterprise as outlined in the optional step near the end of the [DH2i documentation](https://dh2i.com/wp-content/uploads/DxEnterprise-v21.0-Supplemental-Guide-for-Availability-Groups-in-Kubernetes.pdf).
375
+
376
+
2. In Kubernetes, you can optionally create static IP addresses. Creating static IP addresses ensures that if the listener service is deleted and recreated, the external IP address assigned to your listener service does not change and thus remains static. Follow the steps outlined [here](https://docs.microsoft.com/azure/aks/static-ip#create-a-static-ip-address) to create a static IP address in Azure Kubernetes Service (AKS).
377
+
378
+
3. After you have created an IP address, you assign that IP address and create the load balancer service, as shown in the sample yaml below:
379
+
380
+
```bash
381
+
apiVersion: v1
382
+
kind: Service
383
+
metadata:
384
+
name: agslistener
385
+
spec:
386
+
type: LoadBalancer
387
+
loadBalancerIP: 52.140.117.62
388
+
selector:
389
+
app: mssql
390
+
ports:
391
+
- protocol: TCP
392
+
port: 44444
393
+
targetPort: 44444
394
+
```
395
+
366
396
## Steps to configure read/write connection redirection: (Optional)
367
397
368
398
After you've created the availability group, you can enable read/write connection redirection from the secondary to primary by following the steps below. For more information, see [Secondary to primary replica read/write connection redirection](../database-engine/availability-groups/windows/secondary-replica-connection-redirection-always-on-availability-groups.md).
Copy file name to clipboardExpand all lines: docs/relational-databases/memory-management-architecture-guide.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -230,7 +230,7 @@ The primary purpose of a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]
230
230
### How buffer management works
231
231
A buffer is an 8 KB page in memory, the same size as a data or index page. Thus, the buffer cache is divided into 8 KB pages. The buffer manager manages the functions for reading data or index pages from the database disk files into the buffer cache and writing modified pages back to disk. A page remains in the buffer cache until the buffer manager needs the buffer area to read in more data. Data is written back to disk only if it is modified. Data in the buffer cache can be modified multiple times before being written back to disk. For more information, see [Reading Pages](../relational-databases/reading-pages.md) and [Writing Pages](../relational-databases/writing-pages.md).
232
232
233
-
When [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] starts, it computes the size of virtual address space for the buffer cache based on a number of parameters such as the amount of physical memory on the system, the configured number of maximum server threads, and various startup parameters. [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] reserves this computed amount of its process virtual address space (called the memory target) for the buffer cache, but it acquires (commits) only the required amount of physical memory for the current load. You can query the **bpool_commit_target** and **bpool_committed columns** in the [sys.dm_os_sys_info](../relational-databases/system-dynamic-management-views/sys-dm-os-sys-info-transact-sql.md) catalog view to return the number of pages reserved as the memory target and the number of pages currently committed in the buffer cache, respectively.
233
+
When [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] starts, it computes the size of virtual address space for the buffer cache based on a number of parameters such as the amount of physical memory on the system, the configured number of maximum server threads, and various startup parameters. [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] reserves this computed amount of its process virtual address space (called the memory target) for the buffer cache, but it acquires (commits) only the required amount of physical memory for the current load. You can query the **committed_target_kb** and **committed_kb** columns in the [sys.dm_os_sys_info](../relational-databases/system-dynamic-management-views/sys-dm-os-sys-info-transact-sql.md) catalog view to return the number of pages reserved as the memory target and the number of pages currently committed in the buffer cache, respectively.
234
234
235
235
The interval between [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] startup and when the buffer cache obtains its memory target is called ramp-up. During this time, read requests fill the buffers as needed. For example, a single 8 KB page read request fills a single buffer page. This means the ramp-up depends on the number and type of client requests. Ramp-up is expedited by transforming single page read requests into aligned eight page requests (making up one extent). This allows the ramp-up to finish much faster, especially on machines with a lot of memory. For more information about pages and extents, refer to [Pages and Extents Architecture Guide](../relational-databases/pages-and-extents-architecture-guide.md#pages-and-extents).
236
236
@@ -347,4 +347,4 @@ Starting with [!INCLUDE[ssSQL14](../includes/sssql14-md.md)] SP2 and [!INCLUDE[s
0 commit comments