storing of large files uploaded in my website

There are a couple of good reasons for not storing the file itself in a database, and they both concern the size of the items concerned.

Until recently, the maximum size of a database file was restricted to a paltry 16GB - it was raised this to 524,272 terabytes which should be enough for anybody (with the possible exception of Google) for a couple of years.

But... that doesn't mean that you should start storing large objects for a web site.
The problem is that you have at least three computers involved here: SQL server which reads the data and transfers it (normally via 1GBit/sec LAN) to the Webserver where your site application is running, which transfers it via a much slower link to your client. This takes up bandwidth (or web server memory) like crazy - start to transfer two large files at the same time and thing start to grind a bit, and the SQL connection (which is a scarce resource) has to be held until the transfer to the web server is complete.

If you are storing the file as a file in a folder on the Webserver, then the data is already local, and SQL does not have to be involved.

The way I do it is to have a DB table which holds four columns: ID, original file name, date inserted, and a link to a guid-based file name in my webserver. The SQL query is nice and quick,(since the info is just two short strings), and the file itself can be transferred from the local harddrive, with the client passed the original name instead of the internal one. The main reason for using Guid based file names is to ensure that two different users don't save the same file and overwrite each other.