edit more broken links - deploy-notebooks

markingmyname · markingmyname · commit deaf4f91ccb6 · 2020-03-24T07:45:57.000-05:00
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -16588,7 +16588,7 @@
     {
       "source_path": "docs/big-data-clusters/notebooks-guidance.md",
       "redirect_url": "/sql/azure-data-studio/notebooks-guidance.md",
-      "redirect_document_id": false
+      "redirect_document_id": true
     },
     {
       "source_path": "docs/azure-data-studio/sql-notebooks.md.md",
@@ -16598,17 +16598,27 @@
     {
       "source_path": "docs/big-data-clusters/tutorial-notebook-spark.md",
       "redirect_url": "/sql/big-data-clusters/notebooks-tutorial-spark.md",
-      "redirect_document_id": false
+      "redirect_document_id": true
     },
     {
       "source_path": "docs/big-data-clusters/deploy-notebooks.md",
       "redirect_url": "/sql/big-data-clusters/notebooks-deploy.md",
-      "redirect_document_id": false
+      "redirect_document_id": true
     },
     {
       "source_path": "docs/big-data-clusters/manage-notebooks.md",
       "redirect_url": "/sql/big-data-clusters/notebooks-manage.md",
-      "redirect_document_id": false
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/big-data-clusters/manage-notebooks.md",
+      "redirect_url": "/sql/big-data-clusters/notebooks-manage-bdc.md",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/big-data-clusters/notebooks-how-to-manage.md",
+      "redirect_url": "/sql/big-data-clusters/notebooks-manage-bdc.md",
+      "redirect_document_id": true
     }
   ]
 }
diff --git a/docs/azure-data-studio/notebooks-manage-sql-server.md b/docs/azure-data-studio/notebooks-manage-sql-server.md
diff --git a/docs/big-data-cluster/cluster-troubleshooting-commands.md b/docs/big-data-cluster/cluster-troubleshooting-commands.md
@@ -18,7 +18,7 @@ ms.technology: big-data-cluster
 This article describes several useful Kubernetes commands that you can use to monitor and troubleshoot a [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ver15.md)]. It shows how to view in-depth details of a pod or other Kubernetes artifacts that are located in the big data cluster. This article also covers common tasks, such as copying files to or from a container running one of the SQL Server big data cluster services.
 
 > [!TIP]
-> For monitoring status of big data clusters components you can use [**azdata bdc status**](deployment-guidance.md#status) commands or the built-in [troubleshooting notebooks](manage-notebooks.md) in provided with Azure Data Studio.
+> For monitoring status of big data clusters components you can use [**azdata bdc status**](deployment-guidance.md#status) commands or the built-in [troubleshooting notebooks](notebooks-manage.md) in provided with Azure Data Studio.
 
 > [!TIP]
 > Run the following **kubectl** commands on either a Windows (cmd or PS) or Linux (bash) client machine. They require previous authentication in the cluster and a cluster context to run against. For example, for a previously created AKS cluster you can run `az aks get-credentials --name <aks_cluster_name> --resource-group <azure_resource_group_name>` to download the Kubernetes cluster configuration file and set the cluster context.
diff --git a/docs/big-data-cluster/deploy-get-started.md b/docs/big-data-cluster/deploy-get-started.md
@@ -50,7 +50,7 @@ Other tools are required for different scenarios. Each article should explain th
 
 Big data clusters are deployed as a series of interrelated containers that are managed in [Kubernetes](https://kubernetes.io/docs/home). You can host Kubernetes in a variety of ways. Even if you already have an existing Kubernetes environment, you should review the related requirements for big data clusters.
 
-- **Azure Kubernetes Service (AKS)**: AKS allows you to deploy a managed Kubernetes cluster in Azure. You only manage and maintain the agent nodes. With AKS, you don't have to provision your own hardware for the cluster. It is also easy to use a [python script](quickstart-big-data-cluster-deploy.md) or a [deployment notebook](deploy-notebooks.md) to create the AKS cluster and deploy the big data cluster in one step. For more information about configuring AKS for a big data cluster deployment, see [Configure Azure Kubernetes Service for [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ver15.md)] deployments](deploy-on-aks.md).
+- **Azure Kubernetes Service (AKS)**: AKS allows you to deploy a managed Kubernetes cluster in Azure. You only manage and maintain the agent nodes. With AKS, you don't have to provision your own hardware for the cluster. It is also easy to use a [python script](quickstart-big-data-cluster-deploy.md) or a [deployment notebook](notebooks-deploy.md) to create the AKS cluster and deploy the big data cluster in one step. For more information about configuring AKS for a big data cluster deployment, see [Configure Azure Kubernetes Service for [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ver15.md)] deployments](deploy-on-aks.md).
 
 - **Multiple machines**: You can also deploy Kubernetes to multiple Linux machines, which could be physical servers or virtual machines. The [kubeadm](https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/) tool can be used to create the Kubernetes cluster. You can use a [bash script](deployment-script-single-node-kubeadm.md) to automate this type of deployment. This method works well if you already have existing infrastructure that you want to use for your big data cluster. For more information about using **kubeadm** deployments with big data clusters, see [Configure Kubernetes on multiple machines for [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ver15.md)] deployments](deploy-with-kubeadm.md).
 
@@ -78,7 +78,7 @@ The following deployment scripts are currently available:
 
 You can also deploy a big data cluster by running an Azure Data Studio notebook. For more information on how to use a notebook to deploy on AKS, see the following article:
 
-- [Deploy a big data cluster with Azure Data Studio Notebooks](deploy-notebooks.md).
+- [Deploy a big data cluster with Azure Data Studio Notebooks](notebooks-deploy.md).
 
 ## Next steps
 
diff --git a/docs/big-data-cluster/deploy-on-aks.md b/docs/big-data-cluster/deploy-on-aks.md
@@ -23,7 +23,7 @@ AKS makes it simple to create, configure, and manage a cluster of virtual machin
 This article describes the steps to deploy Kubernetes on AKS using Azure CLI. If you don't have an Azure subscription, create a free account before you begin.
 
 > [!TIP]
-> You can also script the deployment of AKS and a big data cluster in one step. For more information, see how to do this in a [python script](quickstart-big-data-cluster-deploy.md) or an Azure Data Studio [notebook](deploy-notebooks.md).
+> You can also script the deployment of AKS and a big data cluster in one step. For more information, see how to do this in a [python script](quickstart-big-data-cluster-deploy.md) or an Azure Data Studio [notebook](notebooks-deploy.md).
 
 ## Prerequisites
 
diff --git a/docs/big-data-cluster/deployment-guidance.md b/docs/big-data-cluster/deployment-guidance.md
@@ -49,7 +49,7 @@ You can choose to deploy Kubernetes in any of three ways:
 | **Single or Multiple machines (`kubeadm`)** | A Kubernetes cluster deployed on physical or virtual machines using `kubeadm` | [Instructions](deploy-with-kubeadm.md) |
 
 > [!TIP]
-> You can also script the deployment of AKS and a big data cluster in one step. For more information, see how to do this in a [python script](quickstart-big-data-cluster-deploy.md) or an Azure Data Studio [notebook](deploy-notebooks.md).
+> You can also script the deployment of AKS and a big data cluster in one step. For more information, see how to do this in a [python script](quickstart-big-data-cluster-deploy.md) or an Azure Data Studio [notebook](notebooks-deploy.md).
 
 ### Verify Kubernetes configuration
 
diff --git a/docs/big-data-cluster/notebooks-deploy.md b/docs/big-data-cluster/notebooks-deploy.md
@@ -40,7 +40,7 @@ In addition to above, deploying SQL Server 2019 big data cluster also requires:
 
 2. On the **Connections** tab, select the ellipses (**...**), then select **Deploy SQL Server...**.
 
-   ![Deploy SQL Server](media/deploy-notebooks/deploy-notebooks.png)
+   ![Deploy SQL Server](media/notebooks-deploy/notebooks-deploy.png)
 
 3. From the deployment options, select **SQL Server Big Data Cluster**.
 
@@ -60,32 +60,32 @@ You can customize the settings of the deployment profile by following the instru
 
 Select the target configuration template from the available templates. The available profiles are filtered depending on the type of deployment target that's chosen in the previous dialog.
 
-   ![Deployment configuration template Step 1](media/deploy-notebooks/deployment-configuration-template.png)
+   ![Deployment configuration template Step 1](media/notebooks-deploy/deployment-configuration-template.png)
 
 ### Azure settings
 
 If the deployment target is a new AKS, additional information such as Azure Subscription ID, resource group, AKS cluster name, VM count, size, and other additional information are required to create the AKS cluster.
 
-   ![Azure settings](media/deploy-notebooks/azure-settings.png)
+   ![Azure settings](media/notebooks-deploy/azure-settings.png)
 
 If the deployment target is an existing Kubernetes cluster, the wizard prompts for the path to the *kube* config file to import the Kubernetes cluster settings. Ensure the appropriate cluster context is selected where the SQL Server 2019 Big Data Cluster can be deployed.
 
-   ![Target cluster context](media/deploy-notebooks/target-cluster-context.png)
+   ![Target cluster context](media/notebooks-deploy/target-cluster-context.png)
 
 ### Cluster, docker, and AD settings
 
 1. Enter the cluster name for the SQL Server 2019 BDC, admin username, and password.
 Note: The same account is used for controller and SQL Server.
 
-   ![Cluster settings](media/deploy-notebooks/cluster-settings.png)
+   ![Cluster settings](media/notebooks-deploy/cluster-settings.png)
 
 2. Enter the Docker settings as appropriate
 
-   ![Docker settings](media/deploy-notebooks/docker-settings.png)
+   ![Docker settings](media/notebooks-deploy/docker-settings.png)
 
 3. If the AD authentication is available, enter the AD settings
 
-   ![Active Directory settings](media/deploy-notebooks/active-directory-settings.png)
+   ![Active Directory settings](media/notebooks-deploy/active-directory-settings.png)
 
 ### Service settings
 
@@ -97,21 +97,21 @@ Enter the number of instances of each of the components in the big data cluster.
 
 A Spark Instance can be included along with HDFS. It's included in the storage pool or on its own in the Spark pool.
 
-   ![Service settings](media/deploy-notebooks/service-settings.png)
+   ![Service settings](media/notebooks-deploy/service-settings.png)
 
 For additional information on each of these components, you can refer to [master instance](concept-master-instance.md), [data pool](concept-data-pool.md), [storage pool](concept-storage-pool.md), or [compute pool](concept-compute-pool.md).
 
 #### Endpoint settings
 
 The default endpoints have been pre-filled. However, they can be changed as appropriate.
 
-   ![Endpoint settings](media/deploy-notebooks/endpoint-settings.png)
+   ![Endpoint settings](media/notebooks-deploy/endpoint-settings.png)
 
 #### Storage settings
 
 The storage settings include storage class and claim size for Data and Logs. The settings can be applied across Storage, Data, and SQL Server master pool.
 
-   ![Storage settings](media/deploy-notebooks/storage-settings.png)
+   ![Storage settings](media/notebooks-deploy/storage-settings.png)
 
 #### Advanced storage settings
 
@@ -121,13 +121,13 @@ You can add additional storage settings under **Advanced storage settings**
 * Data pool
 * SQL Server Master
 
-   ![Advanced storage settings](media/deploy-notebooks/advanced-storage-settings.png)
+   ![Advanced storage settings](media/notebooks-deploy/advanced-storage-settings.png)
 
 ### Summary
 
 This screen summarizes all the input that was provided to deploy SQL Server 2019 Big Data Cluster. The config files can be downloaded via the **Save config files** button. Select **Script to Notebook** to script out the entire deployment configuration to a Notebook. Once the Notebook is open, select **Run Cells** to start deploying the SQL Server 2019 BDC to the selected target.
 
-   ![Summary](media/deploy-notebooks/deploy-sql-server-big-data-cluster-on-a-new-AKS-cluster.png)
+   ![Summary](media/notebooks-deploy/deploy-sql-server-big-data-cluster-on-a-new-AKS-cluster.png)
 
 ## Next steps
 
diff --git a/docs/big-data-cluster/notebooks-how-to-manage.md b/docs/big-data-cluster/notebooks-how-to-manage.md
diff --git a/docs/big-data-cluster/notebooks-manage-bdc.md b/docs/big-data-cluster/notebooks-manage-bdc.md
@@ -38,32 +38,58 @@ In addition to those prerequisites, to deploy SQL Server 2019 Big Data Clusters,
 * [Azure CLI](/cli/azure/install-azure-cli)
 
 ## Access troubleshooting notebooks
+
 There are three ways to access troubleshooting notebooks.
 
 ### Command Palette
+
 1. Select **View** > **Command Palette**.
+
 2. Enter **Jupyter Books: SQL Server 2019 Guide**.
 
 The Jupyter Books viewlet with the Jupyter Book that contains the troubleshooting notebooks related to SQL Server Big Data Clusters will open.
 
 ### SQL Master Dashboard
+
 1. After you install Azure Data Studio Insiders, connect to a SQL Server Big Data Clusters instance.
+
 2. After you're connected to the instance, right-click your server name under **CONNECTIONS** and select **Manage**.
+
 3. In the dashboard, select **SQL Server Big Data Cluster**. Select **SQL Server 2019 guide** to open the Jupyter Book that contains the notebooks you need.
     ![Jupyter notebooks in the dashboard](media/manage-notebooks/jupyter-book-button.png)
 
-1. Select the notebook for the task that you need to complete.
+4. Select the notebook for the task that you need to complete.
 
 ### Controller Dashboard
+
 1. In the **Connections** view, expand **SQL Server Big Data Clusters**.
+
 2. Add controller endpoint details.
+
 3. After you're connected to the controller, right-click the endpoint and select **Manage**.
+
 4. After the dashboard loads, select **troubleshoot** to open the Jupyter Book troubleshooting guides.
 
 ## Use troubleshooting notebooks
+
 1. Find the troubleshooting guide that you need in the Jupyter Book table of contents.
-1. The notebooks are optimized, so you just need to select **Run Cells**. This action will run each cell in the notebook individually until the notebook is complete.
-1. If an error is found, the Jupyter Book will suggest a notebook that you can run to fix the error. Follow the recommended steps, and then run the notebook again.
+
+2. The notebooks are optimized, so you just need to select **Run Cells**. This action will run each cell in the notebook individually until the notebook is complete.
+
+3. If an error is found, the Jupyter Book will suggest a notebook that you can run to fix the error. Follow the recommended steps, and then run the notebook again.
+
+## Change the big data cluster
+
+To change the SQL Server big data cluster for a notebook:
+
+1. Click the **Attach to** menu from the notebook toolbar.
+
+   ![Click the Attach to menu in the notebook toolbar](./media/notebooks-how-to-manage/select-attach-to-1.png)
+
+2. Click a server from the **Attach to** menu.
+
+   ![Select a server from the Attach to menu](./media/notebooks-how-to-manage/select-attach-to-2.png)
 
 ## Next steps
+
 For more information about notebooks in Azure Data Studio, see [How to use notebooks with SQL Server](../azure-data-studio/notebooks-guidance.md).
diff --git a/docs/toc.yml b/docs/toc.yml
@@ -196,7 +196,7 @@
       - name: Kubernetes troubleshooting
         href: big-data-cluster/cluster-troubleshooting-commands.md
       - name: Manage with notebook
-        href: big-data-cluster/manage-notebooks.md
+        href: big-data-cluster/notebooks-manage.md
       - name: Manage with controller dashboard
         href: big-data-cluster/manage-with-controller-dashboard.md
       - name: Manage existing notebooks

Original file line number	Diff line number	Diff line change
`@@ -16588,7 +16588,7 @@`
`16588`	`16588`	`{`
`16589`	`16589`	`"source_path": "docs/big-data-clusters/notebooks-guidance.md",`
`16590`	`16590`	`"redirect_url": "/sql/azure-data-studio/notebooks-guidance.md",`
`16591`		`- "redirect_document_id": false`
	`16591`	`+ "redirect_document_id": true`
`16592`	`16592`	`},`
`16593`	`16593`	`{`
`16594`	`16594`	`"source_path": "docs/azure-data-studio/sql-notebooks.md.md",`
`@@ -16598,17 +16598,27 @@`
`16598`	`16598`	`{`
`16599`	`16599`	`"source_path": "docs/big-data-clusters/tutorial-notebook-spark.md",`
`16600`	`16600`	`"redirect_url": "/sql/big-data-clusters/notebooks-tutorial-spark.md",`
`16601`		`- "redirect_document_id": false`
	`16601`	`+ "redirect_document_id": true`
`16602`	`16602`	`},`
`16603`	`16603`	`{`
`16604`	`16604`	`"source_path": "docs/big-data-clusters/deploy-notebooks.md",`
`16605`	`16605`	`"redirect_url": "/sql/big-data-clusters/notebooks-deploy.md",`
`16606`		`- "redirect_document_id": false`
	`16606`	`+ "redirect_document_id": true`
`16607`	`16607`	`},`
`16608`	`16608`	`{`
`16609`	`16609`	`"source_path": "docs/big-data-clusters/manage-notebooks.md",`
`16610`	`16610`	`"redirect_url": "/sql/big-data-clusters/notebooks-manage.md",`
`16611`		`- "redirect_document_id": false`
	`16611`	`+ "redirect_document_id": true`
	`16612`	`+ },`
	`16613`	`+ {`
	`16614`	`+ "source_path": "docs/big-data-clusters/manage-notebooks.md",`
	`16615`	`+ "redirect_url": "/sql/big-data-clusters/notebooks-manage-bdc.md",`
	`16616`	`+ "redirect_document_id": true`
	`16617`	`+ },`
	`16618`	`+ {`
	`16619`	`+ "source_path": "docs/big-data-clusters/notebooks-how-to-manage.md",`
	`16620`	`+ "redirect_url": "/sql/big-data-clusters/notebooks-manage-bdc.md",`
	`16621`	`+ "redirect_document_id": true`
`16612`	`16622`	`}`
`16613`	`16623`	`]`
`16614`	`16624`	`}`