image field

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Gabriel Pineda - 18 May 2008 23:05 GMT

hi everybody, i have a problem with an image field in mssql 2005.
it's the firt time i use it, and what i see is that every query that include
the image field is very slow.

how can i increase the speedy to make the querys faster?

thank you all!

Reply to this Message

John Bell - 19 May 2008 09:19 GMT

> hi everybody, i have a problem with an image field in mssql 2005.
> it's the firt time i use it, and what i see is that every query that
[quoted text clipped - 4 lines]
>
> thank you all!

Hi

You may want to look at
http://databases.aspfaq.com/database/should-i-store-images-in-the-database-or-th
e-filesystem.html,
if you are going to include the image field why are you returning it in so
many queries?

John

Reply to this Message

Rob - 18 Jul 2008 14:25 GMT

John,

I have a similar problem. I use SQL 2005 as the back end for an Access
application. I have set up an image field in SQL which translates to an OLE
Object field in Access (exactely what I want). I have placed an unbound
object control on a form that uses the OLE object field from the table. When
I right-click and insert object I have a problem. I can choose to create
from file, browse and select the file. I am also choosing to link to save
space. When I click on okay Access hangs and I have to stop the task. If I
set up a new table in Access with an OLE Object field and use it there are
not problems - only with SQL. Any suggestions?

Rob

> > hi everybody, i have a problem with an image field in mssql 2005.
> > it's the firt time i use it, and what i see is that every query that
[quoted text clipped - 13 lines]
>
> John

Reply to this Message

Rob - 22 Jul 2008 15:08 GMT

John,

The link option when inserting an object allows you to see the object but
not store it in the database. It is very handy in Access to keep the file
size at a minimum. When I choose not to link it still locks up the database.
Funny, I can choose the create from new and choose a program like paint and
save that file and it has no problem. Only with the option to select an
existing file. How does one normally show stored images on a form with SQL
as the back end? I do not retrieve the data via a query. I only what to
show the picture when I view the record via a form.

> John,
>
[quoted text clipped - 27 lines]
> >
> > John

Reply to this Message

John Bell - 23 Jul 2008 20:51 GMT

> John,
>
[quoted text clipped - 9 lines]
> as the back end? I do not retrieve the data via a query. I only what to
> show the picture when I view the record via a form.

Hi Rob

See the links on

http://databases.aspfaq.com/database/should-i-store-images-in-the-database-or-th
e-filesystem.html

John

Reply to this Message

Aaron Bertrand [SQL Server MVP] - 19 May 2008 14:37 GMT

Are your queries using SELECT *? Or are you otherwise including the IMAGE
column even in queries that don't even need it?

You should compare performance with having the file on the file system and
SQL Server just storing the path. SQL Server wasn't really designed to be a
file repository like Windows Explorer, and you will undoubtedly observe the
symptom of overhead when pushing data in and out of the database layer.

That said, SQL Server 2008 will provide you with FILESTREAM which is the
best of both worlds... database transactional consistency and file system
performance.

On 5/18/08 6:05 PM, in article
EE564C57-D1C9-4277-BC9C-D9B4F16234AA@microsoft.com, "Gabriel Pineda"
<gabrielpineda2001@hotmail.com> wrote:

> hi everybody, i have a problem with an image field in mssql 2005.
> it's the firt time i use it, and what i see is that every query that include
[quoted text clipped - 3 lines]
>
> thank you all!

Reply to this Message