Solomon Rutzky wrote:
> Now save it somewhere safe. 🙂 Just to "poke the bear" a little bit (cuz why not), isn't this situation a point in favor for, at least sometimes, storing images in the DB? So that they get backed up with the DB backup, which one typically has at least one, if not several, days / weeks worth of? 😉
Heh... I thought it was safe. 😉 Hopefully, I have it on my old 32 bit machine, which I've not fired up in years.
The different between your avatar and mine is that mine was an animated GIF.
Anyway, I agree. There's nothing wrong with storing images, sound files, documents, etc, etc, in a database. No one will make sure the files are safe like a DBA will. You just need to be careful how you store the big stuff so that you don't need to backup large binaries that will never change again. For example, I have almost a decade of call recordings that we're required to keep "online" forever. They're in a partitioned table where there's one filegroup per month and one NDF file per file group, which have been set to Read Only, live in a different database, and never need to be backed up again. My only regret is that I should have used a Partitioned View instead of a Partitioned Table so that I could easily use parts of that large table in for smaller test systems.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems