Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 SQL Image type

Author  Topic 

skillile
Posting Yak Master

208 Posts

Posted - 2003-04-13 : 23:52:21
I am going to use the SQL IMAGE type to store about 120 docs that need to be secured. Can anybody help me with the code to both insert/update and select the data out of the server. I am using classic ADO. I have have only seen it with inline SQL not a SPROC. Can I use the advbbinary (something like that) to insert with a SPROC. I have never tried this before and I am looking for best practice assuming I need to use this route of storage.

Thanks

BTW. SQL Server is 2K and file type is DOC, XLS about 20-40Mb file size

slow down to move faster...

Merkin
Funky Drop Bear Fearing SQL Dude!

4970 Posts

Posted - 2003-04-14 : 00:08:57
I really suggest you don't.
But if you have to, there are some links in this article.

http://www.sqlteam.com/item.asp?ItemID=986



Damian
Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2003-04-14 : 23:58:02
quote:
I am going to use the SQL IMAGE type to store about 120 docs that need to be secured.
Why do you think putting them in the database will make them more secure? Just because they'll be more difficult to extract? Anyone with access to that table can get them all...if they actually have the patience to retrieve them. If you want them to be secure, just burn them onto a CD-R, destroy all the other copies, and lock it away in a desk somewhere, it'll be more secure and probably easier to retrieve.
quote:
BTW. SQL Server is 2K and file type is DOC, XLS about 20-40Mb file size
OK, you gotta be kidding me...who in the world is actually using a 20-40 MB Excel file???? Much less 120 of them!!

And you can't seriously think that putting this into and retrieving it from SQL Server is going to improve anything. You stand an excellent chance of having that file(s) get irrecoverably corrupted during the procedure. Not to mention that putting it into an image column will not be logged (by default), and if you DO log it, your transaction log will balloon and explode long before all of these documents are stored in the database.

Do yourself the greatest favor in the world and keep these files on a disk drive somewhere, anywhere, as long as it's OUTSIDE of SQL Server. You can lock down the drive, folder, and files themselves with the appropriate permissions. More can be found here:

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=24566

Go to Top of Page
   

- Advertisement -