LutzM (12/22/2010)
Gagne (12/22/2010)
...Regarding your transaction log: you might want to perform a transaction log more frequently (the setting on our production system is 15 minutes...). But that's a different story. More or less (because of the file size issue).
I changed that a while ago. If I recall it was after I had 50 users ringing my phone or walking into my office to complain that nothing was working............which turned to be caused by the expansion of the transaction log. It's backed up every 2 hours now.
But back to the point and the first part of your latest post. The CPU on is actually pretty much idle all the time, processor is really not a concern but we are conscious that we'll have to be careful on how much load we put on that machine if we turn it into a hyper-v host.
Disk I/O however can be an issue. I was reading a white paper yesterday on virtualizing SQL Server and there was something about "physical I/O path". I haven't had the time yet to take a close look at that but if I understood well, it's a way of allowing access to the physical disks to a virtual machine which would obviously improve I/O performance. This is definitely something I need to consider.