I would save them outside, simply because they do not need to immediately and urgently store them inside. In addition, the videos are large, and you may need to run them through some other coding steps, etc., which may or may not look like SQL Server. Using basic files also gives you the ability to distribute this load to any number of file servers, rather than to a single SQL Server.
Follow the path; do not save the full path - just save some path relative to the external root that you configure in your application. This way you can move all the files and just change the settings of one site, instead of doing a big UPDATE . For example, in the database, I could store foo/bar/20110404_27.mpg , and then combine this with the site setting \\myfileserver\share (using Path.Combine ).
source share