havent looked at the licensing stuff yet except for the failover stuff we only need one license per bit of software it seems as the other instance isnt actually running unless the other server isnt
16gb ram is only 1.6k so in the grand scheme of stuff its fook all
ah, well this is where it gets complicated and people will give you wrong info etc.
The rules are that all software needs to be licensed, even on DR servers apart from 2 exceptions.
1. You have Software assurance on all the licenses being used i.e. on your windows 2k3 ent. license and all server CALS. In this instance you are allowed to install the software on a COLD start server, i.e. it can be installed but must be turned off except for a few circumstances, but not for warm or hot servers.
The full details can be found here:
http://download.microsoft.com/download/8/7/3/8733d036-92b0-4cb8-8912-3b6ab966b8b2/dr_brief.doc
2. SQL server has special circumstances when licensed by Processor. If licensed by server and CALS then refer to point 1, if using processor licenses, these can be moved between servers so if you have 2 processor licenses on your production server you can run the DR server as a warm server, so have the software installed but not have anyone connecting to the SQL DB and then during failover you can assign those licenses to the DR server, this is the only scenario this counts for.
A good site for licensing rules is
http://www.microsoftvolumelicensing.com/userights
Then choose the revelant product and lots of docs and info can be found in there.
Hope that makes it a bit clearer. So if you have your licenses enrolled in SA you get the cold start as a benefit, if you are doing a warm or hot start or not enrolled in SA you need the licenses for the software, even if you aren't using the server.