The PIAB installer is set up to create the 'piab' database on a typical, local instance of SQL Server. PIAB can also use a remote SQL instance - you will need to know the instance name and have sufficient permissions to restore and administer a database on that SQL instance.
NOTE If your SQL Server is on a remote PC, and you want to use the PROJECT in a box Server tool to help with database configuration, then you will need to install the PROJECT in a box Server too on that remote PC, and run it from there. You can do this with the PIAB installer, no extra licencing is required.
The task is to restore the piab database from a SQL Server .bak backup file that will have been placed in the PIAB install folder by the installer.
Program Files\Microsoft SQL Server\MSSQL\Data
You must set the piab database to allow access from the PROJECT in a box application. In practice this means granting permissions to the Windows user that runs the server's ASP.NET Application.
|Windows 2016 Server||IIS APPPOOL\DefaultAppPool|
|Windows 2012 Server||IIS APPPOOL\DefaultAppPool|
|Windows 2008R2 Server||IIS APPPOOL\DefaultAppPool|
|Windows 2008 Server||IIS APPPOOL\DefaultAppPool|
|Windows 2003 Server||NT AUTHORITY\NETWORK SERVICE|
|Windows 2000 Server||%machinename%\ASPNET|
|Separate SQL Server and Webserver PCs on a Domain||%domain%\%machinename%$|
|Vista with IIS||NT AUTHORITY\NETWORK SERVICE|
|Vista with Personal Web Server||%yourusername%|
|Windows XP Professional||%machinename%\ASPNET|
|Windows 2000 Professional||%machinename%\ASPNET|