Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-05-29 : 09:29:17
|
| Jon writes "I've been all over the net and can't seem to find a definate yes or no regarding storing BLOBs in a SQL 7 database. Seems that there are 2 routes to go:1) Store the docs in a table2) Store the docs in a file system and record the path as a string to that fileI can't believe that it is really that bad to go the first route since many developers are doing it. However I do know that I'm using a "data" base server as a file server in an intranet setting in this case. I have no replication issues that would force me to use method 1 and something about storing BLOBs just frightens me (yes, I am scarred by Access.) So what's the best route??? Should I stay clear of putting docs into my db? I also can't find a clear definition of what's happening when a document is saved into or retrieved from a table that makes it so resource intensive. Do you know? For the record, my production server is a P2 400mhz Proliant with 256 mb of RAM.Thanks for the help!-Jon" |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2002-05-29 : 10:27:18
|
| It's not a good idea to store them in SQL because BLOBs are stored outside of the database and there are some performance issues as well.I've used technique #2 and it works well. The documents are stored on the web server and the url along with some of the document properties are stored in the database. |
 |
|
|
yakoo
Constraint Violating Yak Guru
312 Posts |
Posted - 2002-05-29 : 11:06:52
|
quote:
can't seem to find a definate yes or no regarding storing BLOBs in a SQL 7 database
If you do a search on this site, I think you will find that most people will tell you to go with option #2.Got SQL? |
|
|
|
|
|
|
image / text data - storing office docs