in short don't do it
like storing images there are two schools of though, some advocate storing the image, or some in the db, some advocate storing the path to the resource.
personally I'm a believer in storing the path tot he resource rather than the actual resource in the db.
why
..stops db bloat
..reduce time take for backup & restores
..reduces costs involved in the db
..reduces the load on the db server
..allows resources to be located / stored wherever required or wherever available.
..allows you to point to resources outside your own control, reduces the bandwidth costs if its stored elsewhere.
but then again i'm a jaded developer who deep down inside doesn't like relying entirely on netwrok trolls to do the backup and be in a position to restore the db after the event