Idelossa,
Correct. NIC teaming in the vSphere hypervisor does not equal LACP or Etherchannel. By default, the balancing algorithm will balance outgoing traffic from the host based on the policy: usually based on IP hash, though sometimes based on originating port ID, etc.
Correct, in order to do an actual LACP/Etherchannel you will need the Nexus1000v license, and Enterprise plus—so it's rather pricey. I can tell you I have rarely run into situations, however, where that is a technical requirement based on throughput.
More often, there are configuration options to consider first, rather than just throwing money at the problem. 1) Have you considered traffic shaping? If you really want to get more available bandwidth, you can consolidate your network:
ESX vSwitch config
vmnic0,3 - Management/vMotion Network (separate VLANs for each)
vmnic1,2,4,5 - Production Network (separate VLANs for each)
Physical switch config
switch 1: vmnic0,1,2
switch 2: vmnic3,4,5
Or you could even consolidate this and have a dedicated pair of NICs on that host for your DB server. So you have lots of options. Hope that helps.