Skip to content

Commit 0aac925

Browse files
authored
Merge pull request MicrosoftDocs#34 from Techwriter40/patch-23
Update Set-SPServerScaleOutDatabaseDataSubRange.md
2 parents 7d7edd0 + 5b63655 commit 0aac925

File tree

1 file changed

+24
-13
lines changed

1 file changed

+24
-13
lines changed

sharepoint/sharepoint-ps/sharepoint/Set-SPServerScaleOutDatabaseDataSubRange.md

Lines changed: 24 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ schema: 2.0.0
77
# Set-SPServerScaleOutDatabaseDataSubRange
88

99
## SYNOPSIS
10-
{{Fill in the Synopsis}}
10+
Creates a subrange for a specified scale-out database.
1111

1212

1313
## SYNTAX
@@ -29,23 +29,27 @@ Set-SPServerScaleOutDatabaseDataSubRange -Database <SPDatabasePipeBind> -IsUpper
2929
```
3030

3131
## DESCRIPTION
32-
{{Fill in the Description}}
32+
This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see [Cmdlet Parameter Sets] (https://msdn.microsoft.com/library/dd878348(VS.85).aspx).
3333

3434

3535
## EXAMPLES
3636

3737
### --------------------EXAMPLE---------------------
3838
```
39-
PS C:\> {{ Add example code here }}
39+
$databases = Get-SPServerScaleOutDatabase -ServiceApplication $serviceApplication
40+
$database = $databases[0]
41+
$state = Get-SPServerScaleOutDatabaseDataState -Database $database
42+
Set-SPServerScaleOutDatabaseDataSubRange -Database $database -Range $state.Range -SubRangePoint $state.Range.RangeEnd -SubRangeMode ReadOnly -IsUpperSubRange $false
43+
4044
```
4145

42-
{{ Add example description here }}
46+
This example creates a read-only subrange that starts from the data range start point and ends at the data range end point on the first scale-out database of the specified service application.
4347

4448

4549
## PARAMETERS
4650

4751
### -ConnectionString
48-
{{Fill ConnectionString Description}}
52+
Specifies the connection string for the scale-out database to create the new data sub-range.
4953

5054

5155
```yaml
@@ -62,7 +66,7 @@ Accept wildcard characters: False
6266
```
6367
6468
### -Database
65-
{{Fill Database Description}}
69+
Specifies the scale-out database to create the data subrange.
6670
6771
6872
```yaml
@@ -79,7 +83,7 @@ Accept wildcard characters: False
7983
```
8084
8185
### -IsUpperSubRange
82-
{{Fill IsUpperSubRange Description}}
86+
Specifies whether to create the data subrange on the upper or lower side of the data range.
8387
8488
8589
```yaml
@@ -96,7 +100,7 @@ Accept wildcard characters: False
96100
```
97101
98102
### -Range
99-
{{Fill Range Description}}
103+
Specifies the expected current range of the scale-out database prior to this operation.
100104
101105
102106
```yaml
@@ -113,7 +117,8 @@ Accept wildcard characters: False
113117
```
114118
115119
### -SubRangeMode
116-
{{Fill SubRangeMode Description}}
120+
121+
117122
118123
119124
```yaml
@@ -130,7 +135,9 @@ Accept wildcard characters: False
130135
```
131136
132137
### -AssignmentCollection
133-
{{Fill AssignmentCollection Description}}
138+
Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
139+
140+
Note: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
134141
135142
136143
```yaml
@@ -164,7 +171,7 @@ Accept wildcard characters: False
164171
```
165172
166173
### -IgnoreSubRangePointOnBoundary
167-
{{Fill IgnoreSubRangePointOnBoundary Description}}
174+
Specifies whether to complete without any errors if the new subrange’s start and end points are the same. If this parameter is specified, no errors are displayed.
168175
169176
170177
```yaml
@@ -181,7 +188,7 @@ Accept wildcard characters: False
181188
```
182189
183190
### -IsAzureDatabase
184-
{{Fill IsAzureDatabase Description}}
191+
Specifies whether the database is hosted on SQL Azure.
185192
186193
187194
```yaml
@@ -198,8 +205,12 @@ Accept wildcard characters: False
198205
```
199206
200207
### -SubRangePoint
201-
{{Fill SubRangePoint Description}}
208+
Specifies the start or end point of the data subrange to be created as defined by the following criteria:
209+
210+
--The start point if the data sub-range is created on the upper side of the data range.
211+
--The end point if the data sub-range is created on the lower side of the data range.
202212
213+
The maximum value is NULL.
203214
204215
```yaml
205216
Type: Byte[]

0 commit comments

Comments
 (0)