Opinions: Storing large .exe's as BLOB's in a table 
Author Message
 Opinions: Storing large .exe's as BLOB's in a table

I am tasked with designing a method for client app's to pull new releases
from a server. This is shrink-wrap software and I cannot know what the
network environment will be (Win2k, Novell, etc.)   I cannot setup shared
drives or other network resources to allow clients to gain access to the new
release file. The client app uses only SQL authentication to gain access to
the db.

One idea here is to store the self-extracting executable as a BLOB in a
table. The executable size could be quite large (>50MB). This scheme seems
like it would waste a lot of DB space, as well as being slow and clunky.

I am wondering about any other potential problems injecting a large BLOB
could have on other areas of the DB or the app. Could doing this affect
performance of db operations on other tables?

I realize db backups will create larger files, but could it cause a
slow-down of the server/db in general?

Thanks!

Mike Dudash



Mon, 29 Nov 2004 00:46:44 GMT
 Opinions: Storing large .exe's as BLOB's in a table

Mike,

Just curious, how would you run these executables if they are
stored as BLOBs in the table?

- Anith


Quote:
> I am tasked with designing a method for client app's to pull new releases
> from a server. This is shrink-wrap software and I cannot know what the
> network environment will be (Win2k, Novell, etc.)   I cannot setup shared
> drives or other network resources to allow clients to gain access to the
new
> release file. The client app uses only SQL authentication to gain access
to
> the db.

> One idea here is to store the self-extracting executable as a BLOB in a
> table. The executable size could be quite large (>50MB). This scheme seems
> like it would waste a lot of DB space, as well as being slow and clunky.

> I am wondering about any other potential problems injecting a large BLOB
> could have on other areas of the DB or the app. Could doing this affect
> performance of db operations on other tables?

> I realize db backups will create larger files, but could it cause a
> slow-down of the server/db in general?

> Thanks!

> Mike Dudash



Mon, 29 Nov 2004 03:11:33 GMT
 Opinions: Storing large .exe's as BLOB's in a table
I was hoping to deal with the BLOB data like an image (jpg/bmp). Read the
BLOB data line by line into a file on the client's filesystem (using
GetChunk/AppendChunk or fastest equivalent). Then popup a window showing the
file as an icon for the user to click on and run.


Quote:
> Mike,

> Just curious, how would you run these executables if they are
> stored as BLOBs in the table?

> - Anith



> > I am tasked with designing a method for client app's to pull new
releases
> > from a server. This is shrink-wrap software and I cannot know what the
> > network environment will be (Win2k, Novell, etc.)   I cannot setup
shared
> > drives or other network resources to allow clients to gain access to the
> new
> > release file. The client app uses only SQL authentication to gain access
> to
> > the db.

> > One idea here is to store the self-extracting executable as a BLOB in a
> > table. The executable size could be quite large (>50MB). This scheme
seems
> > like it would waste a lot of DB space, as well as being slow and clunky.

> > I am wondering about any other potential problems injecting a large BLOB
> > could have on other areas of the DB or the app. Could doing this affect
> > performance of db operations on other tables?

> > I realize db backups will create larger files, but could it cause a
> > slow-down of the server/db in general?

> > Thanks!

> > Mike Dudash



Mon, 29 Nov 2004 03:23:25 GMT
 Opinions: Storing large .exe's as BLOB's in a table
Mike,

Slowdown can occur if those who are reading the blob data then can flush out other things from
cache. Also, watch out for transaction log handling. You can do WRITETEXT/UPDATETEXT in
minimally-logged form, but that will affect your backup/restore options.

--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...

Quote:

> I was hoping to deal with the BLOB data like an image (jpg/bmp). Read the
> BLOB data line by line into a file on the client's filesystem (using
> GetChunk/AppendChunk or fastest equivalent). Then popup a window showing the
> file as an icon for the user to click on and run.



> > Mike,

> > Just curious, how would you run these executables if they are
> > stored as BLOBs in the table?

> > - Anith



> > > I am tasked with designing a method for client app's to pull new
> releases
> > > from a server. This is shrink-wrap software and I cannot know what the
> > > network environment will be (Win2k, Novell, etc.)   I cannot setup
> shared
> > > drives or other network resources to allow clients to gain access to the
> > new
> > > release file. The client app uses only SQL authentication to gain access
> > to
> > > the db.

> > > One idea here is to store the self-extracting executable as a BLOB in a
> > > table. The executable size could be quite large (>50MB). This scheme
> seems
> > > like it would waste a lot of DB space, as well as being slow and clunky.

> > > I am wondering about any other potential problems injecting a large BLOB
> > > could have on other areas of the DB or the app. Could doing this affect
> > > performance of db operations on other tables?

> > > I realize db backups will create larger files, but could it cause a
> > > slow-down of the server/db in general?

> > > Thanks!

> > > Mike Dudash



Mon, 29 Nov 2004 18:15:04 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Query performance on 'large' tables

2. Query, large table, 'out of memory'

3. Q:Retrieving newest .exe's from a database Blob field

4. Can't insert large Blob/Ole Data with Access97 in SQL 7.0

5. Exe's files stored in Sql

6. Exe's files stored in Sql

7. Storing files in Oracle's blobs(Problem)

8. Storing Word format text in SQL using BLOB's

9. store and load blob's

10. Access Violation in module 'ProfitAnalyzer.exe'

11. exec xp_cmdshell 'dir *.exe'

12. **************!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Help me !!!!!!!!!!!!!!!!!!!!!!!!'''''''''''''''''''''''*************


 
Powered by phpBB® Forum Software