After successful image uploading to server, you can use in your DB a string (char) value that contain the full path to image. So, if you need to display the image on website, then you just use string value from DB in "src=[path]" field.
You can store images/pictures in databases like MySQL and others. But I would not recommend it and its not a general practice. I would store images in directories on the file system and store references to the images in the database
e.g. path to image, description, ...
If you really want to store images in a DB - You will need to store the image as a BLOB (binary large object )
A general practice is to store images in directories on the file system and store references to the images in the database. Or , you may store images on a content delivery network or numerous hosts across some great expanse of physical territory, and store references to access those resources in the database.
I agree with Albert Aghajanyan, the best way to store an image to database is not really to store the entire image into database, but to store only the path to the image stored in a folder. One thing to keep in mind is that this method of storing images is good if the images will always be in the same folder (scenario when we use static images on the website), ie. if each image will have its own unique path that will always be the same. However, if the images are to be moved from folder to folder, it is still a better solution to create a dynamic path to the image, so if the image has to be moved there will be no need to modify the database.
The practice mentioned by the other guys is the best way. But it depends on the number of images. A simple and cool solution will be to use Amazon S3 buckets and store the path to the file in DB.
You can read about the S3 buckets. They provide a cool solution for your problem.
As others have said a link to the file is standard practice. On a network use the network path and all users will have access. If you decide to place pictures in the database, on SQL Server I have used BLOB's and then extracted the files when needed. This can be challenging in a multi-user environment as you'll need a scheme to determine which pictures belong to which user.