Possible Duplicate:
Can you help me with my software licensing question?
I'm tempted to use a DR server which holds a mirrored copy of a database to also perform test restores and integrity checks of the principle database.
There maybe issues with network bandwidth (copying the backup from the primary server along with the mirrored traffic) and CPU capacity on the secondary DR server (performing redo and running checkdb on Standard edition), besides these, if I do restore and recover the primary database on the seondary DR server, will I have to license the box?
I wouldn't be using this copy of the primary database for anything other than running checkdb (honest guv).
Express or Developer editions won't do it as you're already using mirroring.
Basically as soon as you use the instance for anything apart from hosting redundant copies of databases through log-shipping or mirroring, you must buy a license.
It's a bit sucky as most people would expect that testing restore sequences and running consistency checks would be ok, but them's the rules!
If you go this route, be careful how you place the databases, in terms of I/O subsystem - the extra I/O load from CHECKDB (usually way more than doing a restore) could make your mirroring REDO queue grow and contribute to a slower failover.
Hope this helps!
PS I had an idea - what you could do is log-ship to the same instance the database that you're interested in - then you will be testing the log backups at least. Technically, restoring using WITH STANDBY and running CHECKDB is against the licensing model too...
I've always been under the impression that a 'passive server' is allowed for DR to log ship or mirror to. From microsoft:
When doing failover support, a server is designated as the passive server. The purpose of the passive server is to absorb the data and information held in another server that fails. A passive server does not need a license if the number of processors in the passive server is equal to or less than the number of processors in the active server. The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly.
You still need to buy an OS license though.
If SQL Express won't cut it for what you're trying to do the at the very least you'll need a SQL Developer Edition license. You might be in some gray area with even a SQL Developer license depending on what you're doing with that mirrored copy.
If it truly is used only for disaster recovery, it does not need a SQL license as long as the DR box does not have more processors than the production server. You can install the same edition of SQL as your production server, not higher. If you fail over to the DR box, you have 30 days to restore to the primary server. See the Active/Passive licensing question here, it references log shipping specifically, but applies to all Active/Passive failover models to the best of my understanding. The only possible gotcha is you need to be processor-licensed on the primary. More details are on page 2 here [doc]
You do, however, need to license the OS no matter what.
Go and buy a single server license (CAL Based). It comes with 5 CALs which will be enough for your DBAs to use to connect and will only cost a few thousand. Since all you want to do it restore and checkdb the machine you can get away with the Workgroup edition which costs even less.