A lot depends on what kind of information you're hoping to pull out of the KML. If you want the whole shebang, you're in the land of parsing the KML yourself and figuring out a sane way to represent that in SQL.. Brace yourself. If you really only care about GPS-ish things (waypoints, tracks, names, descriptions, etc.) and not things like camera angles and line widths and colors it's not too bad.
I did a contract project where I was faced with a similar problem a few months ago and it occurred to me that a
custom output format for GPSBabel could do the KML parsing and hock up the 'insert into' lines. I don't recall if I had to post-process the output, but I do remember it made it a pretty trivial problem.
It handles only a small subset of the things expressible in KML but it solved the problem at hand.
(It may have also been an "everything looks like a nail" approach to the solution.)