Error: You must specify a Database server that is either local or a local named instance

When I attempt to install the Blueprint Analyst Database I cannot install the database and receive the following installation message when selecting a remote SQL server.

Error: You must specify a Database server that is either local or a local named instance

How do I install a Blueprint Database on a remote SQL server?

Pharos Blueprint does not currently support a remote SQL server database installation using the standard installers. You can perform a manual installation of the database using the following instructions.

You need to perform the following steps locally on the database server using the files from the CD under \program files\PharosBlueprint\Database\MSSQL, then select the remote database instance when you run the Analyst installer.

1. Edit and execute CreateAnalystDatabase.sql

2. Copy appropriate (2000 or 2005) psbprocs files (psbprocs.mdf, psbprocs.ldf) to server. Edit and execute UpgradeAttachProcsDB.sql

3. Execute AnalystDatabase.sql against psbprint database

4. Execute PartitionDatabase.sql on each of the partition databases

5. Edit and execute SetupAnalystDatabase.sql against psbprint database

6. Execute PartitionSetup.sql against psbprint database

There is a Blueprint sizing guide on DocuShare that contains database sizing information to help with step 1.
http://192.168.1.6/dscgi/ds.py/Get/File-11954/BlueprintSizing.pdf

As guidance, below is a section cut from the .bat file that Patrick uses to quickly set up the DB on his machine.

@REM Create Analyst Database
 osql -Usa -dmaster -Sphoenix -w265 -n -iZ:\Database\Raptor\MSSQL\Current\CreateAnalystDatabase.sql -oZ:\Database\Raptor\MSSQL\Current\CreateAnalystDatabase.out -Ppharos

@REM Attach Procs Database
 copy N:\Core\Source\Database\MSSQL\dbinst\Analyst\psbprocs2000.mdf c:\temp\2K\psbprocs.mdf
 copy N:\Core\Source\Database\MSSQL\dbinst\Analyst\psbprocs2000.ldf c:\temp\2K\psbprocs.ldf
 osql -Usa -dmaster -Sphoenix -w265 -n -i Z:\Database\Raptor\MSSQL\Current\UpgradeAttachProcsDB.sql -o Z:\Database\Raptor\MSSQL\Current\UpgradeAttachProcsDB.out -Ppharos

@REM Populate Analyst Database
 osql -Usa -dpsbprint -Sphoenix -w265 -n -iN:\Core\Source\Database\MSSQL\dbinst\Analyst\AnalystDatabase.sql -oZ:\Database\Raptor\MSSQL\Current\AnalystDatabase2K.out -Ppharos

@REM Populate Partition Databases
 osql -Usa -dpsjobs1 -Sphoenix -w265 -n -iN:\Core\Source\Database\MSSQL\dbinst\Analyst\PartitionDatabase.sql -oZ:\Database\Raptor\MSSQL\Current\PartitionDatabase.out -Ppharos
 osql -Usa -dpsjobs2 -Sphoenix -w265 -n -iN:\Core\Source\Database\MSSQL\dbinst\Analyst\PartitionDatabase.sql -oZ:\Database\Raptor\MSSQL\Current\PartitionDatabase.out -Ppharos
 osql -Usa -dpsjobs3 -Sphoenix -w265 -n -iN:\Core\Source\Database\MSSQL\dbinst\Analyst\PartitionDatabase.sql -oZ:\Database\Raptor\MSSQL\Current\PartitionDatabase.out -Ppharos
 osql -Usa -dpsjobs4 -Sphoenix -w265 -n -iN:\Core\Source\Database\MSSQL\dbinst\Analyst\PartitionDatabase.sql -oZ:\Database\Raptor\MSSQL\Current\PartitionDatabase.out -Ppharos

@REM Setup Analyst Database
 osql -Usa -dpsbprint -Sphoenix -w265 -n -iZ:\Database\Raptor\MSSQL\Current\SetupAnalystDatabase.sql -o Z:\Database\Raptor\MSSQL\Current\SetupAnalystDatabase.out -Ppharos

@REM Setup partitions
 osql -Usa -dpsbprint -Sphoenix -w265 -n -iN:\Core\Source\Database\MSSQL\dbinst\Analyst\PartitionSetup.sql -o Z:\Database\Raptor\MSSQL\Current\PartitionSetup.out -Ppharos