|
|
Posted by Erland Sommarskog on 05/19/06 00:39
KR (kraman@bastyr.edu) writes:
> Where we store these documents are not under our control - the
> application is designed by a third-party. So we have to go with their
> decision - what we are trying to do is to analyze any problems that
> may present due to this and devise a solution or go to the software
> vendor with recommendations.
>
> The documents in the file system are backed up separatley from the
> database. We cannot do Log shipping on our databases since we have SQL
> Standard edition. We backup our transaction logs periodically to a
> network 'store' and restore the transaction logs periodically on the
> two standby server using a stored procedure.
>
> What we are also concerned here is the possible effect on the size of
> transaction log due to updates and inserts on these BLOB fields, the
> backup and restore time.
It goes without saying that the more data you store in the database,
the longer time the backup will take, and the more size is needed for
the transaction log.
I don't have any information about BLOBs and backups per se, but I find
it difficult to believe that a 1MB blob would take any significant more
toll on backup and log than 10000 rows of 100 bytes.
What you should do, is to find an estimate on many documents there
will be in the database, and how many that will be inserted, updated
and deleted per day. And of course, the expected average size of the
documents.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|