Updating image to sql server using vfp
For the old TEXT, NTEXT, and IMAGE data types, which SQL Server 2005 continues to support, you can use the option.
Storing smaller BLOB data inline improves performance, avoiding the extra I/O needed to read the BLOB data record.
But before jumping into the code, let’s review the key elements of SQL Server’s BLOB storage.
SQL Server stores standard INT, CHAR, and VARCHAR data directly within a row.
However, technically, CLOBs can contain only text data such as XML, whereas BLOBs can contain any type of data, including binary data.
(Note that with SQL Server 2005’s row-overflow feature, the maximum row size can exceed 8060 in certain cases; for information about this feature, see Kalen Delaney's "Stretching the 8K Row Limit.") Although more than adequate for most data types, the 8KB limit is a problem for most BLOB data.
As the sidebar "Storing BLOBs in the Database or the File System?
" discusses, integrating BLOB data and relational database data has its pros and cons.
Relational data usually consists of text or numbers and tends to be small.
In contrast, BLOB data is most often pictures in .jpg, .tiff, or format—such as product images on a Web site—which can be quite large.