NOTE:  These instructions do not cover creating a complete test environment and only cover adding another database listing to the Blackbaud CRM (BBEC) or Blackbaud Direct Marketing (BBDM) login screen.

  Making a change to any file (including the web.config file) inside or under the ..\bbappfx\vroot folder will cause the IIS worker process to recycle.  This will halt all running business processes which may cause further data-related issues.  This adjustment is best done when you know there are no activations, queues, or ETL refresh processes or other business processes running.  To see if it’s a good time to add/edit files, check for running business processes:
Admin > Business Processes > Process type - blank, Status - Running, and click Apply.

1) Attach a backup of the original database or already have the secondary database attached
2) Create a copy of the web.config found in the ..\bbappfx\vroot\ folder and then edit the original in notepad or similar editor:
Look in the top 50 lines of the file for the main appSettings section and the add key “DBList”:
    <add key=”DBList” value=?? />
(The “??” will read what you normally see in the dropdown for BBDM when logging in and is a semi-colon separated list)
3) Add a semi colon to this and what you want to see for the secondary database on the login screen
For example:
<add key=”LiveDB;TrainingDB” />
4) With those values in mind, scroll down the web.config file to adjust the <connectionStrings> section.
For each DBList item seen in the <appSettings> section, we need a connection for it here.  You should already have one connection for the existing database and if the secondary database is on the same SQL instance you can copy/paste this line and adjust it to read the new database.
For example:
   <add name=”LiveDB” connectionString=”Server=[SQLSERVERINSTANCE];database=[DATABASENAME];integrated security=sspi” />
   <add name=”TrainingDB” connectionString=”Server=[SQLSERVERINSTANCE];database=[DATABASENAME];integrated security=sspi” />
SQL connection stings may be different if using a different style SQL security or if using a secondary SQL server

NOTE:  For best performance, use a secondary SQL server for this secondary database or consider creating a complete test environment.