Clear-ASAppSqlServicePersistence

Clear-ASAppSqlServicePersistence

Disables SQL Server persistence at the specified scope.

Syntax

Parameter Set: SiteNameAndVirtualPath
Clear-ASAppSqlServicePersistence [-SiteName] <String> [[-VirtualPath] <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]


Detailed Description

This cmdlet removes the sqlWorkflowInstanceStore element from the configuration file associated with the specified scope and adds the <remove name=”sqlWorkflowInstanceStore”> element so that the configuration settings are not inherited from a higher level.

Parameters

-ApplicationObject<ApplicationInfo>

The name of the ApplicationObject, which specifies that the cmdlet will operate on that application. This parameter is used to pipe the output of the Get-ASApplication cmdlet to a cmdlet containing the ApplicationObject parameter.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

true (ByValue)

Accept Wildcard Characters?

-Root

The name of the root application, which specifies that the cmdlet will operate at that scope. If you use the Root parameter, do not use the SiteName, VirtualPath, or Uri parameter.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

-ServiceObject<ServiceInfo>

The name of the ServiceObject, which specifies that the cmdlet will operate on that service. This parameter is typically used to pipe the output of the Get-ASAppService cmdlet to a cmdlet containing the ServiceObject parameter.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

true (ByValue)

Accept Wildcard Characters?

-SiteName<String>

The name of a Web site, as defined in the IIS Connections pane, which specifies that the cmdlet will operate at the scope of that site, or at the scope of an application, virtual directory, or service contained within that site. To the SiteName parameter, you can add the VirtualPath parameter that identifies an application, directory, or service included in the site.

For an application or virtual directory, the virtual path includes the name of the application, as defined in IIS. For a service, the virtual path includes the name of the application, a forward slash, and the name of the .svc file or .xamlx file for the service. The VirtualPath parameter is not necessary for the site scope. The leading "/" character in the virtual path is optional. If you use the SiteName parameter, do not use the Uri parameter.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

-Uri<Uri>

A URI for an IIS site, application, virtual directory, or service, which specifies that the cmdlet will operate at that scope. If you use the Uri parameter, do not use the SiteName parameter or the SiteName and VirtualPath parameter set.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

-VirtualPath<String>

The virtual path for an application, directory, or service, as defined in the IIS Manager Connections pane, which specifies that the cmdlet will operate at the application, virtual directory, or service. You must add the VirtualPath parameter to the SiteName parameter, using SiteName to identify the site that the application, directory, or service is contained within. The leading "/" character in the virtual path is optional.

For an application, the virtual path includes the name of the application, as defined in IIS. For a service, the virtual path includes the name of the application, a forward slash, and the name of the .svc file or .xamlx file for the service. If you use the SiteName and VirtualName parameter set, do not use the Uri parameter.


Aliases

none

Required?

false

Position?

2

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

-Confirm

Prompts you for confirmation before executing the command.


Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WhatIf

Describes what would happen if you executed the command without actually executing the command.


Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

  • None.


Outputs

The output type is the type of the objects that the cmdlet emits.

  • None.


Examples

Example 1

This command disables SQL Server persistence at the root level.


Clear-ASAppSqlServicePersistence –Root

Example 2

This command disables SQL Server persistence at a Web site level.


Clear-ASAppSqlServicePersistence -SiteName "Default Web Site"

Example 3

These commands disable SQL Server persistence at an application level.


Clear-ASAppSqlServicePersistence -SiteName "Default Web Site" -VirtualPath "/SampleService"Get-ASApplication –SiteName “Default Web Site” –VirtualPath “/SampleService” | Clear-ASAppSqlServicePersistence

Example 4

These commands disable SQL Server persistence at a service level.


Clear-ASAppSqlServicePersistence -SiteName "Default Web Site" –VirtualPath "/SampleService/SampleService.xamlx"Get-ASAppService –SiteName “Default Web Site” –VirtualPath “/SampleService/SampleService.xamlx” | Clear-ASAppSqlServicePersistence

Example 5

These commands disable SQL Server persistence at the level specified by the URI.


Clear-ASAppSqlServicePersistence –Uri http://localhostClear-ASAppSqlServicePersistence -Uri http://localhost/SampleService/Clear-ASAppSqlServicePersistence –Uri http://localhost/SampleService/SampleService.xamlx
Show: