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 |
|
gsnk
Starting Member
24 Posts |
 Posted - 2002-07-15 : 13:26:20
|
| Could someone point me to good information (either on sqlteam or outside sources) regarding storing binary data (images, docs, etc.) in the database vs. storing them through the file system and only capturing a pointer in the db?thanks a bundle.Gero**It's better to light a candle than to curse the darkness.** |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-07-15 : 14:40:47
|
| The SQL Team FAQ has an entry about it:http://www.sqlteam.com/FAQ.aspThe general wisdom is to keep binary images and document files on the file system instead of stored in an image or text column in SQL Server. Nevertheless the FAQ article will show you how to do it. You should also do a forum search on SQL Team.The fact is that keeping the files in the database itself adds a layer of compelixity when inserting, retrieving, or modifying the data. IMHO, keeping that data in a disk file instead, and storing a link to that file in the database, makes more sense because it avoids this extra complexity.The one single advantage I can see is if you wanted to full-text search a Word or Excel document, but only if you have SQL 2000. Even then, you can still use the Windows indexing service to perform full-text searches on disk files just as easily, and regardless of SQL Server version. |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-07-15 : 14:55:43
|
| If you save as files then you save network traffic to and from the database server - can store them as close as possible to the delivery point and easily move them arond.==========================================Cursors are useful if you don't know sql.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
BLOB vs. File System storage