Run the Go​.ps1 script to configure the PI Vision database

The Go.ps1 script is used to create or upgrade your PI Vision database when you are performing a new AVEVA PI Vision installation or a version upgrade. The PI Vision installation program puts the Go.ps1 script in the SQL directory on the application server.

If you use on-premises SQL Server for your PI Vision database, it is recommended that you first attempt to create or upgrade your PI Vision database from the Administration website, before you use the Go.ps1 script. However, if for any reason using the Administration website process is not successful, you can use the Go.ps1 script.

If you use Azure SQL Database or Amazon RDS for SQL Server for your PI Vision database, you must use the Go.ps1 script to create or upgrade your PI Vision database; the Administration website cannot be used to create or upgrade a PI Vision database that is on Azure SQL Database or Amazon RDS for SQL Server.

The steps that you need to follow to run the Go.ps1 script are different depending on what type of database platform you use, and there are different steps depending on your authentication method. For instructions on running the Go.ps1 script, go to the appropriate section below based on your database platform and your authentication method. There are also sections below providing the prerequisites for running the Go.ps1 script with either on-premises SQL Server, Azure SQL Database, or Amazon RDS for SQL Server.

SQL Server prerequisites

The permissions that you need to run the Go.ps1 script against SQL Server are different depending on whether you are using the script to create or upgrade your PI Vision database. For details on the permissions that you need for each supported database platform, refer to Required SQL permissions.

Run the script: SQL Server with Windows authentication

If you use on-premises SQL Server with Windows authentication for your PI Vision database, follow the steps below to run the Go.ps1 script in order to create or upgrade your database.

1. On the AVEVA PI Vision application server, copy the SQL directory.

   This directory is typically located here:

   Program Files/PIPC/PIVision/Admin/SQL

2. On the machine running SQL Server, paste the folder and all its contents to a local directory.

3. On the machine running SQL Server, open Powershell or Powershell ISE as Administrator, navigate to the local directory pasted in step 2, and run the Go.ps1 script.

   Type:

   Note: If any parameter below contains any spaces, enclose it in double quotation marks.

   .\Go.ps1 DBServer DBName PIVisionService LogFile

   where:

   • DBServer is the name of the SQL server.

   • DBName is the name of the AVEVA PI Vision database, which is typically PIVision.

   • PIVisionService is the name of the AVEVA PI Vision service account.

     You need to format PIVisionService according to which type of account you are using:

     PIVisionService account type	Format for PIVisionService
     Domain user	domain\service account name
     Network Service, and SQL Server is not installed on the AVEVA PI Vision application server	Enter the application server computer domain account. Active Directory computer accounts always end in a dollar sign. For example: "domain\computer name$"
     Network Service, and SQL Server is installed locally on the AVEVA PI Vision application server	"NT AUTHORITY\Network Service"

   • LogFile is the file where the script writes log information. This parameter is optional. If specified, the script writes to this file in the directory that contains the Go.ps1 script. If not specified, the script writes to the go_outputfile.log file in the directory defined by the user variable TEMP.

4. After the command completes, open the AVEVA PI Vision Administration website to confirm that AVEVA PI Vision can successfully connect to the SQL database. For details, see Create and configure your PI Vision database.

   Note: If you are performing an upgrade and you are continuing to use the same database, typically you do not need to complete additional steps on the Administration website.

Examples of input parameters for Go.ps1

The following examples demonstrate the use of input parameters with the Go.ps1 script when using on-premises SQL Server with Windows authentication for your PI Vision database

• Default local instance of SQL Server, custom domain account

  .\Go.ps1 .\ PIVision mydomain\PIVisionaccount

  • The AVEVA PI Vision SQL database is named PIVision.

  • The default local instance of SQL Server is used.

  • A custom domain account is used.

• Specific instance of SQL Server, machine account

  .\Go.ps1 sqlserver\sqlinstance PIVision mydomain\PIVisionserver$

  • The AVEVA PI Vision SQL database is named PIVision.

  • A particular instance of SQL Server is used.

  • The machine account of the AVEVA PI Vision application server is used.

• Local SQL Express database, services running under default application pool

  .\Go.ps1 .\SQLEXPRESS PIVision "NT AUTHORITY\NETWORK SERVICE" output.log

  • The AVEVA PI Vision SQL database is a local SQL Express database. The PI Vision SQL database is named PIVision.

  • The AVEVA PI Vision web services run under the default application pool.

  • The script writes results to the output.log file in the directory that contains the Go.ps1 file.

• SQL Server using custom port, custom domain account

  .\Go.ps1 "sqlserver,4452" PIVision mydomain\PIVisionaccount

  • The AVEVA PI Vision SQL database is named PIVision.

  • Custom port 4452 is being used for SQL Server.

  • A custom domain account is used.

Run the script: SQL Server with SQL authentication

If you use on-premises SQL Server with SQL Server authentication for your PI Vision database, follow the steps below to run the Go.ps1 script in order to create or upgrade your database.

5. On the AVEVA PI Vision application server, copy the SQL directory.

   This directory is typically located here:

   Program Files/PIPC/PIVision/Admin/SQL

6. On the machine running SQL Server, paste the folder and all its contents to a local directory.

7. On the machine running SQL Server, open Powershell or Powershell ISE as Administrator, navigate to the local directory pasted in step 2, and run the Go.ps1 script.

   Type:

   Note: If any parameter below contains any spaces, enclose it in double quotation marks.

   .\Go.ps1 -SqlServerName DBServer -SqlDatabaseName DBName -WindowsLoginForService PIVisionService -SqlUserName MySQLUser -OutputFile LogFile

   where:

   • DBServer is the name of the SQL server.

   • DBName is the name of the AVEVA PI Vision database, which is typically PIVision.

   • PIVisionService is the name of the AVEVA PI Vision service account. This parameter is optional. Specify this parameter if you want the Go.ps1 script to set up permissions for the AVEVA PI Vision service account to access its SQL database using Windows authentication. If you want to use SQL authentication instead, do not specify this parameter.

   • MySQLUser is the SQL user that you use to authenticate to the SQL Server while running the Go.ps1 script. This user must have the necessary permissions (refer to the table on Create and configure your PI Vision database). You will be prompted to enter the SQL password for this SQL user.

   • LogFile is the file where the script writes log information. This parameter is optional. If specified, the script writes to this file in the directory that contains the Go.ps1 script. If not specified, the script writes to the go_outputfile.log file in the directory defined by the user variable TEMP.

8. If you did not specify the WindowsLoginForService parameter, follow the steps to Add permissions to the PI Vision database for web services.

9. Modify the web.config file.

10. Open the PI Vision Administration website to confirm that PI Vision can successfully connect to the SQL database. For details, see Create and configure your PI Vision database.

    Note: If you are performing an upgrade and you are continuing to use the same database, typically you do not need to complete additional steps on the Administration website.

Examples of input parameters for Go.ps1

The following examples demonstrate the use of input parameters with the Go.ps1 script when using on-premises SQL Server with SQL Server authentication for your PI Vision database

• Default local instance of SQL Server, custom domain account

  .\Go.ps1 -SqlServerName .\ -SqlDatabaseName PIVision -WindowsLoginForService mydomain\PIVisionaccount -SqlUserName MySQLUser

  • The AVEVA PI Vision SQL database is named PIVision.

  • The default local instance of SQL Server is used.

  • A custom domain account is used.

• Default local instance of SQL Server, no domain account permissions will be configured

  .\Go.ps1 -SqlServerName .\ -SqlDatabaseName PIVision -SqlUserName MySQLUser

  • The AVEVA PI Vision SQL database is named PIVision.

  • The default local instance of SQL Server is used.

  • You do not want the script to configure permissions for the AVEVA PI Vision service account using Windows authentication.

• Specific instance of SQL Server, machine account

  .\Go.ps1-SqlServerName sqlserver\sqlinstance -SqlDatabaseName PIVision -WindowsLoginForService mydomain\PIVisionserver$ -SqlUserName MySQLUse

  • The AVEVA PI Vision SQL database is named PIVision.

  • A particular instance of SQL Server is used.

  • The machine account of the AVEVA PI Vision application server is used.

• Local SQL Express database, services running under default application pool

  .\Go.ps1 -SqlServerName .\SQLEXPRESS -SqlDatabaseName PIVision -WindowsLoginForService "NT AUTHORITY\NETWORK SERVICE" -SqlUserName MySQLUser -OutputFile output.log

  • The AVEVA PI Vision SQL database is a local SQL Express database. The PI Vision SQL database is named PIVision.

  • The AVEVA PI Vision web services run under the default application pool.

  • The script writes results to the output.log file in the directory that contains the Go.ps1 file.

• SQL Server using custom port, custom domain account

  .\Go.ps1 -SqlServerName "sqlserver,4452" -SqlDatabaseName PIVision -WindowsLoginForService mydomain\PIVisionaccount

  • The AVEVA PI Vision SQL database is named PIVision.

  • Custom port 4452 is being used for SQL Server.

  • A custom domain account is used.

Azure SQL Database prerequisites

To create or update a PI Vision database that is on Azure SQL Database, you must be logged in with Windows Authentication. For details on the permissions that you need, refer to Required SQL permissions.

For Azure managed identities:

If you are using a System Assigned Managed Identity, it must be enabled on the Azure VM on which you are running the Go.ps1 script.

If you are using a User Assigned Managed Identity, it must be assigned to the Azure VM on which you are running the Go.ps1 script.

Refer to Configure managed identities on Azure virtual machines (VMs) for details on how to enable or assign an identity to an Azure VM.

Run the script: Azure SQL Database with Microsoft Entra authentication

If you use Azure SQL Database with Microsoft Entra authentication for your PI Vision database, follow the steps below to run the Go.ps1 script in order to create or upgrade your database.

Note: If you will be using a System or User Assigned Managed Identity to run this script, the machine on which you will run the Go.ps1 script to create the PI Vision Azure SQL database must itself be hosted in Azure and the Azure VM must be assigned this identity.

11. Typically, you should run the Go.ps1 script from the machine on which AVEVA PI Vision is installed, but it can be run from any machine that can access your Azure SQL Database. If you will run the script from somewhere other than the AVEVA PI Vision machine, follow the next two steps below. If you will run the script from the machine where AVEVA PI Vision is installed, skip ahead to step 3.

    On the AVEVA PI Vision application server, copy the SQL directory.

    This directory is typically located here:

    Program Files/PIPC/PIVision/Admin/SQL

12. On the machine from which you will run the Go.ps1 script, paste the folder and all its contents to a local directory.

13. On the machine from which you will run the Go.ps1 script, open Powershell or Powershell ISE as Administrator, navigate to the directory containing the Go.ps1 script (located at either Program Files/PIPC/PIVision/Admin/SQL on the AVEVA PI Vision server itself or the local directory where you pasted the directory in the previous step), and run the Go.ps1 script.

    Type:

    Note: If any parameter below contains any spaces, enclose it in double quotation marks.

    .\Go.ps1 -SqlServerName DBServer -SqlDatabaseName DBName -SqlUserName -G [-MicrosoftEntraUserId MyEntraUser] [-MicrosoftEntraPassword MyEntraPassword] [-OutputFile LogFile]

    -OR-

    .\Go.ps1 -SqlServerName DBServer -SqlDatabaseName DBName -SqlUserName -auth -AuthMode ChooseAuthMode [-MicrosoftEntraUser MyEntraUser] [-MicrosoftEntraPassword MyEntraPassword] [-OutputFile LogFile]

    where:

    • The -G option is compatible with either sqlcmd (odbc) or the newer sqlcmd (go). The -auth option is only compatible with the newer sqlcmd (go). Refer to Microsoft's sqlcmd utility page for details on how to install sqlcmd.

    • DBServer is the name of the Azure SQL Database server.

    • DBName is the name of the AVEVA PI Vision database, typically PIVision.

    • MicrosoftEntraUserId is the Microsoft Entra user or client ID. It is optional dependent on which authentication method you would like to use. See examples for details.

    • MicrosoftEntraPassword is the Microsoft Entra password. It is optional, dependent on which authentication method you would like to use. See examples further below for details.

    • LogFile is the file where the script writes log information. This parameter is optional. If specified, the script writes to this file in the directory that contains the Go.ps1 script. If not specified, the script writes to the go_outputfile.log file in the directory defined by the user variable TEMP.

14. Follow the steps to Add permissions to the PI Vision database for web services.

15. Modify the web.config file.

16. Open the PI Vision Administration website to confirm that PI Vision can successfully connect to the SQL database. For details, see Create and configure your PI Vision database.

    Note: If you are performing an upgrade and you are continuing to use the same database, typically you do not need to complete additional steps on the Administration website

Examples of input parameters for Go.ps1

The following examples demonstrate the use of input parameters with the Go.ps1 script when using Azure SQL Database with Microsoft Entra authentication for your PI Vision database. For descriptions of the different authentication options, refer to Microsoft's Authenticate with Microsoft Entra ID in sqlcmd page. In these examples, the Azure SQL Database is named my-azure-sql-server.database.windows.net and AVEVA PI Vision SQL database is named PIVision.

• -G option: Integrated [sqlcmd (odbc)] or default [sqlcmd (go)] Microsoft Entra Authentication

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -G

  • If using sqlcmd (ODBC) this uses Microsoft Entra integrated authentication. If using sqlcmd (go) this uses default Microsoft Entra authentication (refer to Authenticate with Microsoft Entra ID in sqlcmd for setup details).

• -G option: Interactive Microsoft Entra Authentication

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -G -MicrosoftEntraUserId myuser@mydomain.com

  • Launches a web browser to authenticate the user. Note that you will be prompted to authenticate for each sqlcmd connection attempt in the Go.ps1 script.

• -G option: Microsoft Entra Password Authentication

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -G -MicrosoftEntraUserId myuser@mydomain.com -MicrosoftEntraPassword (Read-Host "MicrosoftEntraPassword" -AsSecureString)

  • Prompts the user to enter the Microsoft Entra password corresponding to the user myuser@mydomain.com and authenticates with this username and password.

• -auth option: ActiveDirectoryDefault Microsoft Entra Authentication [sqlcmd (go) only]

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -auth -AuthMode ActiveDirectoryDefault

• -auth option: ActiveDirectoryPassword Microsoft Entra Authentication [sqlcmd (go) only]

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -auth -AuthMode ActiveDirectoryPassword -MicrosoftEntraUserId myuser@mydomain.com

  Note: Set the corresponding Microsoft Entra password in the SQLCMDPASSWORD system environment variable.

• -auth option: ActiveDirectoryManagedIdentity Microsoft Entra Authentication with a System Assigned Managed Identity

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -auth -AuthMode ActiveDirectoryManagedIdentity

  Uses the System Assigned Managed Identity of the machine on which the Go.ps1 script is being run to authenticate to Azure SQL Database.

  Note: The machine on which you are running Go.ps1 must be an Azure-hosted VM with its System Assigned Managed Identity enabled to use this option.

• -auth option: ActiveDirectoryManagedIdentity Microsoft Entra Authentication with a User Assigned Managed Identity

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -auth -AuthMode ActiveDirectoryManagedIdentity -MicrosoftEntraUserId 65935a7f-8ad3-4261-8fae-cecae613c87e

  Uses the specified User Assigned Managed Identity (client ID is 65935a7f-8ad3-4261-8fae-cecae613c87e in the above example) assigned to the machine on which the Go.ps1 script is being run to authenticate to Azure SQL Database.

  Note: The machine on which you are running Go.ps1 must be an Azure-hosted VM with the User Assigned Managed Identity whose client ID is specified assigned to it to use this option.

• -auth option: ActiveDirectoryServicePrincipal

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -auth -AuthMode ActiveDirectoryServicePrincipal -MicrosoftEntraUserId ServicePrincipalId@TenantId

  Uses the specified service principal (ServicePrincipalId@TenantId in this example) to connect to Azure SQL Database.

  Note: Set the corresponding Microsoft Entra password in the SQLCMDPASSWORD system environment variable.

Run the script: Azure SQL Database with SQL authentication

If you use Azure SQL Database with SQL Server authentication for your PI Vision database, follow the steps below to run the Go.ps1 script in order to create or upgrade your database.

17. Typically, you should run the Go.ps1 script from the machine on which AVEVA PI Vision is installed, but it can be run from any machine that can access your Azure SQL Database. If you will run the script from somewhere other than the AVEVA PI Vision machine, then follow the next two steps below. If you will run the script from the machine where AVEVA PI Vision is installed, skip ahead to step 3.

    On the AVEVA PI Vision application server, copy the SQL directory.

    This directory is typically located here:

    Program Files/PIPC/PIVision/Admin/SQL

18. On the machine from which you will run the Go.ps1 script, paste the folder and all its contents to a local directory.

19. On the machine from which you will run the Go.ps1 script, open Powershell or Powershell ISE as Administrator, navigate to the directory containing the Go.ps1 script (located at either Program Files/PIPC/PIVision/Admin/SQL on the AVEVA PI Vision server itself or the local directory where you pasted the directory in the previous step), and run the Go.ps1 script.

    Type:

    Note: If any parameter below contains any spaces, enclose it in double quotation marks.

    .\Go.ps1 -SqlServerName DBServer -SqlDatabaseName DBName -SqlUserName MySQLUser -OutputFile LogFile

    where:

    • DBServer is the name of the Azure SQL Database server.

    • DBName is the name of the AVEVA PI Vision database, typically PIVision.

    • MySQLUser is the SQL user that you use to authenticate to the Azure SQL Database while running the Go.ps1 script. This user must have the necessary permissions (refer to the Azure SQL Database prerequisites section above). You will be prompted to enter the SQL password for this SQL user.

    • LogFile is the file where the script writes log information. This parameter is optional. If specified, the script writes to this file in the directory that contains the Go.ps1 script. If not specified, the script writes to the go_outputfile.log file in the directory defined by the user variable TEMP.

20. Follow the steps to Add permissions to the PI Vision database for web services.

21. Modify the web.config file.

22. Open the PI Vision Administration website to confirm that PI Vision can successfully connect to the SQL database. For details, see Create or upgrade the PI Vision database.

    Note: If you are performing an upgrade and you are continuing to use the same database, typically you do not need to complete additional steps on the Administration website

Examples of input parameters for Go.ps1

The following examples demonstrate the use of input parameters with the Go.ps1 script when using Azure SQL Database with SQL authentication for your PI Vision database. In these examples, the Azure SQL Database is named my-azure-sql-server.database.windows.net and the AVEVA PI Vision SQL database is named PIVision.

• Default log file location

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -SqlUserName MySQLUser

  • The script writes to the default log file location.

• Custom log file location

  .\Go.ps1 -SqlServerName my-azure-sql-server.database.windows.net -SqlDatabaseName PIVision -SqlUserName MySQLUser -OutputFile output.log

  • The script writes results to the output.log file in the directory that contains the Go.ps1 file.

Run the script: Amazon RDS for SQL Server with Windows authentication

If you use Amazon RDS for SQL Server with Windows authentication for your PI Vision database, follow the steps below to run the Go.ps1 script in order to create or upgrade your database.

23. Typically, you should run the Go.ps1 script from the machine on which AVEVA PI Vision is installed, but it can be run from any machine that can access your database. If you will run the script from somewhere other than the AVEVA PI Vision machine, follow the next two steps below. If you will run the script from the machine where AVEVA PI Vision is installed, skip ahead to step 3.

    On the AVEVA PI Vision application server, copy the SQL directory.

    This directory is typically located here:

    Program Files/PIPC/PIVision/Admin/SQL

24. On the machine from which you will run the Go.ps1 script, paste the folder and all its contents to a local directory.

25. On the machine from which you will run the Go.ps1 script, open PowerShell or PowerShell ISE as Administrator, navigate to the local directory pasted in step 2, and run the Go.ps1 script.

    Type:

    Note: If any parameter below contains any spaces, enclose it in double quotation marks.

    .\Go.ps1 DBServer DBName PIVisionService LogFile

    where:

    • DBServer is the name of the SQL server.

    • DBName is the name of the AVEVA PI Vision database, which is typically PIVision.

    • PIVisionService is the name of the AVEVA PI Vision service account.

      You need to format PIVisionService according to which type of account you are using:

      PIVisionService account type	Format for PIVisionService
      Domain user	domain\service account name
      Network Service	Enter the application server computer domain account. Active Directory computer accounts always end in a dollar sign. For example: "domain\computer name$"

    • LogFile is the file where the script writes log information. This parameter is optional. If specified, the script writes to this file in the directory that contains the Go.ps1 script. If not specified, the script writes to the go_outputfile.log file in the directory defined by the user variable TEMP.

26. If you did not specify the WindowsLoginForService parameter, follow the steps to Add permissions to the PI Vision database for web services.

27. After the command completes, open the PI Vision Administration website to confirm that PI Vision can successfully connect to the SQL database. For details, see Create and configure your PI Vision database.

    Note: If you are performing an upgrade and you are continuing to use the same database, typically you do not need to complete additional steps on the Administration website.

Examples of input parameters for Go.ps1

The following examples demonstrate the use of input parameters with the Go.ps1 script when using Amazon RDS for SQL Server with Windows authentication for your PI Vision database

• Services run under default application pool

  .\Go.ps1 mysqlserver.abcdefg1ij2k.us-east-1.rds.amazonaws.com PIVision mydomain\PIVisionserver$

  • The PI Vision SQL database is named PIVision.

  • The PI Vision web services run under the machine account (default application pool) of the PI Vision server named PIVisionserver.

• Services run under custom domain account

  .\Go.ps1 mysqlserver.abcdefg1ij2k.us-east-1.rds.amazonaws.com PIVision mydomain\PIVisionaccount

  • The PI Vision SQL database is named PIVision.

  • The PI Vision web services run under a custom domain account.

Run the script: Amazon RDS for SQL Server with SQL authentication

If you use Amazon RDS for SQL Server with SQL authentication for your PI Vision database, follow the steps below to run the Go.ps1 script in order to create or upgrade your database.

28. Typically, you should run the Go.ps1 script from the machine on which AVEVA PI Vision is installed, but it can be run from any machine that can access your database. If you will run the script from somewhere other than the AVEVA PI Vision machine, then follow the next two steps below. If you will run the script from the machine where AVEVA PI Vision is installed, skip ahead to step 3.

29. On the AVEVA PI Vision application server, copy the SQL directory.

    This directory is typically located here:

    Program Files/PIPC/PIVision/Admin/SQL

30. On the machine from which you will run the Go.ps1 script, open Powershell or Powershell ISE as Administrator, navigate to the local directory pasted in step 2, and run the Go.ps1 script..

    Type:

    Note: If any parameter below contains any spaces, enclose it in double quotation marks.

    .\Go.ps1 -SqlServerName DBServer -SqlDatabaseName DBName -WindowsLoginForService PIVisionService -SqlUserName MySQLUser -OutputFile LogFile

    where:

    • DBServer is the name of the SQL server.

    • DBName is the name of the AVEVA PI Vision database, which is typically PIVision.

    • PIVisionService is the name of the AVEVA PI Vision service account. This parameter is optional. Specify this parameter if you want the Go.ps1 script to set up permissions for the AVEVA PI Vision service account to access its SQL database using Windows authentication. If you want to use SQL authentication instead, do not specify this parameter.

    • MySQLUser is the SQL user that you use to authenticate to the SQL Server while running the Go.ps1 script. This user must have the necessary permissions (refer to the table on Create and configure your PI Vision database). You will be prompted to enter the SQL password for this SQL user.

    • LogFile is the file where the script writes log information. This parameter is optional. If specified, the script writes to this file in the directory that contains the Go.ps1 script. If not specified, the script writes to the go_outputfile.log file in the directory defined by the user variable TEMP.

31. If you did not specify the WindowsLoginForService parameter, follow the steps to Add permissions to the PI Vision database for web services.

32. Modify the web.config file.

33. Open the PI Vision Administration website to confirm that PI Vision can successfully connect to the SQL database. For details, see Create and configure your PI Vision database.

    Note: If you are performing an upgrade and you are continuing to use the same database, typically you do not need to complete additinal steps on the Administration website.

Examples of input parameters for Go.ps1

The following examples demonstrate the use of input parameters with the Go.ps1 script when using Amazon RDS for SQL Server with SQL authentication for your PI Vision database

• Services run under default application pool

  .\Go.ps1 -SqlServerName mysqlserver.abcdefg1ij2k.us-east-1.rds.amazonaws.com -SqlDatabaseName PIVision -WindowsLoginForService mydomain\PIVisionserver$

  • The PI Vision SQL database is named PIVision.

  • The PI Vision web services run under the machine account (default application pool) of the PI Vision server named PIVisionserver.

• Services run under custom domain account

  .\Go.ps1 -SqlServerName mysqlserver.abcdefg1ij2k.us-east-1.rds.amazonaws.com -SqlDatabaseName PIVision -WindowsLoginForService mydomain\PIVisionaccount -SqlUserName MySQLUser

  • The PI Vision SQL database is named PIVision.

  • The PI Vision web services run under a custom domain account.

• No domain account permissions will be configured

  .\Go.ps1 -SqlServerName mysqlserver.abcdefg1ij2k.us-east-1.rds.amazonaws.com -SqlDatabaseName PIVision -SqlUserName MySQLUser

  • The PI Vision SQL database is named PIVision.

  • You do not want the script to configure permissions for the PI Vision service account using Windows authentication.