If you choose to use database mirroring with a database snapshot, then you need to ensure that none of your data files is over 64GB in size. There's a Windows sparse file issue that you can encounter. And my environment did, and it caused downtime as the transaction log filled up on the primary server since the mirroring records didn't get cleared from the tlog. We were using the database snapshot for internal folks to run some adhoc queries every now and then. We've avoided the sparse file issue by adding multiple data files (my 1TB database has 21 data files now), but we decided not to use a database snapshot on the mirror just in case.

I use transactional replication for all of our reporting needs.