Re: chunking in binary (BLOB) data for generic providers



Michael,

You never visited probably our (free of advertising) website.

http://www.vb-tips.com/dbpages.aspx?ID=0bf3f72d-b722-459d-8a46-38b5a2f7fdf0

that it is a image does not matter, although if it is a document I would
even first zip it.

(How to do that is AFAIK as well on our website)

I hope this helps,

Cor

"Michael Burstin" <mburstin@xxxxxxxxxxxxxxxxx> schreef in bericht
news:O2tI$QP2GHA.1040@xxxxxxxxxxxxxxxxxxxxxxx
I think that the answer is no, but is there a generic way to insert BLOB
data into a table in a generic method via ADO.Net in blocks/chunks? From
reading all examples, questions, and other information I can find on
various web sites, newsgroup posts, etc, it appears to be no.

For example, if I have a large binary object that I want to store in a
database (ignoring the philosophical debate of whether this should be in
the database), I certainly don't want to load a 100MB of data and transmit
it across the wire in one piece.

All other database access methods (ODBC via SQLPutData, JDBC, etc) support
inserting data in chunks. Reading MSDN docs, it appears that old ADO
does.
(http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q308042)

ADO.Net doesn't appear to:
http://support.microsoft.com/kb/317016/

The only thing I see even close to it is using proprietary SQL2005
extensions for update.write.
http://msdn2.microsoft.com/en-us/library/a1904w6t.aspx
http://staceyw.spaces.live.com/Blog/cns!1pnsZpX0fPvDxLKC6rAAhLsQ!404.entry

This seems to be a step backwards from ADO and even ODBC.


.



Relevant Pages

  • Re: Which database support?
    ... ADO is likely the better way to go, although ODBC is a close second. ... but *only* if the target database is based on the MSFT Jet Engine ... ADO is built on OLEDB; Both are based on a set of interfaces defined by ...
    (microsoft.public.vc.mfc)
  • Re: Regarding fastest database interaction with Oracle in VC++
    ... access Oracle database using VC++. ... It only use ODBC if the OLE DB provider for ODBC is used as the ADO ... Using native OLD DB providers with ADO is fastest and does not use ODBC. ...
    (microsoft.public.vc.database)
  • Re: Which database support?
    ... it presumes that the user is apparently interacting with the database through ... >ADO is likely the better way to go, although ODBC is a close second. ... >ADO is built on OLEDB; Both are based on a set of interfaces defined by ...
    (microsoft.public.vc.mfc)
  • Re: Which database support?
    ... it presumes that the user is apparently interacting with the database through ... >>ADO is likely the better way to go, although ODBC is a close second. ... >>ADO is built on OLEDB; Both are based on a set of interfaces defined by ...
    (microsoft.public.vc.mfc)
  • ADO Vs ODBC Data types and formatting.
    ... I am replacing a VB5 application that handles database communication ... directly through ODBC API calls with a VB5 application that uses ADO ... I am having some issues with mapping the data types returned by ODBC ...
    (microsoft.public.sqlserver.odbc)