SQL Server is easy to adminsitrate, but it still needs administration. That includes at minimum:
- Regular backups. You want that - or another model - to clean up your log files (as they otherwise accumulate and never get deleted).
- Regular patching. Every 2 months for a cumulative update.
On top, set up some autoamtic maintenance within SQL Server (like weekyl database checks etc.).
From all databases SQL Server is the one best to administrate.
That said, you are on a bad track potentially:
- SQL licenses on the internet have to be SPLA (Service Provider License Agreement). Not purchased, rented monthly. Cheaper than purchasing, on top. Your licesne simply does not cover service providing.
- IO performance possibly sucks. Hyper-V standard servres are NOT made for SQL hosting. SQL, as any database, when getting more busy has VERY specific IO needs - the disc layout is normally planned for a database, not just a "put some discs into a case" thing. It works nice on Hyper-V, too (I run my main SQL Server on Hyper-V), but you wont want to have a "normal" hyper-V setup which most likely has totally crappy IO values to start with.
Example of the IO issue:
Depending on how you run Hyper-V as host you may have a "mid sized server" (8-12 processor cores, basically a dual processor Opteron platform) with 32-64gb RAM that you load with VM's. Discs - hm - a couple of large 1tb discs in a RAID possibly. Either 2x1TB to 2x2tb mirrored, or three in a RAID 5 is likely (cheap). Performance? Good enough for most things. Db wise? STUPID SUCKING LOW IO. You would not do that for a SQL Serve alone, but here it is shared between all hyper-v instances... and there will be many.
My own setup (just as comparison):
- Hyper-V server 2 rack units, 2x4 core opteron 64gb ram. So far the same.
- 4x10k rpm velociraptor drives as RAID 10 for OS and virtual machines.
Already a lot better and more expensive. But that is NOT where it ends.
- For the SQL server another 12 (!) velociraptor drives in 2 raid groups (logs, data) that are DIRECTLY mapped to the hyper-v instance. (And yes, the drive case has 24 hard disc slots).
Ergo: I have all the IO performacne I need (and I need it). Though this is not a typical low cost hyper-v virtual server setup.
Be carefull about your needs and about what you get as Hyper-V server. MOST offers make BAD database servers. Not relevant for a small server, though.