I fully agree Tom, SQL Servers totally own the filesystem equivalent in this regard. Our attachments table is huge and it would be rather difficult to keep a track of them all and ensure every last one is backed up without the MySQL storage system :-)<br>
<br><div dir="ltr"><div><blockquote style="margin: 1.5em 0pt;"><p><b>Regards,<br>Aaron Guise<br>
<img src="http://www.guise.net.nz/images/signatures/ph.jpg" border="0" height="22" width="25">
07 838 7793<br>
<img src="http://www.guise.net.nz/images/signatures/mob.gif" border="0" height="24" width="30">027
212 6638<br>
<img src="http://www.guise.net.nz/images/signatures/email.gif" border="0" height="26" width="29"><a href="mailto:aaron@guise.net.nz" target="_blank">aaron@guise.net.nz</a></b><br>
<img src="http://www.guise.net.nz/images/signatures/itil_logo.gif" height="30"> <img style="width: 25px; height: 41px;" src="http://www.guise.net.nz/images/signatures/officiallogo-nd-25.jpg"> <img src="http://www.guise.net.nz/images/signatures/ubuntu.png" height="30"></p>
</blockquote></div></div><br><br><div class="gmail_quote">On Thu, Sep 17, 2009 at 11:00 AM, Tom Lahti <span dir="ltr"><<a href="mailto:toml@bitstatement.net">toml@bitstatement.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Justin Hayes wrote:<br>
> Thanks Aaron. I've always wondered why file attachments are stored in<br>
> the db at all. I'd have thought those would have been better placed out<br>
> in the filesystem.<br>
<br>
</div>Egads! What if the storage database is not local to the web server? How will<br>
you perform comprehensive backups? What if your RT has a million attachments,<br>
or more? Not to mention the performance hit of using a filesystem as a<br>
database, especially with high concurrency at the HTTP level.<br>
<br>
I have a custom database application designed specifically to store PDFs in<br>
the database. It has 30 million documents in it, the database storage is over<br>
4TB. The web-based front-end for it is efficient enough to saturate a<br>
100MBit/sec Internet connection with a single Core-2 duo web server. When I<br>
tested this against our old filesystem version of the application, it<br>
outperformed the filesystem by more than 100%. Backup is done by dumping the<br>
database in chunks in a rotating schedule. Scalability can be accomplished<br>
with simple replication to additional read-only SQL servers and using a SQL<br>
relay to dispatch SQL commands in a load-balancing fashion.<br>
<font color="#888888"><br>
--<br>
-- ============================<br>
Tom Lahti<br>
BIT Statement LLC<br>
<br>
(425)251-0833 x 117<br>
<a href="http://www.bitstatement.net/" target="_blank">http://www.bitstatement.net/</a><br>
-- ============================<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
<a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users" target="_blank">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</a><br>
<br>
Community help: <a href="http://wiki.bestpractical.com" target="_blank">http://wiki.bestpractical.com</a><br>
Commercial support: <a href="mailto:sales@bestpractical.com">sales@bestpractical.com</a><br>
<br>
<br>
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.<br>
Buy a copy at <a href="http://rtbook.bestpractical.com" target="_blank">http://rtbook.bestpractical.com</a><br>
</div></div></blockquote></div><br>