Skip to content

Commit 4db6dcd

Browse files
markingmynamemarkingmyname
committed
Added lines 66-68 in utilirt article
1 parent c67b152 commit 4db6dcd

3 files changed

Lines changed: 85 additions & 79 deletions

File tree

‎docs/ssms/menu-help/properties-window-f1-help-management-studio.md‎

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,7 @@
11
---
22
title: "Properties Window F1 Help (Management Studio)"
3-
ms.custom: seo-lt-2019
4-
ms.date: "01/19/2017"
53
ms.prod: sql
6-
ms.prod_service: "sql-tools"
7-
ms.reviewer: ""
4+
ms.prod_service: sql-tools
85
ms.technology: ssms
96
ms.topic: conceptual
107
f1_keywords:
@@ -21,16 +18,23 @@ helpviewer_keywords:
2118
- "Properties window [SQL Server Management Studio]"
2219
- "SQL Server Management Studio Help [SQL Server], properties window"
2320
ms.assetid: f682ff0d-0161-4b42-a689-26eeb077d9e9
24-
author: "markingmyname"
25-
ms.author: "maghan"
21+
author: markingmyname
22+
ms.author: maghan
23+
ms.reviewer: ""
24+
ms.custom: seo-lt-2019
25+
ms.date: 01/19/2017
2626
---
27+
2728
# Properties Window F1 Help (Management Studio)
29+
2830
[!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW ](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
31+
2932
Use the **Properties** window to view properties of selected elements. You can also use the **Properties** window to view file, project, and solution properties. The **Properties** window is available by clicking **Properties Window** on the **View** menu.
3033

3134
The **Properties** window displays different types of editing fields, depending on the needs of a particular property. Properties shown in gray are read-only.
3235

33-
## Options
36+
## Options
37+
3438
**Object name**
3539
Lists the currently selected object or objects. Only objects from the active editor or designer are visible.
3640

@@ -46,6 +50,6 @@ Displays the properties for an object.
4650
**Description pane**
4751
The description pane appears at the bottom of the **Properties** window and shows the property type and a short description of the property. You can turn the description of the property off and on using the **Description** command on the shortcut menu.
4852

49-
## See Also
50-
[Properties Window in SQL Server Management Studio](../../relational-databases/scripting/use-the-properties-window-in-management-studio.md)
51-
53+
## See Also
54+
55+
- [Properties Window in SQL Server Management Studio](../../relational-databases/scripting/use-the-properties-window-in-management-studio.md)

‎docs/ssms/object/object-explorer.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,5 +44,4 @@ Object Explorer provides a hierarchical user interface to view and manage the ob
4444
|Describes how to connect Object Explorer to an instance of the [!INCLUDE[ssDE](../../includes/ssde_md.md)], [!INCLUDE[ssASnoversion](../../includes/ssasnoversion_md.md)], [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)], and [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)].|[Connect to an Instance From Object Explorer](../../ssms/object/connect-to-an-instance-from-object-explorer.md)|
4545
|Describes how to manage objects represented as nodes in the Object Explorer hierarchy.|[Manage Objects by Using Object Explorer](../../ssms/object/manage-objects-by-using-object-explorer.md)|
4646
|Describes the Object Explorer Details Pane, a tabular view of all of the objects in the server with a user interface to manage them.|[Object Explorer Details Pane](../../ssms/object/object-explorer-details-pane.md)|
47-
|Describes ways to run custom reports in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)].|[Custom Reports in Management Studio](../../ssms/object/custom-reports-in-management-studio.md)|
48-
47+
|Describes ways to run custom reports in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)].|[Custom Reports in Management Studio](../../ssms/object/custom-reports-in-management-studio.md)|

‎docs/ssms/ssms-utility.md‎

Lines changed: 70 additions & 67 deletions
Original file line numberDiff line numberDiff line change
@@ -15,118 +15,121 @@ author: markingmyname
1515
ms.author: maghan
1616
ms.reviewer: ""
1717
ms.custom: seo-lt-2019
18-
ms.date: 08/07/2019
18+
ms.date: 07/24/2020
1919
---
2020

2121
# SSMS Utility
2222

2323
[!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW ](../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
2424

25-
The **Ssms** utility opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)]. If specified, **Ssms** also establishes a connection to a server, and opens queries, scripts, files, projects, and solutions.
25+
The **SSMS** utility opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)]. If specified, **Ssms** also establishes a connection to a server, and opens queries, scripts, files, projects, and solutions.
2626

2727
You can specify files that contain queries, projects, or solutions. Files that contain queries are automatically connected to a server if connection information is provided and the file type is associated with that type of server. For instance, .sql files open a SQL Query Editor window in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)], and .mdx files open an MDX Query Editor window in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)]. **SQL Server Solutions and Projects** open in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)].
2828

2929
> [!NOTE]
3030
> The **Ssms** utility does not run queries. To run queries from the command line, use the **sqlcmd** utility.
31-
31+
3232
## Syntax
33-
34-
```
35-
Ssms
36-
[scriptfile] [projectfile] [solutionfile]
37-
[-S servername] [-d databasename] [-G] [-U username] [-E] [-nosplash] [-log [filename]?] [-?]
38-
```
39-
33+
34+
```syntaxsql
35+
Ssms
36+
[scriptfile] [projectfile] [solutionfile]
37+
[-S servername] [-d databasename] [-G] [-U username] [-E] [-nosplash] [-log [filename]?] [-?]
38+
```
39+
4040
## Arguments
4141

42-
*scriptfile*
43-
Specifies one or more script files to open. The parameter must contain the full path to the files.
44-
45-
*projectfile*
46-
Specifies a script project to open. The parameter must contain the full path to the script project file.
47-
48-
*solutionfile*
49-
Specifies a solution to open. The parameter must contain the full path to the solution file.
50-
42+
*scriptfile*
43+
Specifies one or more script files to open. The parameter must contain the full path to the files.
44+
45+
*projectfile*
46+
Specifies a script project to open. The parameter must contain the full path to the script project file.
47+
48+
*solutionfile*
49+
Specifies a solution to open. The parameter must contain the full path to the solution file.
50+
5151
[**-S** _servername_]
52-
Server name
53-
52+
Server name
53+
5454
[**-d** _databasename_]
55-
Database name
55+
Database name
5656

5757
[**-G**]
5858
Connect using Active Directory Authentication. The type of connection is determined whether **-U** is included.
5959

6060
> [!Note]
6161
> **Active Directory - Universal with MFA support** is not currently supported.
62-
62+
6363
[**-U** _username_]
64-
User name when connecting with 'SQL Authentication'
65-
64+
User name when connecting with 'SQL Authentication'
65+
66+
[**-P** _password_]
67+
Password when connecting with 'SQL Authentication'
68+
6669
[**-E**]
67-
Connect using Windows Authentication
68-
69-
[**-nosplash**]
70-
Prevents [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from displaying the splash screen graphic while opening. Use this option when connecting to the computer running [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] by means of Terminal Services over a connection with a limited bandwidth. This argument is not case-sensitive and may appear before or after other arguments
71-
70+
Connect using Windows Authentication
71+
72+
[**-nosplash**]
73+
Prevents [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from displaying the splash screen graphic while opening. Use this option when connecting to the computer running [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] by means of Terminal Services over a connection with a limited bandwidth. This argument is not case-sensitive and may appear before or after other arguments
74+
7275
[**-log**_[filename]?_]
73-
Logs [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] activity to the specified file for troubleshooting
74-
76+
Logs [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] activity to the specified file for troubleshooting
77+
7578
[**-?**]
76-
Displays command-line help
79+
Displays command-line help
7780

7881
## Remarks
7982

8083
All of the switches are optional and separated by a space except files, which are separated by commas. If you do not specify any switches, **Ssms** opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] as specified in the **Options** settings on the **Tools** menu. For example, if the **Environment/General** page **At startup** option specifies **Open new query window**, **Ssms** opens with a blank Query Editor.
81-
84+
8285
The **-log** switch must appear at the end of the command line, after all, other switches. The filename argument is optional. If a filename is specified, and the file does not exist, the file is created. If the file cannot be created - for example, due to insufficient write access, the log is written to the nonlocalized APPDATA location instead (See below). If the filename argument is not specified, two files are written to the current user's nonlocalized application data folder. The nonlocalized application data folder for SQL Server can be found from the APPDATA environment variable. For example, for SQL Server 2012, the folder is \<system drive>:\Users\\<username\>\AppData\Roaming\Microsoft\AppEnv\10.0\\. The two files are, by default, named ActivityLog.xml and ActivityLog.xsl. The former contains the activity log data, and the latter is an XML style sheet, which provides a more convenient way to view the XML file. Use the following steps to view the log file in your default XML viewer, like Internet Explorer: Click Start, then click Run...", then type "\<system drive>:\Users\\<username\>\AppData\Roaming\Microsoft\AppEnv\10.0\ActivityLog.xml" into the field provided, and then press Enter.
83-
86+
8487
Files that contain queries prompt to be connected to a server if connection information is provided and the file type is associated with that type of server. For instance, .sql files open a SQL Query Editor window in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)], and .mdx files open an MDX Query Editor window in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)]. **SQL Server Solutions and Projects** open in [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)].
8588

8689
The following table maps server types to file extensions.
87-
88-
|Server type|Extension|
89-
|-----------------|---------------|
90+
91+
| Server type | Extension |
92+
|-------------|-----------|
9093
|[!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]|.sql|
9194
|SQL Server Analysis Services|.mdx<br /><br /> .xmla|
9295

9396
## Examples
9497

9598
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt with the default settings:
96-
97-
```
98-
Ssms
99-
```
99+
100+
```
101+
Ssms
102+
```
100103

101104
The following scripts opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt using *Active Directory - Integrated*:
102-
103-
```
104-
Ssms.exe -S servername.database.windows.net -G
105-
```
105+
106+
```
107+
Ssms.exe -S servername.database.windows.net -G
108+
```
106109

107110
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt, with Windows Authentication, with the Code Editor set to the server `ACCTG and the database AdventureWorks2012,` without showing the splash screen:
108-
109-
```
110-
Ssms -E -S ACCTG -d AdventureWorks2012 -nosplash
111-
```
112-
113-
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt, and opens the MonthEndQuery script.
114-
115-
```
116-
Ssms "C:\Documents and Settings\username\My Documents\SQL Server Management Studio Projects\FinanceScripts\FinanceScripts\MonthEndQuery.sql"
117-
```
118-
119-
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt, and opens the NewReportsProject project on the computer named `developer`:
120-
121-
```
122-
Ssms "\\developer\fin\ReportProj\ReportProj\NewReportProj.ssmssqlproj"
123-
```
124-
125-
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt, and opens the MonthlyReports solution:
126-
127-
```
111+
112+
```
113+
Ssms -E -S ACCTG -d AdventureWorks2012 -nosplash
114+
```
115+
116+
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt, and opens the MonthEndQuery script.
117+
118+
```
119+
Ssms "C:\Documents and Settings\username\My Documents\SQL Server Management Studio Projects\FinanceScripts\FinanceScripts\MonthEndQuery.sql"
120+
```
121+
122+
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt, and opens the NewReportsProject project on the computer named `developer`:
123+
124+
```
125+
Ssms "\\developer\fin\ReportProj\ReportProj\NewReportProj.ssmssqlproj"
126+
```
127+
128+
The following script opens [!INCLUDE[ssManStudioFull](../includes/ssmanstudiofull-md.md)] from a command prompt, and opens the MonthlyReports solution:
129+
130+
```
128131
Ssms "C:\solutionsfolder\ReportProj\MonthlyReports.ssmssln"
129-
```
132+
```
130133

131134
## See Also
132135

0 commit comments

Comments
 (0)