Need help storing large text and images into SQL Server 6.5 
Author Message
 Need help storing large text and images into SQL Server 6.5

Anyone have an idea of using text and image data type?  I would like to
store documents and images into SQL Server 6.5.  I've found some
information on TEXTSIZE using pointers to point to the image or large text.
 I need  information on how to implement the actual storge and retrieval of
the data.  Any information on this topic is greatly appreciated.  



Mon, 28 Aug 2000 03:00:00 GMT
 Need help storing large text and images into SQL Server 6.5

Steve,

 Unless you have a damn good reason to store it in SQL then don't.  
Store it on a filesystem and just let SQL store a UNC path to it.

 Neil Pike MVP/MCSE
 Protech Computing Ltd



Sat, 02 Sep 2000 03:00:00 GMT
 Need help storing large text and images into SQL Server 6.5

Hi Neil,

I recognized that You avoid putting blobs in SS 6.5. We are using this
feature very well for a while.

What are Your experiences about that, making You that skeptical?

Michael

Quote:

> Steve,

>  Unless you have a damn good reason to store it in SQL then don't.
> Store it on a filesystem and just let SQL store a UNC path to it.

>  Neil Pike MVP/MCSE
>  Protech Computing Ltd



Sat, 02 Sep 2000 03:00:00 GMT
 Need help storing large text and images into SQL Server 6.5

Quote:
> I recognized that You avoid putting blobs in SS 6.5. We are using this
> feature very well for a while.

> What are Your experiences about that, making You that skeptical?

 Michael,

 Reasons I don't use it (in order)

 1.  How do you process/read/update the file/image?  readtext etc. is
horribly clumsy.  With a UNC name I can fire it straight into
Word/printing/OCR etc. etc.  Everything understands files in native format
- nothing understands embedded SQL objects.

 2.  I can use Index Server against a file system for free text searching.

 3.  Support people can get straight at the files using explorer/notepad
as they wish if they don't need a SQL interface.

 4.  Plenty of bugs with TEXT/IMAGE processing with SQL 6.x - some of
which have caused corruptions.  I don't like using buggy features which is
also why I don't (typically) use identity columns either.

 5.  All text/images take a minimum of 2K of database space regardless of
size.

 That's not to say that it doesn't work at all - it does - and many people
have good systems that work this way.

 Neil Pike MVP/MCSE
 Protech Computing Ltd



Mon, 04 Sep 2000 03:00:00 GMT
 Need help storing large text and images into SQL Server 6.5

Hi Neil,

look down a bit...

Quote:

> > I recognized that You avoid putting blobs in SS 6.5. We are using this
> > feature very well for a while.

> > What are Your experiences about that, making You that skeptical?

>  Michael,

>  Reasons I don't use it (in order)

>  1.  How do you process/read/update the file/image?  readtext etc. is
> horribly clumsy.  With a UNC name I can fire it straight into
> Word/printing/OCR etc. etc.  Everything understands files in native format
> - nothing understands embedded SQL objects.

We are inserting the objects (WinWord embedded, Excel embedded, Images
via appendchunk (VB))

Quote:
>  2.  I can use Index Server against a file system for free text searching.

Good argument. But our clients need a relativly strong security always
changing object per object, and I can realize this easily via DB.

Quote:
>  3.  Support people can get straight at the files using explorer/notepad
> as they wish if they don't need a SQL interface.

OK. We wrote code therefore...

Quote:
>  4.  Plenty of bugs with TEXT/IMAGE processing with SQL 6.x - some of
> which have caused corruptions.  I don't like using buggy features which is
> also why I don't (typically) use identity columns either.

Didn`t recognize one yet :-)...

Quote:
>  5.  All text/images take a minimum of 2K of database space regardless of
> size.

That is not a big problem, because our objects are in average 39K in
size.

But we`ve got several other considerations about that:

Replication: The db will go into replication with a few other systems in
future - and the blobs are a must...
WAN-Access: Some of the users will log into the db via a TCP/IP WAN
(Internet over cable-modem) - and they must have easy access to the
blobs. (And I didn`t want to write/manage several FTP-Sessions in
background...) -> administration/security (!) ...

Mobile users: I am only waiting for SS7 to manage my whole DB for
multiple servers and connectionless notebooks... Works good so far :-)
(That`s why I am using SS: I tried other dbs (Sybase, DB2, Oracle), but
Sybase and DB2 aren`t able to replicate Blobs, and oracle is too
expensive...

So I am waiting for SS7...

Michael

Quote:
>  That's not to say that it doesn't work at all - it does - and many people
> have good systems that work this way.

>  Neil Pike MVP/MCSE
>  Protech Computing Ltd



Mon, 04 Sep 2000 03:00:00 GMT
 Need help storing large text and images into SQL Server 6.5

Michael,

 Sounds like you've got the bases covered - SQL 7 will certainly
improve TEXT handling and remove some of the reasons I don't use it.

 Neil Pike MVP/MCSE
 Protech Computing Ltd



Thu, 07 Sep 2000 03:00:00 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. Need help storing large text and images into SQL Server 6.5

2. Ned help storing large text and images into SQL Server 6.5

3. Help - Storing large text fields within SQL Server????

4. Need help on retrieving OUTPUT parameter in stored procedure and Visual Interdev 6.0 - SQL Server 6.5

5. Does SQL Server 6.5 replicate text/image or not

6. Trying to fetch large text/memofields from SQL server 6.5 using ASP fails

7. Storing and Retrieving Images in SQL Server 6.5

8. Help: Image Datatype in Microsoft SQL Server 6.5

9. HELP: Images on SQL-Server 6.5 / 7.0

10. Need to insert text field in SQL Server 6.5

11. Need Help with ODBC/MS SQL Server 6.5/Peer Web Server 3.0/Frontpage Problem


 
Powered by phpBB® Forum Software