2nd Server min requirements for transaction log shipping & reducing license cost

  • I will have a 64-bit 2008 R2 SQL Server Standard edition acting as the production (primary) database server in a vSphere environment.

    I was planning on creating a secondary server that mirrors the Operating system environment and SQL server configuration, which is where the primary databases transactional logs will be shipped and applied.

    Since this is a virtualized environment the plan was to keep the secondary server to a bare minimum in terms of CPUs/RAM, but I am wondering what the bare minimum recommendation here would be.

    I am also wondering how what the most effective licensing model would be for the secondary server, since technically it is only a standby server, it wont have any active user connections other than whats necessary for shipping and applying the transactional logs.

    Any info/experience would be much appreciated!

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply