Enter A for "Yes to All" for the execution policy change.
Note
The time to collect this script on a given system may vary. It depends on system speed, system size, the number of virtual machines, the amount of data in logs, and so on. Depending on these factors, the average collection time is between 30 and 90 minutes, or even longer, especially if no skip commands are used.
The collection is stored in a compressed file in the C:\MS_DATA folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
Optional parameters
Some parameters are optional to perform a quicker and more streamlined collection, which may help the script finish successfully if a certain section stops responding.
This cmdlet skips running the Best Practices Analyzer and makes the collection faster.
PowerShell
.\TSS.ps1 -SDP SQLbase -SkipSDPList skipBPA
This cmdlet skips some small collection items that may fail in a regular collection and makes the script more reliable.
PowerShell
.\TSS.ps1 -SDP SQLbase -SkipSDPList skipHang
This cmdlet skips some additional collection parameters that may not be needed.
PowerShell
.\TSS.ps1 -SDP SQLbase -SkipSDPList skipTS
This cmdlet skips testing Server Message Block (SMB) connectivity to any Cluster Shared Volumes (CSVs) in the failover cluster.
PowerShell
.\TSS.ps1 -SDP SQLbase -SkipSDPList skipCsvSMB
Note
You can combine multiple skip parameters with comma-separated items, such as the following example:
Administer an SQL Server database infrastructure for cloud, on-premises and hybrid relational databases using the Microsoft PaaS relational database offerings.