The term 'test.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
When running a script like
./Test.ps1 the script is expected to be in the current working directory (
Depending on the environment from which you're executing that statement the working directory may not be what you expect, though.
Here are some commands that allow you to determine the current working directory when run the same way as your script:
$PWD.Path (Get-Location).Path (Resolve-Path '.').Path
There are basically 3 ways to deal with the issue:
- Specify the path to your PowerShell script relative to the current working directory.
Change the current working directory to the location of the PowerShell script:
Push-Location 'C:\temp\folder' .\Test.ps1 Pop-Location
Run the PowerShell script with its full path:
If the executable's filename, path, or pathname doesn't contain spaces, using the call (&) operator is optional. Otherwise, the call operator is required.
performance object: SQLServer database
Microsoft Windows Server 2008 and 2008 R2 Maximum Memory Limits
|Version||Maximum Memory Limit (x64 Only)|
|Windows Server 2008 R2 Datacenter||
|Windows Server 2008 R2 Enterprise||2TB|
|Windows Server 2008 R2 for Itanium||2TB|
|Windows Server 2008 R2 Foundation||8GB|
|Windows Server 2008 R2 Standard||32GB|
|Windows Web Server 2008 R2||32GB|
|Version||Max Memory Limit (x32)||Max Memory Limit (x64)|
|Windows Server 2008 Datacenter||64GB||2TB|
|Windows Server 2008 Enterprise||64GB||2TB|
|Windows Server 2008 Standard||4GB||32GB|
|Windows Small Business Server 2008||4GB||32GB|
|Windows Web Server 2008||4GB||32GB|