Re: drawbacks of Saving documents to Sql server

Bryan, another question,
why did you choose 64K byte and not any other number? what are the drawbacks
of uploading the whole document in 1 shot?

thanks

"sameer" wrote:

thanks for the reply guys,

Bryan : i am already using Gzip compressing, it really does help. could you
by anychance know or have the code to retrive the documents from the database
as you have mentioned ?

Steve : about the code that you have mentioned which is more optmized in
retriving documents, do you think u might be able to point me to online
resource or share it with me.

running on a very strick deadline, any help is appreciated.

thanks

"Steve" wrote:

I too have done this.

We also wrote some tests

Retrieving random documents from SQL was faster than retrieving random
documents from the file system., it was much much faster.

Writing random documents to SQL was slower than the file system.

To get good read speeds, we wrote our own stream class that streamed the
data from SQL.

SQLs is better at locating the doc when you have millions off rows.

One more plus point is transactions, you can have a transaction for writing
you doc to SQL, so you can :

Update metadata
Write doc
Do some other SQL stuff

and its all in one transaction, so you can easily roll back.

Steve

"Bryan Phillips" <bphillips@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23u6CLYa8GHA.3280@xxxxxxxxxxxxxxxxxxxxxxx
1. I have done this before with various sized Word docs. The performance
penalty was not noticeable.
2. Retrieving the files from the file system is always faster but not
necessarily better. Flat-file databases are faster than relational
databases but the features of the relational database outweigh the
performance hit.
3. The biggest problem with the files will be transport between the web
server and the web client. I broke the files into 64K chunks and
up/downloaded them via a web service. In the database I used a table to
store a "header" record with one row per file containing the filename,
filesize, number of 64K chunks, etc... Another child table was the
"detail" table with one row per file chunk. An image column was used to
store the actual chunk of binary data.
4. SQL Server 2005 performs better than SQL Server 2000 hands down.

Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com




"sameer" <sameer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EC07B737-4741-4D74-B581-14FE6C758471@xxxxxxxxxxxxx:

Hi all,

.Net 1.1
Sql server 2000

i am working on a document managment module of my application, all i want
to
do here is save the documents uplaoded by the user from my winforms over
webservices application\ webforms applicatoin to sql server 2000. I have
been
told saving it on the webserver's file system might be a better way but
seems
that microsft is gong more towars saving everthing in sql server. So my
question to the gurus out there is

1. does any one really have any hands on experience saving documents to
sql
server 2000 and if so please tell me if u have any kind of performance
issues
with this.

2. i was told that sql server is kind of a little slow in streaming out
the
documents from the database, expecially bigger ones when compared to the
retriving it from the web server's file system, is this true ?

3. please tell me any other problesm that u might have faced when
saving\
retriving files from the database.

4. is sql server 2005 any better in saving and retriving documents from
the
database.

thanks

sameer



.

Relevant Pages

  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MS Access DAO -> ADO.NET Migration
    ... full SQL Server and I see the logic you explained in a multi user ... allow two users to access the same database file Read/Write at any given ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... Hitchhiker's Guide to Visual Studio and SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MS Access DAO -> ADO.NET Migration
    ... For that it is much harder to handle the incremental identifier, ... database but although they have the data, they are not connected at the same ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... SQL Server Management Studio is nowhere to be found on my ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Word 2003/Access2000/SQLSVR
    ... SQL server being where the data is held and this is accessed through a MS ... entire database and that may be say a record for Berkshire. ... "Peter Jamieson" wrote: ... replaced with the first record on the table in use. ...
    (microsoft.public.word.mailmerge.fields)