fr/Microsoft.SqlServer.Management.PSProvider.dll-Help.xml

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
<?xml version="1.0" encoding="utf-8"?>

<helpItems schema="maml">

<!-- v 1.3.0.36 -->
<command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
<command:details>
<command:name>
                   Decode-SqlName
</command:name>
<maml:description>
<maml:para>Retourne l'identificateur SQL Server d'origine lorsqu'un identificateur encodé dans un format utilisable dans les chemins d'accès PowerShell a été transmis.</maml:para>
</maml:description>
<maml:copyright>
<maml:para></maml:para>
</maml:copyright>
<command:verb>Decode</command:verb>
<command:noun>SqlName</command:noun>
<dev:version></dev:version>
</command:details>
<maml:description>
<maml:para>Retourne l'identificateur SQL Server non encodé lorsqu'un identificateur encodé dans un format utilisable dans les chemins d'accès PowerShell a été transmis. Les identificateurs délimités SQL Server peuvent contenir des caractères spéciaux non pris en charge habituellement dans les noms d'objet PowerShell. Ces caractères étendus doivent être encodés dans leur représentation hexadécimale ou être placés dans une séquence d'échappement à l'aide du caractère `. Certains caractères, par exemple les deux-points (:), ne peuvent pas être placés dans une séquence d'échappement. L'encodage hexadécimal a le format %nn. Decode-SqlName convertit les encodages suivants en les caractères correspondants :    %5C-\    %3A-:    %2E-.    %2F-/   %25-%    %3C-&lt;    %3E-&gt;    %2A-*    %3F-?    %5B-[    %5D-]    %7C-|</maml:para>
</maml:description>
<!-- Cmdlet syntax section-->
<command:syntax>
<command:syntaxItem>
<maml:name>Decode-SqlName</maml:name>
<command:parameter required="true" variableLength="false" globbing="false" pipelineInput="true (ByValue, ByPropertyName)" position="2">
<maml:name>SqlName</maml:name>
<maml:description>
<maml:para>Identificateur SQL Server à reformater.</maml:para>
</maml:description>
<command:parameterValue required="true" variableLength="false">string</command:parameterValue>
</command:parameter>
</command:syntaxItem>
</command:syntax>
<!-- Cmdlet parameter section  -->
<command:parameters>
<command:parameter required="true" variableLength="false" globbing="false" pipelineInput="true (ByValue, ByPropertyName)" position="2">
<maml:name>SqlName</maml:name>
<maml:description>
<maml:para>Identificateur SQL Server à reformater.</maml:para>

</maml:description>
<command:parameterValue required="true" variableLength="false">string</command:parameterValue>
<dev:type>
<maml:name>string</maml:name>
<maml:uri/>
</dev:type>
<dev:defaultValue></dev:defaultValue>
</command:parameter>
</command:parameters>
<!-- Input - Output section-->
<command:inputTypes>
<command:inputType>
<dev:type>
<maml:name>String</maml:name>
<maml:uri/>
<maml:description />
</dev:type>
<maml:description>
<maml:para>
<!-- description  -->

</maml:para>
</maml:description>
</command:inputType>
</command:inputTypes>
<command:returnValues>
<command:returnValue>
<dev:type>
<maml:name>String</maml:name>
<maml:uri />
<maml:description />
</dev:type>   
<maml:description>
<maml:para>
<!-- description  -->

</maml:para>
</maml:description> 
</command:returnValue>
</command:returnValues>
<!-- Error section-->
<command:terminatingErrors />
<command:nonTerminatingErrors />
<!-- Notes section  -->
<maml:alertSet>
<maml:title></maml:title>
<maml:alert>
<maml:para>
                          
                        </maml:para>
</maml:alert>
<maml:alert>
<maml:para></maml:para>
</maml:alert>
</maml:alertSet>
 <!-- Example section  -->
<command:examples>

<command:example>
<maml:title>
-------------------------- EXAMPLE 1 --------------------------
</maml:title> 
<maml:introduction>
<maml:para>C:\PS&gt;</maml:para>
</maml:introduction> 
   <dev:code>
Decode-SqlName -SqlName &quot;My%3ATable`/&quot;

My:Table/                        </dev:code>
        <dev:remarks>
                                <maml:para>Description</maml:para>
                                <maml:para>-----------</maml:para>
           <maml:para>Décode un identificateur SQL Server qui a une représentation hexadécimale encodée pour le caractère :. PowerShell supprime aussi le caractère d'échappement backtip (`) d'un caractère d'échappement /.</maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> </dev:remarks> <command:commandLines> <command:commandLine> <command:commandText></command:commandText> </command:commandLine> </command:commandLines> </command:example> </command:examples> <!-- Link section --> <maml:relatedLinks> <maml:navigationLink> <maml:linkText>SQL Server Books Online: Using SQL Server Identifiers in PowerShell</maml:linkText> <maml:uri/> </maml:navigationLink> <maml:navigationLink> <maml:linkText>Encode-SqlName</maml:linkText> <maml:uri/> </maml:navigationLink> </maml:relatedLinks> </command:command> <!-- v 1.3.0.36 --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name> Encode-SqlName </command:name> <maml:description> <maml:para>Encode les caractères étendus présents dans les noms SQL Server en formats utilisables dans les chemins d'accès PowerShell.</maml:para>
</maml:description>
<maml:copyright>
<maml:para></maml:para>
</maml:copyright>
<command:verb>Encode</command:verb>
<command:noun>SqlName</command:noun>
<dev:version></dev:version>
</command:details>
<maml:description>
<maml:para>Encode les caractères spéciaux présents dans les noms SQL Server en formats utilisables dans les chemins d'accès PowerShell. Les identificateurs délimités SQL Server peuvent contenir des caractères non pris en charge habituellement dans les noms d'objet PowerShell. Lorsque des identificateurs délimités sont utilisés dans des cheminsd'accès de fournisseur SQL Server, ces caractères étendus doivent être encodés dans leur représentation hexadécimale ou être placés dans une séquence d'échappement à l'aide du caractère `. Certains caractères, par exemple les deux-points (:), ne peuvent pas être placés dans une séquence d'échappement. L'encodage hexadécimal des caractères a le format %nn. Les caractères encodés par Encode-SqlName sont : \:./%&lt;&gt;*?[]|</maml:para> </maml:description> <!-- Cmdlet syntax section--> <command:syntax> <command:syntaxItem> <maml:name>Encode-SqlName</maml:name> <command:parameter required="true" variableLength="false" globbing="false" pipelineInput="true (ByValue, ByPropertyName)" position="2"> <maml:name>SqlName</maml:name> <maml:description> <maml:para>Identificateur SQL Server à encoder.</maml:para> </maml:description> <command:parameterValue required="true" variableLength="false">string</command:parameterValue> </command:parameter> </command:syntaxItem> </command:syntax> <!-- Cmdlet parameter section --> <command:parameters> <command:parameter required="true" variableLength="false" globbing="false" pipelineInput="true (ByValue, ByPropertyName)" position="2"> <maml:name>SqlName</maml:name> <maml:description> <maml:para>Identificateur SQL Server à encoder.</maml:para> </maml:description> <command:parameterValue required="true" variableLength="false">string</command:parameterValue> <dev:type> <maml:name>string</maml:name> <maml:uri/> </dev:type> <dev:defaultValue></dev:defaultValue> </command:parameter> </command:parameters> <!-- Input - Output section--> <command:inputTypes> <command:inputType> <dev:type> <maml:name>String</maml:name> <maml:uri/> <maml:description /> </dev:type> <maml:description> <maml:para> <!-- description --> </maml:para> </maml:description> </command:inputType> </command:inputTypes> <command:returnValues> <command:returnValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> <maml:description /> </dev:type> <maml:description> <maml:para> <!-- description --> </maml:para> </maml:description> </command:returnValue> </command:returnValues> <!-- Error section--> <command:terminatingErrors /> <command:nonTerminatingErrors /> <!-- Notes section --> <maml:alertSet> <maml:title></maml:title> <maml:alert> <maml:para> </maml:para> </maml:alert> <maml:alert> <maml:para></maml:para> </maml:alert> </maml:alertSet> <!-- Example section --> <command:examples> <command:example> <maml:title> -------------------------- EXAMPLE 1 -------------------------- </maml:title> <maml:introduction> <maml:para>C:\PS&gt;</maml:para> </maml:introduction> <dev:code> Encode-SqlName -SqlName &quot;My:Table/&quot; My%3ATable%2F </dev:code> <dev:remarks> <maml:para>Description</maml:para> <maml:para>-----------</maml:para> <maml:para>Encode un nom de table SQL Server qui contient les caractères : et /.</maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> </dev:remarks> <command:commandLines> <command:commandLine> <command:commandText></command:commandText> </command:commandLine> </command:commandLines> </command:example> </command:examples> <!-- Link section --> <maml:relatedLinks> <maml:navigationLink> <maml:linkText>SQL Server Books Online: Using SQL Server Identifiers in PowerShell</maml:linkText> <maml:uri/> </maml:navigationLink> <maml:navigationLink> <maml:linkText>Decode-SqlName</maml:linkText> <maml:uri/> </maml:navigationLink> </maml:relatedLinks> </command:command> <!-- v 1.3.0.36 --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name> Convert-UrnToPath </command:name> <maml:description> <maml:para>Convertit un URN d'objet SMO (SQL Server Management Objects) en un chemin d'accès de fournisseur PowerShell SQL Server.</maml:para> </maml:description> <maml:copyright> <maml:para></maml:para> </maml:copyright> <command:verb>Convert</command:verb> <command:noun>UrnToPath</command:noun> <dev:version></dev:version> </command:details> <maml:description> <maml:para>Convertit un URN (Uniform Resource Name) d'objet SMO (SQL Server Management Objects) en un chemin d'accès de fournisseur SQL Server. Les objets SMO (SQL Server Management Objects) ont une propriété Urn qui retourne une chaîne indiquant leur emplacement dans la hiérarchie d'objets SQL Server.  Si des nœuds de l'URN sont des identificateurs délimités SQL Server qui contiennent des caractères étendus non pris en charge dans les nœuds de chemin d'accès PowerShell, ces caractères étendus sont encodés avec leur représentation hexadécimale. Par exemple, un nom de table &quot;My:Table&quot; est encodé sous la forme &quot;My%3ATable&quot;.</maml:para>
</maml:description>
<!-- Cmdlet syntax section-->
<command:syntax>
<command:syntaxItem>
<maml:name>Convert-UrnToPath</maml:name>
<command:parameter required="true" variableLength="false" globbing="false" pipelineInput="true (ByValue, ByPropertyName)" position="named">
<maml:name>Urn</maml:name>
<maml:description>
<maml:para>Chaîne de caractères qui contient un URN (Unique Resource Name) SQL Server.   Un URN SQL Server est une chaîne qui identifie l'emplacement d'un objet dans la hiérarchie SQL Server. Les URN contiennent les mêmes informations qu'un chemin d'accès PowerShell SQL Server, mais dans un format différent. Les objets SMO (SQL Server Management Objects) ont une propriété Urn.</maml:para>
</maml:description>
<command:parameterValue required="true" variableLength="false">string</command:parameterValue>
</command:parameter>
</command:syntaxItem>
</command:syntax>
<!-- Cmdlet parameter section  -->
<command:parameters>
<command:parameter required="true" variableLength="false" globbing="false" pipelineInput="true (ByValue, ByPropertyName)" position="named">
<maml:name>Urn</maml:name>
<maml:description>
<maml:para>Chaîne de caractères qui contient un URN (Unique Resource Name) SQL Server.   Un URN SQL Server est une chaîne qui identifie l'emplacement d'un objet dans la hiérarchie SQL Server. Les URN contiennent les mêmes informations qu'un chemin d'accès PowerShell SQL Server, mais dans un format différent. Les objets SMO (SQL Server Management Objects) ont une propriété Urn.</maml:para>

</maml:description>
<command:parameterValue required="true" variableLength="false">string</command:parameterValue>
<dev:type>
<maml:name>string</maml:name>
<maml:uri/>
</dev:type>
<dev:defaultValue></dev:defaultValue>
</command:parameter>
</command:parameters>
<!-- Input - Output section-->
<command:inputTypes>
<command:inputType>
<dev:type>
<maml:name>String</maml:name>
<maml:uri/>
<maml:description />
</dev:type>
<maml:description>
<maml:para>
<!-- description  -->
Chaîne de caractères qui contient un URN (Unique Resource Name) d'objet SMO (SQL Server Management Objects). </maml:para> </maml:description> </command:inputType> </command:inputTypes> <command:returnValues> <command:returnValue> <dev:type> <maml:name>String</maml:name> <maml:uri /> <maml:description /> </dev:type> <maml:description> <maml:para> <!-- description --> Chaîne de caractères qui contient un chemin d'accès de fournisseur PowerShell SQL Server.
</maml:para>
</maml:description> 
</command:returnValue>
</command:returnValues>
<!-- Error section-->
<command:terminatingErrors />
<command:nonTerminatingErrors />
<!-- Notes section  -->
<maml:alertSet>
<maml:title></maml:title>
<maml:alert>
<maml:para>
                          
                        </maml:para>
</maml:alert>
<maml:alert>
<maml:para></maml:para>
</maml:alert>
</maml:alertSet>
 <!-- Example section  -->
<command:examples>

<command:example>
<maml:title>
-------------------------- EXAMPLE 1 --------------------------
</maml:title> 
<maml:introduction>
<maml:para>C:\PS&gt;</maml:para>
</maml:introduction> 
   <dev:code>
Set-Location SQLSERVER:\SQL\MyComputer\MyInstance\Databases\AdventureWorks2012
Convert-UrnToPath -Urn (Get-Item .).Urn.ToString()

SQLSERVER:\SQL\MyComputer\MyInstance\Databases\AdventureWorks2012                        </dev:code>
        <dev:remarks>
                                <maml:para>Description</maml:para>
                                <maml:para>-----------</maml:para>
           <maml:para>Retourne une chaîne de caractères qui contient le chemin d'accès actuel. L'exemple utilise la fonction ToString() de la propriété Urn SMO pour retourner l'URN sous la forme d'une chaîne de caractères.</maml:para>
                        <maml:para></maml:para>
                        <maml:para></maml:para>
                        <maml:para></maml:para>
                        <maml:para></maml:para>
   </dev:remarks>
<command:commandLines>
<command:commandLine>
<command:commandText></command:commandText>
</command:commandLine>
</command:commandLines>
</command:example>

<command:example>
<maml:title>
-------------------------- EXAMPLE 2 --------------------------
</maml:title> 
<maml:introduction>
<maml:para>C:\PS&gt;</maml:para>
</maml:introduction> 
   <dev:code>
Set-Location ( Convert-UrnToPath -Urn &quot;Server[@Name='MyComputer']/Database[@Name='AdventureWorks']/Table[@Name='Address' and @Schema = 'Person']&quot; )                        </dev:code>
        <dev:remarks>
                                <maml:para>Description</maml:para>
                                <maml:para>-----------</maml:para>
           <maml:para>Définit le chemin d'accès de l'emplacement spécifié dans un URN d'objet SMO (SQL Server Management Objects).</maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> </dev:remarks> <command:commandLines> <command:commandLine> <command:commandText></command:commandText> </command:commandLine> </command:commandLines> </command:example> <command:example> <maml:title> -------------------------- EXAMPLE 3 -------------------------- </maml:title> <maml:introduction> <maml:para>C:\PS&gt;</maml:para> </maml:introduction> <dev:code> Set-Location SQLSERVER:\SQL\MyComputer\DEFAULT\Databases foreach ($Item in Get-ChildItem) { $Item.Urn.ToString() | Convert-UrnToPath} SQLSERVER:\SQL\MyComputer\DEFAULT\Databases\AdventureWorks2012 </dev:code> <dev:remarks> <maml:para>Description</maml:para> <maml:para>-----------</maml:para> <maml:para>Retourne une série de chaînes de caractères qui contiennent chacune le chemin d'accès d'une base de données de l'instance par défaut. Utilise un pipeline pour transmettre l'URN de nœud actuel à Convert-UrnToPath</maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> <maml:para></maml:para> </dev:remarks> <command:commandLines> <command:commandLine> <command:commandText></command:commandText> </command:commandLine> </command:commandLines> </command:example> </command:examples> <!-- Link section --> <maml:relatedLinks> <maml:navigationLink> <maml:linkText>Decode-SqlName</maml:linkText> <maml:uri/> </maml:navigationLink> <maml:navigationLink> <maml:linkText>Encode-SqlName</maml:linkText> <maml:uri/> </maml:navigationLink> </maml:relatedLinks> </command:command> <!-- v 1.3.0.34 --> <providerHelp> <Name> SQLServer </Name> <Drives> <Para>SQLSERVER</Para> </Drives> <Synopsis> Access SQL Server instances and their databases. </Synopsis> <DetailedDescription> <para>The Microsoft SQL Server PowerShell provider lets you manage the configuration of instances of the SQL Server Database Engine and the objects in those instances. The SQL Server PowerShell provider implements separate path hierarchies for different classes of objects that are supported by the SQL Server management object models. The SQL Server PowerShell provider implements one virtual drive named SQLSERVER:. The SQLSERVER: drive has several folders: \SQL, \SQLPolicy, \SQLRegistration, \Utility, \DAC, \DataCollection, \IntegrationServices, and SQLAS. The SQLServer:\SQL folder lets you navigate to instances of the SQL Server Database Engine and manage the objects in the instances, such as logins, tables, functions, jobs, queues, and mail agents. The SQL folder operates using the objects in these namespaces: Microsoft.SqlServer.Management.SMO Microsoft.SqlServer.Management.SMO.Agent Microsoft.SqlServer.Management.SMO.Broker Microsoft.SqlServer.Management.SMO.Mail The SQLSERVER:\SQLPolicy folder lets you navigate to instances of the Database Engine that contains a Policy-Based Management policy store and manage objects such as policies and facets. The SQLPolicy folder operates using the objects in the Microsoft.SqlServer.Management.Dmf and Microsoft.SqlServer.Management.Facets namespaces. The SQLSERVER:\SQLRegistration folder lets you navigate to instances of the Database Engine and manage Registered Server objects such as server groups and registered servers. The SQLRegistration folder operates using the objects in the Microsoft.SqlServer.Management.RegisteredServers and Microsoft.SqlServer.Management.RegSvrEnum namespace. The SQLSERVER:\Utility folder lets you navigate to the managed instances and data-tier applications registered in the SQL Server Utility. The Utility folder operates using the objects in the Microsoft.SqlServer.Management.Utility namespace. The SQLServer:\DAC folder lets you navigage through data-tier applications objects such as DAC package files. The DAC folder operates using the objects in the Microsoft.SqlServer.Management.DAC namespace. The SQLServer:\DataCollection folder lets you navigate to instances of the Database Engine and manage Data Collector objects such as collection sets and configuration stores. The DataCollection folder operates using the objects in the Microsoft.SqlServer.Management.Collector namespace. The SQLServer:\IntegrationServices folder lets you manage SQL Server Integration Services objects such as projects, packages, and environments. The IntegrationServices folder operates using the Microsoft.SqlServer.Management.IntegrationServices namespace. The SQLServer:\SQLAS folders lets you manage SQL Server Analysis Services objects such as aggregations, dimensions, and cubes. The SQLAS folder operates using the Microsoft.AnalysisServices namespace. You can navigate the SQLSERVER: paths by using PowerShell path cmdlets such as Get-Location, Set-Location, and Get-ChildItem. The leading part of a SQLSERVER:\SQL path has the form SQLSERVER:\SQL\ComputerName\InstanceName. You must always specify an instance name, even for default instances. Specify DEFAULT for default instance names. The path nodes following the InstanceName alternate between object classes and object names. Schemas are not represented as an object class. When you specify a path node for top level objects in schemas, such as tables or views, the node name must be in the format SchemaName.ObjectName. For example, this is the path to the AddressID column in the Address table of the Person schema: SQLSERVER:\SQL\MyComputer\DEFAULT\Databases\AdventureWorks\Tables\Person.Address\Columns\AddressID To save typing, you can create your own PowerShell drives that map over the first several nodes of an SQL path. The information that is returned by Get-ChildItem depends on which part of the path the cmdlet is executed from: Returns the local computer name and the list of computers to which you have opened Database Engine connections by using WMI: PS SQLSERVER:\SQL&gt; Get-ChildItem Returns the list of instances on the specified computer: PS SQLSERVER:\SQL\ComputerName&gt; Get-ChildItem Returns the list of top-level object types from the instance, such as Logins and Databases: PS SQLSERVER:\SQL\ComputerName\InstanceName&gt; Get-ChildItem. With the SQL Server PowerShell provider, you manage the objects that are exposed in SQL Server paths by using the SQL Server management object model methods and properties for that class of object. For example, you can use the methods of the Microsoft.SQLServer.Management.SMO.Database class to perform actions such as creating, altering, and dropping databases. You can also use the class properties to query the current state of the objects. Use the Get-Member cmdlet to get a list of the methods and properties that are supported for the various objects. For information about the classes, see the namespace reference sections in the SQL Server Books Online. You cannot select, insert, update, or delete data in tables and views by using the SQL Server PowerShell provider. For example, there is no Select() or Insert() method for tables. Use the Invoke-Sqlcmd cmdlet to access and change the data in tables and views. By default, the SQL Server PowerShell provider opens Windows Authentication connections by using the credentials of the Windows account that is running the PowerShell session. See SQL Server Books Online for information about opening a SQL Server Authentication connection using the provider. In complex databases, the lists returned by Get-ChildItem and the PowerShell tab-completion lists can be very large. You can use three system variables created by the SQL Server PowerShell provider to control the size of these lists: $SqlServerMaximumTabCompletion = n n is an integer that specifies the maximum number of objects in a tab completion list. The default is 0, which means all objects are returned. $SqlServerMaximumChildItems = n n is an integer that specifies the maximum number of objects returned when you run Get-ChildItem on SQL Server path nodes. The default is 0, which means all objects are returned. $SQLServerIncludeSystemObjects = { $True | $False } Specifies whether SQL Server system objects are returned by Get-ChildItem or included in tab-completion lists. The default is $True</para> </DetailedDescription> <Capabilities> <para></para> </Capabilities> <Filters> <para></para> </Filters> <Notes> SQL Server delimited identifiers are object names that are enclosed in brackets ([Table:Name]) or quotation marks (&quot;View&gt;Name&quot;). Delimited identifiers can contain any Unicode character. The special characters in these names must be either encoded to their hexadecimal representation or escaped for use in PowerShell paths. The hexadecimal encoding for characters uses the format %nn. An example of encoding the colon (:)character in the name &quot;Table:Name&quot; is: Set-Location &quot;Table%3AName&quot;. The PowerShell escape character is the back tick (`) character that is typically on the key at the top left of the keyboard. An example of escaping an extended character is as follows: Set-Location &quot;View`&gt;Name&quot; Certain characters, such as the colon character (:), cannot be escaped. They must be encoded. The SQL Server PowerShell provider snapin implements two cmdlets to help encode and decode delimited identifiers: Encode-SqlName and Decode-SqlName. You must supply a registry or directory object for the -Type parameter when using these core cmdlets with a SQLRegistration: drive: Copy-Object, Move-Object, New-Object, Remove-Object, and Rename-Object. </Notes> <Tasks> <Task> <Title> Navigating SQLSERVER:\SQL paths </Title> <Description> <para></para> </Description> <Examples> <Example> <Title> -------------------------- EXAMPLE 1 -------------------------- </Title> <Introduction> <para>This example uses the Set-Location cmdlet to change the path to the SQL folder.</para> </Introduction> <Code> Set-Location SQLSERVER:\SQL </Code> <Remarks> <para></para> </Remarks> </Example> <Example> <Title> -------------------------- EXAMPLE 2 -------------------------- </Title> <Introduction> <para>This example uses Set-Location to change the path to a default instance of the Database Engine</para> </Introduction> <Code> Set-Location SQLSERVER:\SQL\MyComputer\DEFAULT </Code> <Remarks> <para></para> </Remarks> </Example> <Example> <Title> -------------------------- EXAMPLE 3 -------------------------- </Title> <Introduction> <para>This example uses Set-Location to change the path to the AdventureWorks sample database.</para> </Introduction> <Code> Set-Location SQLSERVER:\SQL\MyComputer\MyInstance\Databases\AdventureWorks </Code> <Remarks> <para></para> </Remarks> </Example> </Examples> </Task> <Task> <Title> Build a New PowerShell Drive </Title> <Description> <para></para> </Description> <Examples> <Example> <Title> -------------------------- EXAMPLE 1 -------------------------- </Title> <Introduction> <para>If you are going to do a lot of work in the AdventureWorks database, create a new AWDB: drive to save typing.</para> </Introduction> <Code> New-PSDrive -Name AWDB -Root SQLSERVER:\SQL\MyComputer\DEFAULT\Databases\AdventureWorks -PSProvider SQLServer </Code> <Remarks> <para></para> </Remarks> </Example> </Examples> </Task> <Task> <Title> Get the Methods and Properties of a SQL Server Object </Title> <Description> <para></para> </Description> <Examples> <Example> <Title> -------------------------- EXAMPLE 1 -------------------------- </Title> <Introduction> <para>This command sets a variable to the SMO Database class and then gets a list of the methods and properties supported by the class.</para> </Introduction> <Code> $MyVar = New-Object Microsoft.SqlServer.Management.SMO.Database $MyVar | Get-Member -Type Methods $MyVar | Get-Member -Type Properties </Code> <Remarks> <para></para> </Remarks> </Example> <Example> <Title> -------------------------- EXAMPLE 2 -------------------------- </Title> <Introduction> <para>This command navigates to the database node in an SQL-based path and get s a list of the properties that are supported for databases.</para> </Introduction> <Code> Set-Location SQLSERVER:\SQL\MyComputer\DEFAULT\Databases Get-Item . | Get-Member -Type Properties </Code> <Remarks> <para></para> </Remarks> </Example> </Examples> </Task> <Task> <Title> Filter SQL Server Objects by Using SMO Properties </Title> <Description> <para></para> </Description> <Examples> <Example> <Title> -------------------------- EXAMPLE 1 -------------------------- </Title> <Introduction> <para>This command lists only the tables that are in the AdventureWorks Sales schema.</para> </Introduction> <Code> Set-Location SQLSERVER:\SQL\MyComputer\DEFAULT\Databases\AdventureWorks\Tables Get-ChildItem | WHERE {$_.Schema -eq &quot;Sales&quot;} </Code> <Remarks> <para></para> </Remarks> </Example> </Examples> </Task> <Task> <Title> Generate Scripts That Create SQL Server Objects </Title> <Description> <para></para> </Description> <Examples> <Example> <Title> -------------------------- EXAMPLE 1 -------------------------- </Title> <Introduction> <para>This script creates a Views.sql file that contains the CREATE VIEW statements that are required to recreate all of the views that are defined in AdventureWorks.</para> </Introduction> <Code> Remove_Item c:\PowerShell\Views.sql Set-Location SQLSERVER:\SQL\MyComputer\DEFAULT\Databases\AdventureWorks\Views foreach ($Item in Get-ChildItem) {$Item.Script() | Out-File -Filepath c:\PowerShell\Views.sql -append } </Code> <Remarks> <para></para> </Remarks> </Example> </Examples> </Task> <Task> <Title> Use SMO to Manage SQL Server Objects </Title> <Description> <para></para> </Description> <Examples> <Example> <Title> -------------------------- EXAMPLE 1 -------------------------- </Title> <Introduction> <para>This script uses SMO to create a database and then query its state.</para> </Introduction> <Code> Set-Location SQLSERVER:\SQL\MyComputer\DEFAULT\Databases $MyVar = New-Object Microsoft.SqlServer.Management.SMO.Database $MyVar.Parent = (Get-Item ..) $MyVar.Name = &quot;NewDB&quot; $MyVar.Create() $MyVar.State </Code> <Remarks> <para></para> </Remarks> </Example> </Examples> </Task> <Task> <Title> Controlling SQL Server Objects in Tab-completion and Get-ChildItem </Title> <Description> <para></para> </Description> <Examples> <Example> <Title> -------------------------- EXAMPLE 1 -------------------------- </Title> <Introduction> <para>This script sets the values for the system variables that control the number of SQL Server objects included in tab-completion lists or returned by Get-ChildItem.</para> </Introduction> <Code> $SqlServerMaximumTabCompletion = 20 $SqlServerMaximumChildItems = 10 $SqlServerIncludeSystemObjects = $False dir variable:sqlserver* </Code> <Remarks> <para></para> </Remarks> </Example> </Examples> </Task> </Tasks> <DynamicParameters> <DynamicParameter> <Name></Name> <CmdletSupported></CmdletSupported> <Type> <Name></Name> </Type> <Description></Description> <PossibleValues> <PossibleValue> <Value></Value> <Description> <para></para> </Description> </PossibleValue> </PossibleValues> </DynamicParameter> </DynamicParameters> <RelatedLinks> <navigationLink> <linkText>about_provider</linkText> <uri/> </navigationLink> <navigationLink> <linkText>Encode-SqlName</linkText> <uri/> </navigationLink> <navigationLink> <linkText>Decode-SqlName</linkText> <uri/> </navigationLink> <navigationLink> <linkText>Invoke-Sqlcmd</linkText> <uri/> </navigationLink> <navigationLink> <linkText>New-PSDrive</linkText> <uri/> </navigationLink> <navigationLink> <linkText>Get-Member</linkText> <uri/> </navigationLink> <navigationLink> <linkText>Invoke-PolicyEvaluation</linkText> <uri/> </navigationLink> </RelatedLinks> </providerHelp> </helpItems>