Whenever I've come across installing Tridion, I've always installed at least two broker databases, and lately three if you count the Session Preview broker as well. The first broker is for Staging websites, while the second is used for Live sites.
As is the case with a repetitive action, the more you do it, the faster and better you become at it.
Here are several pseudo-steps as an easy recipe to get you through this setup fast as fast can be in Tridion 2013 SP1.
1. Install the actual database and know the database credentials ahead of time*: run the Powershell script
& '.\Install Content Data Store.ps1'
2. Name your broker something different than what is in the database already (eg. Tridion_Broker_Staging)
3. Update your (second) Deployer cd_storage_conf.xml with the new broker information and configure how you want different item types to be handled. A second separate deployer is required to write to the new database.
4. Update (another) corresponding website cd_storage_conf.xml to show content from the second broker. A separate website is necessary as well to show content stored in the new broker.
5. Loop back into the Tridion Content Manager Explorer and create the necessary [Staging] target type and publication target(s).
Specify the deployer information based on type installed and apply the publications you want to store content in the new broker.
.. and voila, the second broker should be active and receiving content when you publish.
Happy brokering!
References (login required):
