Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit e8714de

Browse files
authored
Updates
DMV tool will not be ready for CPT1
1 parent 54d45ba commit e8714de

1 file changed

Lines changed: 25 additions & 54 deletions

File tree

docs/linux/sql-server-linux-dmv-tool.md

Lines changed: 25 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,17 @@
11
---
22
# required metadata
33

4-
title: Monitor SQL Server on Linux with dmvtool - SQL Server vNext CTP1 | Microsoft Docs
5-
description: This topic describes how to monitor SQL Server running on Linux with the dmvtool.
4+
title: Monitor SQL Server on Linux with dmvtool | SQL Server vNext CTP1
5+
description:
66
author: rothja
77
ms.author: jroth
88
manager: jhubbard
9-
ms.date: 11/08/2016
9+
ms.date: 10-19-2016
1010
ms.topic: article
11-
ms.prod: sql-linux
12-
ms.technology: database-engine
13-
ms.assetid: 2856cc89-d35b-4030-b12e-4c4ff9240706
11+
ms.prod: sql-non-specified
12+
ms.service:
13+
ms.technology:
14+
ms.assetid:
1415

1516
# optional metadata
1617

@@ -37,46 +38,14 @@ DMVTool uses the FUSE file system module to create two zero byte files for each
3738
> [!NOTE]
3839
> Viewing the contents of DMVs in JSON format is only available when connected to a SQL Server 2016 or higher version of SQL Server. DMVTool can connect to local SQL Servers running on Linux and remote SQL Servers running on Windows or Linux. For now, DMVTool is only a Linux-based tool.
3940
40-
## Installing DMVTool
41+
## 1. Install DMVTool
4142

42-
### To install on Ubuntu
43-
44-
$ sudo apt-get install dmvtool
45-
46-
> [!NOTE]
47-
> This assumes that you have already configured your server to install the mssql-tools package. If you have not done that already, please see the Installation Guide for instructions on doing that first.
48-
49-
### To install on Red Hat Enterprise Linux (RHEL)
50-
51-
Configure the tools repo:
52-
53-
$ cd/etc/yum.repos.d
54-
$ cp private-repo.microsoft.com.repo private-tools-repo.microsoft.com.repo
55-
$ vi private-tools-repo.microsoft.com.repo
56-
57-
Change **mssql-private-preview** in the first **three** lines to **mssql-tools-private-preview**.
58-
59-
The private-tools-repo.microsoft.com.repo file should look like:
60-
61-
\[mssql-**tools**-private-preview\]
62-
name=mssql-**tools**-private-preview
63-
baseurl=https://private-repo.microsoft.com/rhel7/mssql-**tools**-private-preview/
64-
enabled=1
6543

66-
gpgcheck=1
67-
68-
gpgkey=https://private-repo.microsoft.com/keys/dpgswdist.v1.asc
69-
70-
sslclientcert=/etc/sslyum/client.private-repo.microsoft.com.pem
71-
sslclientkey=/et/ssl/yum/client.private-repo.microsoft.com.pem
72-
73-
Install
74-
75-
$ sudo yum update
76-
77-
$ sudo yum install dmvtool
44+
TODO: Find Install steps for Public Preview
45+
### To install on RHEL
46+
### To install on Ubuntu
7847

79-
## Configuring and Running DMVTool
48+
## 2. Configure DMVTool
8049

8150
The DMV tool needs a config file and an empty directory to mount and create the virtual files in. The config file allows you to specify the hostname, username, password (optionally), and SQL Server version for all the servers you want to manage using DMVTool. The version attribute needs to be 14 (SQL Server 2014) or 16 (SQL Server 2016 or higher).
8251

@@ -86,16 +55,16 @@ The DMV tool needs a config file and an empty directory to mount and create the
8655

8756
$ mkdir dmv
8857

89-
1. Create a file to store the configuration
58+
3. Create a file to store the configuration
9059

9160
$ touch dmvtool.config
9261

93-
1. Edit the config file using an editor like VI
62+
4. Edit the config file using an editor like VI
9463

95-
$ vi dmvtool.config
64+
$ vi dmvtool.config
9665

9766
The config file should be in the following format:
98-
\[server friendlyname\]
67+
[server friendlyname]
9968
hostname=<HOSTNAME>
10069
username=<USERNAME>
10170
password=<PASSWORD>
@@ -109,21 +78,21 @@ names.
10978

11079
Example:
11180

112-
\[server1\]
81+
[server1]
11382
hostname= 10.82.164.188
11483
username=sa
11584
password=password1
11685
version=16
11786

118-
\[server2\]
87+
[server2]
11988
hostname= 10.82.164.127
12089
username=sa
12190
password=password2
12291
version=16
12392

124-
### To run the DMVTool
93+
## 3. Run DMVTool
12594

126-
dmvtool -c ./\[Config File\] -m ./\[Mount Directory\]
95+
dmvtool -c ./[Config File] -m ./[Mount Directory]
12796

12897
Example:
12998

@@ -138,20 +107,22 @@ Example:
138107

139108
You should see the list of your server friendly names.
140109

141-
$ cd <server friendly name>
110+
$ cd <server friendly name>
142111
$ ls
143112

144113
You should see the list of DMVs as files. Look at the contents of one of the files:
145114

146-
$ more &lt;dmv file name&gt;
115+
$ more <dmv file name>
147116

148117
You can pipe the output from DMVTool to tools like [*cut*](https://en.wikipedia.org/wiki/Cut_(Unix)) (CSV) and [*jq*](https://stedolan.github.io/jq/) (JSON) to format the data for better readability.
149118

119+
## 4. Stop DMVtool
120+
150121
By default, DMVTool runs in background. You can shut it down using the following commands:
151122

152123
ps -A | grep dmvtool
153124

154-
kill -2 &lt;dmvtool pid&gt;
125+
kill -2 <dmvtool pid>;
155126

156127
If you want to run it in the foreground you can pass the -f parameter. You can pass the -v parameter for verbose output if you are running the tool in the foreground.
157128

0 commit comments

Comments
 (0)