StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
514569
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-02-05T04:24:19.360
FavoriteCount
0
LastActivityDate
2009-02-05T04:24:19.360
LastEditDate
LastEditorUserId
0
OwnerUserId
56279
ParentId
512262
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
The only limit to storing documents in the database is technological. A <a href="http://en.wikipedia.org/wiki/Relational_database" rel="nofollow noreferrer">relation database</a> is meant to be the persistent store of the mission critical data of an enterprise. How well it can perform that function varies from database to database and system to system, of course. But ideally the <a href="http://en.wikipedia.org/wiki/ACID" rel="nofollow noreferrer">ACID</a> properties of a <a href="http://en.wikipedia.org/wiki/Relational_model" rel="nofollow noreferrer">relational database</a> are intended to make it the store of all <a href="http://en.wikipedia.org/wiki/Enterprise_Data_Management" rel="nofollow noreferrer">enterprise data</a>. The file system, revision controller systems and other local store storage systems might have specific advantages but they are not designed for enterprise data storage as such. If the documents you are storing qualify as enterprise data - if they are used persistently through-out the enterprise - then it is logical to keep them in the database. If you are having problems with storing in the database, perhaps a DBA can find a better solution. You might even have to move them out of the database for performance reasons but I don't think you should move them out of the database for best-practices reasons. Of course, if the documents aren't enterprise data, if they're only used for one application, say, then moving them out of the database would also make sense. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORecommended location for document storage - in database or elsewhere?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoe Soul-bringer
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORecommended location for document storage - in database or elsewhere?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.