Storing Tiff files

Printable View

10-10-2007, 04:13 PM
daljitsb

Storing Tiff files

What is the best way to store 100 of thousands of .jiff files (<3 MB each) to be used (creating and retreiving) in .net c# new application using oracle 10g db.

We will also need to migrate existing files working with old VB application (with sqlserver) to .net c# application (using oracle 10g)

SO the next question will be to: what is the best way to migrate these files into new db/system

Please advice.
Thanks
10-10-2007, 05:26 PM
davey23uk

use blobs
10-11-2007, 05:22 PM
daljitsb

Quote:

Originally Posted by davey23uk

use blobs

Can we not store .tiff file as bfile - store it in file system and save the pointer to file in the database and keep the database small. What are the pros and cons for different options.

Our application is going to be configurable to work with both sqlserver and oracle db and We do want to store the files on file system in sqlserver db.
10-11-2007, 08:59 PM
PAVB

Quote:

Originally Posted by daljitsb

Can we not store .tiff file as bfile - store it in file system and save the pointer to file in the database and keep the database small. What are the pros and cons for different options.

The idea of storing files outside the database is nothing new; think about backup consistency.

Quote:

Originally Posted by daljitsb

Our application is going to be configurable to work with both sqlserver and oracle db and We do want to store the files on file system in sqlserver db.

Nice idea, hard to implement. Your backend code will be totally different.
10-12-2007, 05:16 PM
daljitsb

Quote:

Originally Posted by PAVB

Nice idea, hard to implement. Your backend code will be totally different.

For that we are planning to use ORM tool and have most business logic in application.

So which way you suggest - Blobs v/s file system (Bfile)
10-12-2007, 05:36 PM
PAVB

Quote:

Originally Posted by daljitsb

For that we are planning to use ORM tool and have most business logic in application.

That will solve the issue I've raised.

Now -because of I'm required to do it by law- please note that a full application based business logic has a high potential of being more dificult to maintain and audit. Also, in terms of performance and code reutilization nothing beats backend based business logic.

Quote:

Originally Posted by daljitsb

So which way you suggest - Blobs v/s file system (Bfile)

If you are looking for a solid deployment including the certainty of having consistent backups I'll go with BLOBs in both Oracle and SQL Server -yes! against popular perception SQL Server supports BLOBs with a max size of about 2 Gig per object.