What's the most appropriate storage type for a PDF?

Question

0

What's the most appropriate storage type for a PDF?

Jez Hailwood posted 9 Years Ago

I need to add a new file type for use with an extended attribute, but I'm not sure whether to choose FileSystem or Database as the storage type. If I chose FileSystem, where should I put the files?

David Leigh · Accepted Answer · 2015-03-17T04:09-07:00

0

David Leigh replied 9 Years Ago

This decision really depends on the expected size of your database and how you want to manage these files.

For anything other than a small database, I would recommend file system storage for the following reasons:
1. Reduced database size.
This means better performance and your nightly database backup will run faster and take up less space.

2. The PDF files can be backed up and managed separately.
Given that these files are usually relatively static, they probably don't need to be backed up nightly - they can be backed up on a separate schedule.
Also, it is easier to track large files and other potential problems if the files are stored in the file system.

3. You have the option to store the files in a different location (a slower disk/server) if necessary, when resources on the database server become an issue at a later stage.
Having said that, I would follow the pattern used for Rock Media Files until such time as you need to store files in a different location.

Hope this helps.

Edit Answer

This decision really depends on the expected size of your database and how you want to manage these files.

For anything other than a small database, I would recommend file system storage for the following reasons: 
1. Reduced database size. 
This means better performance and your nightly database backup will run faster and take up less space.

2. The PDF files can be backed up and managed separately. 
Given that these files are usually relatively static, they probably don't need to be backed up nightly - they can be backed up on a separate schedule. 
Also, it is easier to track large files and other potential problems if the files are stored in the file system.

3. You have the option to store the files in a different location (a slower disk/server) if necessary, when resources on the database server become an issue at a later stage. 
Having said that, I would follow the pattern used for Rock Media Files until such time as you need to store files in a different location.

Hope this helps.

<p>This decision really depends on the expected size of your database and how you want to manage these files.</p>

<p>For anything other than a small database, I would recommend file system storage for the following reasons:<br />
1. Reduced database size.<br />
<span style="line-height: 20.7999992370605px;">This means better performance and your nightly database backup will run faster and take up less space.</span></p>

<p><span style="line-height: 1.6em;">2. The PDF files can be backed up and managed separately.</span><br />
<span style="line-height: 1.6em;">Given that these files are usually relatively static, they probably don't need to be backed up nightly - t</span><span style="line-height: 1.6em;">hey can be backed up on a separate schedule.<br />
Also, it is easier to track large files and other potential problems if the files are stored in the file system.</span></p>

<p><span style="line-height: 1.6em;">3. You have the option to store the files in a different location (a slower disk/server) if necessary, when resources on the database server become an issue at a later stage.</span><br />
<span style="line-height: 1.6em;">Having said that, I would follow the pattern used for Rock Media Files until such time as you need to store files in a different location.</span></p>

<p>Hope this helps.</p>

<p>This decision really depends on the expected size of your database and how you want to manage these files.</p>

<p>For anything other than a small database, I would recommend file system storage for the following reasons:<br />
1. Reduced database size.<br />
<span style="line-height: 20.7999992370605px;">This means better performance and your nightly database backup will run faster and take up less space.</span></p>

<p><span style="line-height: 1.6em;">2. The PDF files can be backed up and managed separately.</span><br />
<span style="line-height: 1.6em;">Given that these files are usually relatively static, they probably don't need to be backed up nightly - t</span><span style="line-height: 1.6em;">hey can be backed up on a separate schedule.<br />
Also, it is easier to track large files and other potential problems if the files are stored in the file system.</span></p>

<p><span style="line-height: 1.6em;">3. You have the option to store the files in a different location (a slower disk/server) if necessary, when resources on the database server become an issue at a later stage.</span><br />
<span style="line-height: 1.6em;">Having said that, I would follow the pattern used for Rock Media Files until such time as you need to store files in a different location.</span></p>

<p>Hope this helps.</p>

Save Cancel

Jez Hailwood

9 years ago

So helpful, thanks! Would you recommend that I use ~/App_Data/Files as the root, or something like ~/App_Data/Files/MyNewFileType?
David Leigh

9 years ago

I would use separate sub-directories, so you can keep related files together.
Jez Hailwood

9 years ago

Thanks again. I don't suppose you know what happens if you change from database to file system storage when there are already files in the database?

Question

0

What's the most appropriate storage type for a PDF?

0