Uncategorized

Images in the Database – Reader Feedback Continues

SelectViews Show
The Weekly SQL Server show about all sorts of different things from how-to to commentary has been updated. This weeks show: Replication Troubleshooting, Managing SQL Server as a Part-Time DBA, Web 2.0 Book(s) Reviewed, Noise and News in the DB world. Also, the 60-Second SQL Server Tip of the Day, Upcoming Events and Information About the Virtual Conference. Lots on the Show!

Watch the Show Here, Online

Featured Article(s)
Checking Over sized Log file growth TSQL procedure
The following procedure checks using a cross reference between sp_HelpDb AND DBCC SQLPERF (‘LOGSPACE’) tsql statements if a the log file is over sized. This check is done by comparing the total size of the database to the size of the log file. If the Data file size is less than the log file then this log is reported as an over sized log file

Images In, Or Out, Of The Database
Several readers provided feedback about the pros and cons of storing image data in the database. Generally, traditional advice of course is that you store a link to the image file, but not the image itself, in the database. There are exceptions, but this is usually the suggestion. Now however, databases are much better about these types of data types – but issues do remain. Here are more reader feedback emails:

Kevin: "The main problem I have encountered storing files in the database is a performance/efficiency problem.

At least with SQL Server and ADO.NET it appears the only way to get a file in is to create a byte[] containing the entire file and pass that as a parameter. If the file is sufficiently large this behavior has a lot of downsides. If I could specify a stream instead of a byte array I would agree that putting the files in the database is a viable option.

Of course, if you’re only reading the files from the database and not adding files, as in the example of using the images on a website, this isn’t an issue."

Read more in his blog here.

Wayne: "Yes, store them in the db. I know there are cases against it and every expert seems to have their own opinion, however, if managed properly they should not be a problem in the db.

Our business stores front and back images of checks that are cashed by customers. I purge the images out into a separate archive database and only keep 30-days of image data in the live transaction db. Storing them that way makes the db more efficient and one restore gets everything back.

I was inclined to store our images in the db from the start (about 5 years ago), but was not sure if I should. My research turned up an article by Microsoft (wish I could find it again) discussing the pros and cons. My decision was confirmed when I learned they store the images for the Terra Server in the db. Good enough for them, certainly good enough for me."

Ben: "I think it’s also important to look to the future. SQL Server 2008 has some great file management functionality that will make managing documents and images much easier than in the past. As SQL Server continues to mature into a “data management platform” instead of just a relational database engine, the likelihood of systems storing images and documents in the database becomes greater. In the end, I think it will always benefit a system to keep data and document storage simple and consolidated and these new enhancements make it not only more possible but also more feasible."

More to come. Send in your thoughts and feedback here.

Webcast: SQL Server Crystal Ball: Knowing What to Watch As Your SQL Server System Grows
We’ll look into pulling baseline information, things you can do to chart and forecast growth on your system and the basic options you have to grow you system Out and Up. Find out how to use Performance Monitor tools and learn about what different scaling techniques can bring to the table.

> Register Now
> Nov 13 2007 12:00pm Noon Pacific

Webcast: Creating, Managing and Reviewing Jobs with SQL Server 2005
We’ll show how to create a job, work through the different options,including notifications, variable job steps, scheduling and more. The goal of this session is to have you up and running, understanding how the options work for setting up and managing jobs in your system.

> Register Now
> Nov 14 2007 12:00pm Noon Pacific

Featured White Paper(s)
GridApp Clarity™ SQL Server
The relational database product landscape, formerly a monolithic list of a few 800-pound gorillas, now spans a broad range of… (read more)

Selecting the Right Change Management Solution
Frequent application updates, data migrations, service level requirements, and new compliance mandates mean your company need… (read more)

Top 10 Things You Should Know about Optimizing SQL Server Performance
Performance optimization on SQL Server is difficult. A vast array of information exists on how to address performance problem… (read more)

Business Objects and Microsoft Interoperability
This document discusses how customers using Microsoft and Business Objects technologies can maximize the interoperability fro… (read more)