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 |
|
amsqlguy
Yak Posting Veteran
89 Posts |
 Posted - 2009-03-28 : 12:15:09
|
| I am exploring the option of moving 15mill tiff images into SQL Server 2005 database. What are the pros and cons of string images in SQL Server 2005 as opposed to file system. Are there any article or white papers suggesting the pros and cons? |
|
|
cshah1
Constraint Violating Yak Guru
347 Posts |
Posted - 2009-03-28 : 14:35:27
|
| There are pros and cons of each approach, storing iamges directly in the database vs file stream.[url]http://databases.aspfaq.com/database/should-i-store-images-in-the-database-or-the-filesystem.html[/url]I would prefer to store them in the file system. In SQL Server 2008, there is a filestream datatype that provide better trade off for this kind of operation. |
 |
|
|
TonyTheDBA
Posting Yak Master
121 Posts |
Posted - 2009-03-30 : 07:53:10
|
| Nice outline of the potential problems . . . We are in this situation at the moment with a supplier that stores image data in the database. Its fine, but when you then add a developemnt instance(s), a test instance, train instance, and a reporting instance, you do end up duplicating an awful lot of data . . . which Impacts backup / restore times . . . If you anonymise data for the instances how do you anonymise the image data?? This is important in our case as the images are scans of letters and forms which hold personal confidential information . . . Luckily our developers looked at it logiaclly with thier apps and hold the image data on a filestore server with UNC filenames stored in the database . . .Deletion is not yet an issue as our users don't believe in deleting any data-- RegardsTony The DBA |
|
|
|
|
|
|
Storing Images in SQL Server 2005