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
Copy file name to clipboardExpand all lines: docs/azure-data-studio/extensibility.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,9 @@ Some of the key extensibility points are:
28
28
29
29
Because the core Azure Data Studio platform is built upon Visual Studio Code, details about the Visual Studio Code extensibility APIs are found in the [Extension Authoring](https://code.visualstudio.com/docs/extensions/overview) and [Extension API](https://code.visualstudio.com/docs/extensionAPI/overview) documentation on the Visual Studio Code website.
30
30
31
+
> [!NOTE]
32
+
> Azure Data Studio releases are aligned with a recent version of VS Code, however the included VS Code engine may not be the current VS Code release. For example, in November 2020 the VS Code engine in Azure Data Studio is 1.48 and the current VS Code version is 1.51. The error message "Unable to install extension '<name>' as it is not compatible with VS Code <version>" when installing an extension is caused by an extension that has a later VS Code engine version defined in the package manifest (`package.json`). You can verify the VS Code engine version in your Azure Data Studio through the **Help** menu under **About**.
33
+
31
34
## Manage Dashboard tab panel contributions
32
35
33
36
For details, see [Contribution Points](#contribution-points) and [Context Variables](#context-variables).
| Azure Arc extension |[Known Issue:](https://github.com/microsoft/azuredatastudio/issues/13319) The "Script to Notebook" button for Arc MIAA & PG deployments does not do field validation before scripting the notebook. This means that if users enter the password wrong in the password confirm inputs then they may end up with a notebook that has the wrong value for the password.| The "Deploy" button works as expected though so users should use that instead. |
37
-
| Object Explorer | Releases of ADS before 1.24.0 have a breaking change in object explorer due to the engine's changes related to [Azure Synapse Analytics SQL on-demand](https://docs.microsoft.com/azure/synapse-analytics/sql/on-demand-workspace-overview). | To continue utilizing object explorer in Azure Data Studio with Azure Synapse Analytics SQL on-demand, you need to use Azure Data Studio 1.24.0 or later. |
37
+
| Object Explorer | Releases of ADS before 1.24.0 have a breaking change in object explorer due to the engine's changes related to [Azure Synapse Analytics serverless SQL pool](https://docs.microsoft.com/azure/synapse-analytics/sql/on-demand-workspace-overview). | To continue utilizing object explorer in Azure Data Studio with Azure Synapse Analytics serverless SQL pool, you need to use Azure Data Studio 1.24.0 or later. |
38
38
39
39
You can reference [Azure Data Studio feedback](https://github.com/microsoft/azuredatastudio) for other known issues and to provide feedback to the product team.
description: 'Learn how to get logs and troubleshoot Azure Data Studio, which is helpful in reporting bug reports.'
4
+
ms.prod: azure-data-studio
5
+
ms.technology: azure-data-studio
6
+
ms.topic: conceptual
7
+
author: dzsquared
8
+
ms.author: drskwier
9
+
ms.reviewer: hanqin, maghan
10
+
ms.custom: seodec18
11
+
ms.date: 11/24/2020
12
+
---
13
+
14
+
# Azure Data Studio Troubleshooting
15
+
Azure Data Studio tracks issues and feature requests using on a [GitHub repository issue tracker](https://github.com/Microsoft/azuredatastudio/issues) for the `azuredatastudio` repository.
16
+
17
+
## If you've experienced any issue
18
+
19
+
Report issues to [GitHub Issue Tracker](https://github.com/Microsoft/azuredatastudio/issues) and let us know any details that will help reproduce the error. Include any [log information](#how-to-set-the-logging-level) from the log file.
20
+
21
+
## Writing good bug reports and feature requests
22
+
23
+
File a single issue per problem and feature request.
24
+
25
+
* Don't enumerate multiple bugs or feature requests in the same issue.
26
+
* Don't add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
27
+
28
+
The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.
29
+
30
+
Include the following information with each issue:
31
+
32
+
* Version of Azure Data Studio
33
+
* Reproducible steps (1... 2... 3...) and what you expected versus what you actually saw.
34
+
* Images, animations, or a link to a video. Images and animations illustrate repro-steps but don't replace them.
35
+
* A code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.
36
+
37
+
> [!NOTE]
38
+
> Because we need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
39
+
40
+
* Errors in the Dev Tools Console (Help | Toggle Developer Tools)
41
+
42
+
Please remember to do the following:
43
+
44
+
* Search the issue repository to see if there exists a duplicate.
45
+
* Simplify your code around the issue so we can better isolate the problem.
46
+
47
+
Don't feel bad if we can't reproduce the issue and ask for more information!
48
+
49
+
## How to set the logging level
50
+
51
+
### Azure Data Studio
52
+
Run the `Developer: Set Log Level...` command to select the log level for the current session. This value is NOT persisted over multiple sessions - so if you restart Azure Data Studio it will revert back to the default `Info` level.
53
+
54
+
If you want to enable debug logging for startup then set the log level to `Debug` and run the `Developer: Reload Window` command
55
+
56
+
### MSSQL (Built-In Extension)
57
+
58
+
If the `Mssql: Log Debug Info` user setting is set to true, then debug log info will be sent to the `MSSQL` output channel.
59
+
60
+
The `Mssql: Tracing Level` user setting is used to control the verbosity of the logging.
61
+
62
+
## Debug log location
63
+
From Azure Data Studio, run the `Developer: Open Logs Folder` command to open the path to the logs. There's many different types of log files that write there, a few of the commonly used ones are:
64
+
65
+
1.`renderer#.log` (for example, renderer1.log) - this file is the log file for the main process.
66
+
1.`telemetry.log` - When the log level is set to `Trace` this file will contain the telemetry events sent by Azure Data Studio
67
+
1.`exthost#/exthost.log` - Log file for the extension host process (this is only the process itself, not the extensions running inside it)
68
+
1.`exthost#/Microsoft.mssql` - Logs for the mssql extension, which contains much of the core logic for MSSQL-related features
69
+
* sqltools.log is the log for SQL Tools Service
70
+
1.`exthost#/output_logging_#######` - these folders contain the messages displayed in the `Output` panel in Azure Data Studio. Each file is named `#-<Channel Name>` so for example the `Notebooks` output channel may output to a file named `3-Notebooks.log`.
71
+
72
+
If you are asked to provide logs, zip up the entire folder to ensure that the correct logs are included.
73
+
74
+
## Next Steps
75
+
-[Report an issue](https://github.com/Microsoft/azuredatastudio/issues)
76
+
-[What is Azure Data Studio](what-is-azure-data-studio.md)
Copy file name to clipboardExpand all lines: docs/big-data-cluster/deploy-openshift.md
+18-50Lines changed: 18 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Deploy on OpenShift
3
3
titleSuffix: SQL Server Big Data Cluster
4
-
description: Learn how to upgrade SQL Server Big Data Clusters on OpenShift.
4
+
description: Learn how to upgrade SQL Server Big Data Clusters on OpenShift.
5
5
author: mihaelablendea
6
6
ms.author: mihaelab
7
7
ms.reviewer: mikeray
@@ -32,7 +32,7 @@ This article outlines deployment steps that are specific to the OpenShift platfo
32
32
> [!IMPORTANT]
33
33
> Below pre-requisites must be performed by a OpenShift cluster admin (cluster-admin cluster role) that has sufficient permissions to create these cluster level objects. For more information on cluster roles in OpenShift see [Using RBAC to define and apply permissions](https://docs.openshift.com/container-platform/4.4/authentication/using-rbac.html).
34
34
35
-
1. Ensure the `pidsLimit` setting on the OpenShift is updated to accommodate SQL Server workloads. The default value in OpenShift is too low for production like workloads. We recommend a value of at least `4096`, but the optimal value will depend of the `max worker threads` setting in SQL Server and the number of CPU processors on the OpenShift host node.
35
+
1. Ensure the `pidsLimit` setting on the OpenShift is updated to accommodate SQL Server workloads. The default value in OpenShift is too low for production like workloads. Start with at least `4096`, but the optimal value depends the `max worker threads` setting in SQL Server and the number of CPU processors on the OpenShift host node.
36
36
- To find out how to update `pidsLimit` for your OpenShift cluster use [these instructions](https://github.com/openshift/machine-config-operator/blob/master/docs/ContainerRuntimeConfigDesign.md). Note that OpenShift versions before `4.3.5` had a defect causing the updated value to not take effect. Make sure you upgrade OpenShift to the latest version.
37
37
- To help you compute the optimal value depending on your environment and planned SQL Server workloads, you can use the estimation and examples below:
38
38
@@ -44,7 +44,13 @@ This article outlines deployment steps that are specific to the OpenShift platfo
44
44
> [!NOTE]
45
45
> Other processes (e.g. backups, CLR, Fulltext, SQLAgent) also add some overhead, so add a buffer to the estimated value.
46
46
47
-
2. Create a custom security context constraint (SCC) using the attached [`bdc-scc.yaml`](#bdc-sccyaml-file).
47
+
1. Download the custom security context constraint (SCC) [`bdc-scc.yaml`](#bdc-sccyaml-file):
For a deployment on ARO, we recommend to start with one of the `aro-` profiles, that includes default values for `serviceType` and `storageClass` appropriate for this environment. For example:
108
+
For a deployment on ARO, start with one of the `aro-` profiles, that includes default values for `serviceType` and `storageClass` appropriate for this environment. For example:
Copy file name to clipboardExpand all lines: docs/big-data-cluster/release-notes-big-data-cluster.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,8 +108,10 @@ This release includes minor fixes and enhancements. The following articles inclu
108
108
-[Manage big data cluster access in Active Directory mode](manage-user-access.md)
109
109
-[Deploy [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)] in Active Directory mode](active-directory-deploy.md)
110
110
-[Deploy [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)] on AKS in Active Directory mode](active-directory-deployment-aks.md)
111
-
-[Deploy [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)] with high availability](deployment-high-availability.md)
The <xref:System.Data.Common.DbDataAdapter.Fill%2A> method of the <xref:Microsoft.Data.SqlClient.SqlDataAdapter> fills a <xref:System.Data.DataSet> only with table columns and rows from a data source; though constraints are commonly set by the data source, the **Fill** method does not add this schema information to the **DataSet** by default.
23
+
24
+
To populate a **DataSet** with existing primary key constraint information from a data source, you can either call the <xref:System.Data.Common.DbDataAdapter.FillSchema%2A> method of the **DataAdapter**, or set the <xref:System.Data.Common.DataAdapter.MissingSchemaAction%2A> property of the **DataAdapter** to **AddWithKey** before calling **Fill**. This will ensure that primary key constraints in the **DataSet** reflect those at the data source.
25
+
26
+
> [!NOTE]
27
+
> Foreign key constraint information is not included and must be created explicitly.
28
+
29
+
Adding schema information to a **DataSet** before filling it with data ensures that primary key constraints are included with the <xref:System.Data.DataTable> objects in the **DataSet**. As a result, when additional calls to fill the **DataSet** are made, the primary key column information is used to match new rows from the data source with current rows in each **DataTable**, and current data in the tables is overwritten with data from the data source. Without the schema information, the new rows from the data source are appended to the **DataSet**, resulting in duplicate rows.
30
+
31
+
> [!NOTE]
32
+
> If a column in a data source is identified as auto-incrementing, the <xref:System.Data.Common.DbDataAdapter.FillSchema%2A> method, or the <xref:System.Data.Common.DbDataAdapter.Fill%2A> method with a <xref:System.Data.Common.DataAdapter.MissingSchemaAction%2A> of **AddWithKey**, creates a **DataColumn** with an **AutoIncrement** property set to `true`. However, you will need to set the **AutoIncrementStep** and **AutoIncrementSeed** values yourself.
33
+
34
+
> [!NOTE]
35
+
> Using **FillSchema** or setting the **MissingSchemaAction** to **AddWithKey** requires extra processing at the data source to determine primary key column information. This additional processing can hinder performance. If you know the primary key information at design time, we recommend that you explicitly specify the primary key column or columns in order to achieve optimal performance.
36
+
37
+
The following code example shows how to add schema information to a **DataSet** using <xref:System.Data.Common.DbDataAdapter.FillSchema%2A>:
The following code example shows how to add schema information to a **DataSet** using the <xref:System.Data.Common.DataAdapter.MissingSchemaAction%2A> property and the <xref:System.Data.Common.DbDataAdapter.Fill%2A> method:
If the **DataAdapter** meets multiple result sets returned from the <xref:Microsoft.Data.SqlClient.SqlDataAdapter.SelectCommand%2A>, it will create multiple tables in the **DataSet**. The tables will be given a zero-based incremental default name of **Table***N*, starting with **Table** instead of "Table0". The tables will be given a zero-based incremental name of **TableName***N*, starting with **TableName** instead of "TableName0" if a table name is passed as an argument to the <xref:System.Data.Common.DbDataAdapter.FillSchema%2A> method.
48
+
49
+
## See also
50
+
51
+
-[DataAdapters and DataReaders](dataadapters-datareaders.md)
52
+
-[Retrieving and modifying data in ADO.NET](retrieving-modifying-data.md)
53
+
-[Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)
0 commit comments