If there are dozens, hundreds or more instances, the command line may exceed the maximum number of characters allowed. Using a csv file avoids this limit.
How Has This Been Tested?
Tested using 80+ instances on numerous on prem machines.
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
Hello, Do you have an example of what the CSV file should look like? I want to update documentation as well before I push this through. The script already accepts a comma separated list of server instances
Fixes #163
Description
Allows for supplying a csv file of Host/Instance pairs to avoid calling the CollectSQLProfile.ps1 in a loop.
Related Issue
This project only accepts pull requests related to open issues.
https://github.com/rubrikinc/rubrik-scripts-for-powershell/issues/163
Motivation and Context
If there are dozens, hundreds or more instances, the command line may exceed the maximum number of characters allowed. Using a csv file avoids this limit.
How Has This Been Tested?
Tested using 80+ instances on numerous on prem machines.
Types of changes
What types of changes does your code introduce? Put an
x
in all the boxes that apply:Checklist:
Go over all the following points, and put an
x
in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!