How do the specs line up for this new proposed solution? Number of IOPs it's capable of? Number of spindles?
This all needs to be addressed and it needs to address your needs. Watch closely how they're selling it to management. You care about spindles and disk queue lengths, right, not capacity (although you obviously need to have enough disk space to store and grow). So the vendor needs to prove to you that the IOPs and disk latency aren't going to be an issue the intended solution.
We've used a lot of things in the past and still have a good mix of disk solutions around (SAN, DAS, Internal Storage, and one iSCSI solution) and the iSCSI solution is the least favorite of mine. We eventually got the SQL data moved off that solution and onto a SAN, and used that iSCSI solution as document storage (which I think it's better suited to 😉 ). But again, on a fiber connection, you can run that way w/o problems if disk latency is not an issue.
Doubt that helps you much with hard numbers for mgmt, and was kind of flip-floppy, but really comes down to whether or not the I/Os are going to be fast enough for your app or not, regardless of the storage solution.
Patrick Purviance, MCDBA