Normally, our log backups has < 10MB size In a big database with a lot of transactions per hour ).
But now we have a database, that is storing Images on a Image field.
the problem is, the database is HUGE ( it has now 500GB MDF, and 700GB on LDF file )and every log backup has more than 70GB !
What is the best way to store Images on a database? I've seen a lot of posts saying about store the Physical patch of the image on a VARCHAR field. But this way, we need to store the images in some place, right? It will fill the storage in the same way. Or am I wrong?
We have full backups every day at 22:00 and log backups every hour.
This is the sizes of the log backups.
EDIT1:
Each "Image" has a binary code, and it has 43679 characters ). 1 millions rows for this table ( 1.141.947 images ( with coduser, image, and etc )
EDIT2: We are now using varbinary(max), but it's not solving our problems. It has now almost 700mb after 20 minutes.
varbinary(max)
which allows 2GB of image storage. Depending on your sql server edition, you should spend time exploring FILESTREAM for storing images. – Kin Shah Nov 4 '15 at 20:28When you are using failover clustering, the FILESTREAM filegroups must be on shared disk resources.
, I need to use a disk that is inside the cluster, right? I can't use a external server, for example. I could configure it in my machine and it's perfect. – Racer SQL Nov 6 '15 at 17:38