| Groups | Blog | Home |
dotnet ado.net : ASP.Net - Access 2003 - Large BLOBs
PDFs, Excel Spreadsheets, Videos, and Images in an Access 2003 database. We have not yet upgraded the database to SQL Server as it is still in the development and testing stages. Unable to utilize administrative webforms that insert BLOBS in excess of 4MB. No problems with any of the documents that are 2MB or less. Objects range up to 110MB. Using the following code to read file: Stream ms = filSource.PostedFile.InputStream; BinaryReader br = new BinaryReader(ms); byte[] byteArray = br.ReadBytes((int)filSource.PostedFile.ContentLength); br.Close(); Object is inserted into the database as a parameter, OleDbType.LongVarBinary. Docs indicate that the max field size is 1GB so should work. Any ideas? -- Rich S www.24x7systems.net
Are you trying to read these blobs into an Access OLE field with the
idea that you are eventually going to migrate them to a SQL Server table? If so, this is a really bad idea for any database, but especially for Access. It has a long tradition of choking on large blobs, becoming easily corrupted in the process. Even for SQL Server, which is a more robust platform by far, recommended best practice is to store the blobs on the file system and simply record the location in a table. --Mary On Tue, 23 Nov 2004 16:25:03 -0600, "Rich S" <rich@arslist.info> [quoted text, click to view] wrote:
>Working on C#/ASP.Net application in which we are storing secure, private >PDFs, Excel Spreadsheets, Videos, and Images in an Access 2003 database. We >have not yet upgraded the database to SQL Server as it is still in the >development and testing stages. > >Unable to utilize administrative webforms that insert BLOBS in excess of >4MB. No problems with any of the documents that are 2MB or less. Objects >range up to 110MB. > >Using the following code to read file: > >Stream ms = filSource.PostedFile.InputStream; > >BinaryReader br = new BinaryReader(ms); > >byte[] byteArray = br.ReadBytes((int)filSource.PostedFile.ContentLength); > >br.Close(); > >Object is inserted into the database as a parameter, >OleDbType.LongVarBinary. > >Docs indicate that the max field size is 1GB so should work. Any ideas?
Mary,
In my opinion is your message true, however I have another idea for thumbnails. Just to make your message not as black and white as it looks like now. Cor "Mary Chipman" <mchip@online.microsoft.com> [quoted text, click to view] > Are you trying to read these blobs into an Access OLE field with the > idea that you are eventually going to migrate them to a SQL Server > table? If so, this is a really bad idea for any database, but > especially for Access. It has a long tradition of choking on large > blobs, becoming easily corrupted in the process. Even for SQL Server, > which is a more robust platform by far, recommended best practice is > to store the blobs on the file system and simply record the location > in a table. > > --Mary > > On Tue, 23 Nov 2004 16:25:03 -0600, "Rich S" <rich@arslist.info> > wrote: > >>Working on C#/ASP.Net application in which we are storing secure, private >>PDFs, Excel Spreadsheets, Videos, and Images in an Access 2003 database. >>We >>have not yet upgraded the database to SQL Server as it is still in the >>development and testing stages. >> >>Unable to utilize administrative webforms that insert BLOBS in excess of >>4MB. No problems with any of the documents that are 2MB or less. Objects >>range up to 110MB. >> >>Using the following code to read file: >> >>Stream ms = filSource.PostedFile.InputStream; >> >>BinaryReader br = new BinaryReader(ms); >> >>byte[] byteArray = br.ReadBytes((int)filSource.PostedFile.ContentLength); >> >>br.Close(); >> >>Object is inserted into the database as a parameter, >>OleDbType.LongVarBinary. >> >>Docs indicate that the max field size is 1GB so should work. Any ideas? >
???
On Thu, 25 Nov 2004 15:44:15 +0100, "Cor Ligthert" [quoted text, click to view] <notmyfirstname@planet.nl> wrote:
>Mary, > >In my opinion is your message true, however I have another idea for >thumbnails. > >Just to make your message not as black and white as it looks like now. > >Cor > >"Mary Chipman" <mchip@online.microsoft.com> > >> Are you trying to read these blobs into an Access OLE field with the >> idea that you are eventually going to migrate them to a SQL Server >> table? If so, this is a really bad idea for any database, but >> especially for Access. It has a long tradition of choking on large >> blobs, becoming easily corrupted in the process. Even for SQL Server, >> which is a more robust platform by far, recommended best practice is >> to store the blobs on the file system and simply record the location >> in a table. >> >> --Mary >> >> On Tue, 23 Nov 2004 16:25:03 -0600, "Rich S" <rich@arslist.info> >> wrote: >> >>>Working on C#/ASP.Net application in which we are storing secure, private >>>PDFs, Excel Spreadsheets, Videos, and Images in an Access 2003 database. >>>We >>>have not yet upgraded the database to SQL Server as it is still in the >>>development and testing stages. >>> >>>Unable to utilize administrative webforms that insert BLOBS in excess of >>>4MB. No problems with any of the documents that are 2MB or less. Objects >>>range up to 110MB. >>> >>>Using the following code to read file: >>> >>>Stream ms = filSource.PostedFile.InputStream; >>> >>>BinaryReader br = new BinaryReader(ms); >>> >>>byte[] byteArray = br.ReadBytes((int)filSource.PostedFile.ContentLength); >>> >>>br.Close(); >>> >>>Object is inserted into the database as a parameter, >>>OleDbType.LongVarBinary. >>> >>>Docs indicate that the max field size is 1GB so should work. Any ideas? >> >
Mary,
In my opinion is a blob field with a thumbnail field and a field with the path to the actual image the nicest way to do it. And not only as you write holding the path to an image in a database. Cor "Mary Chipman" <mchip@online.microsoft.com> schreef in bericht news:jb0fq0thea1v6fs566dbcloe1m4q9id6pa@4ax.com... [quoted text, click to view] > ??? > > On Thu, 25 Nov 2004 15:44:15 +0100, "Cor Ligthert" > <notmyfirstname@planet.nl> wrote: > >>Mary, >> >>In my opinion is your message true, however I have another idea for >>thumbnails. >> >>Just to make your message not as black and white as it looks like now. >> >>Cor >> >>"Mary Chipman" <mchip@online.microsoft.com> >> >>> Are you trying to read these blobs into an Access OLE field with the >>> idea that you are eventually going to migrate them to a SQL Server >>> table? If so, this is a really bad idea for any database, but >>> especially for Access. It has a long tradition of choking on large >>> blobs, becoming easily corrupted in the process. Even for SQL Server, >>> which is a more robust platform by far, recommended best practice is >>> to store the blobs on the file system and simply record the location >>> in a table. >>> >>> --Mary >>> >>> On Tue, 23 Nov 2004 16:25:03 -0600, "Rich S" <rich@arslist.info> >>> wrote: >>> >>>>Working on C#/ASP.Net application in which we are storing secure, >>>>private >>>>PDFs, Excel Spreadsheets, Videos, and Images in an Access 2003 database. >>>>We >>>>have not yet upgraded the database to SQL Server as it is still in the >>>>development and testing stages. >>>> >>>>Unable to utilize administrative webforms that insert BLOBS in excess of >>>>4MB. No problems with any of the documents that are 2MB or less. >>>>Objects >>>>range up to 110MB. >>>> >>>>Using the following code to read file: >>>> >>>>Stream ms = filSource.PostedFile.InputStream; >>>> >>>>BinaryReader br = new BinaryReader(ms); >>>> >>>>byte[] byteArray = >>>>br.ReadBytes((int)filSource.PostedFile.ContentLength); >>>> >>>>br.Close(); >>>> >>>>Object is inserted into the database as a parameter, >>>>OleDbType.LongVarBinary. >>>> >>>>Docs indicate that the max field size is 1GB so should work. Any ideas? >>> >> >
OIC -- yes, a nice way to do it if it's just images. But of less
utility with large spreadsheets and pdf's, as is the case here. --Mary On Sat, 27 Nov 2004 09:19:27 +0100, "Cor Ligthert" [quoted text, click to view] <notmyfirstname@planet.nl> wrote:
>Mary, > >In my opinion is a blob field with a thumbnail field and a field with the >path to the actual image the nicest way to do it. And not only as you write >holding the path to an image in a database. > >Cor > >"Mary Chipman" <mchip@online.microsoft.com> schreef in bericht >news:jb0fq0thea1v6fs566dbcloe1m4q9id6pa@4ax.com... >> ??? >> >> On Thu, 25 Nov 2004 15:44:15 +0100, "Cor Ligthert" >> <notmyfirstname@planet.nl> wrote: >> >>>Mary, >>> >>>In my opinion is your message true, however I have another idea for >>>thumbnails. >>> >>>Just to make your message not as black and white as it looks like now. >>> >>>Cor >>> >>>"Mary Chipman" <mchip@online.microsoft.com> >>> >>>> Are you trying to read these blobs into an Access OLE field with the >>>> idea that you are eventually going to migrate them to a SQL Server >>>> table? If so, this is a really bad idea for any database, but >>>> especially for Access. It has a long tradition of choking on large >>>> blobs, becoming easily corrupted in the process. Even for SQL Server, >>>> which is a more robust platform by far, recommended best practice is >>>> to store the blobs on the file system and simply record the location >>>> in a table. >>>> >>>> --Mary >>>> >>>> On Tue, 23 Nov 2004 16:25:03 -0600, "Rich S" <rich@arslist.info> >>>> wrote: >>>> >>>>>Working on C#/ASP.Net application in which we are storing secure, >>>>>private >>>>>PDFs, Excel Spreadsheets, Videos, and Images in an Access 2003 database. >>>>>We >>>>>have not yet upgraded the database to SQL Server as it is still in the >>>>>development and testing stages. >>>>> >>>>>Unable to utilize administrative webforms that insert BLOBS in excess of >>>>>4MB. No problems with any of the documents that are 2MB or less. >>>>>Objects >>>>>range up to 110MB. >>>>> >>>>>Using the following code to read file: >>>>> >>>>>Stream ms = filSource.PostedFile.InputStream; >>>>> >>>>>BinaryReader br = new BinaryReader(ms); >>>>> >>>>>byte[] byteArray = >>>>>br.ReadBytes((int)filSource.PostedFile.ContentLength); >>>>> >>>>>br.Close(); >>>>> >>>>>Object is inserted into the database as a parameter, >>>>>OleDbType.LongVarBinary. >>>>> >>>>>Docs indicate that the max field size is 1GB so should work. Any ideas? >>>> >>> >> >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |