Save file pointers to database

[haripandian]

Hi,

My application requires saving of images (5 per trial) which is to be used for processing in later stages. I am storing trial data in database using LabVIEW database connectivity toolkit. I would also want to save images with the database for easy data management. But I do not want to save the entire image as it makes my db bulky and slow overtime. I would rather create a file reference/pointer to the image in database. Any ideas on how to create a file reference in database.

[Artem.SPb]

Save filepath as string

[crossrulz]

The simplest solution is to just store the path as a string in the database.  This requires you to follow some guidelines on where your files will go out on the server, preferably with the database.

Another solution, if using SQL, is the FileStream.  It allows the SQL database to keep the files in its own way (folder location stored with the database).  So the files are not exactly in the database and you can access the files quite quickly.  This does require using some .NET nodes and a little setting up with the database.

[mikeporter]

So what you are saying is that the pictures aren't very important and it's OK to have them be lost?

If they are not in the database they *will* get lost. It's not a matter of if it will happen. It's a matter of when.

Better to use a DB server that can store all your data -- and by the way, images don't have to be large thanks to data compression. Likewise, any database will slow down over time if it is not maintained.

[haripandian]

I would want to explore the SQL Filestream method as it would be reliable for my case. I have some idea with Filestream but how to use .NET nodes is something I haven't explored. Where do I start???

[haripandian]

Mike Porter, I will require the images for further processing , so I should not lose them. With regards to data compression, there may be some data loss which may affect my processing in future. How to configure a db server. Can you brief this method.

[Yamaeda]

---

@mikeporter wrote:
So what you are saying is that the pictures aren't very important and it's OK to have them be lost?

If they are not in the database they *will* get lost. It's not a matter of if it will happen. It's a matter of when.

Better to use a DB server that can store all your data -- and by the way, images don't have to be large thanks to data compression. Likewise, any database will slow down over time if it is not maintained.

---

If they are saved as files on the database server it's about as likely they are deleted as other data.

/Y

[mikeporter]

Y: true, but if they are in the database you can at least setup permissions that would make it more difficult.

haripandian: with compression it depends on the type you use.

Mike...