ESpigle (8/16/2012)
We are wanting to setup a second read-only database server that we replicate to to help load balance for some specific applications that will be fairly intense with the database. This second SQL server is always online, on the same network and as mentioned will be read only--no sending data back to the primary server. Updates need to happen as data changes on the primary server.
Reading your initial requirements I'm not sure why you need to configure transactional replication with updateable subscriptions. You have said that your replicated database will be read-only, so surely no need for an updateable subscription?