Click here to Skip to main content
15,889,862 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I'm thinking in design a form as prescription, feed it with the data, then capture it and print, and save captured image in the database as image.
But i'm afraid of database growth when i save every prescription as image in it(after years) database reach a size limit,
Is that right to save the prescriptions by this way? or there is a better way to save the prescription to retrieve and print it at any time.

What I have tried:

Is that better to save the prescription content as seperated strings in one cell(separated by any sign like ($$)), when user try to retrieve a prescription the program seperate the cell content (make every $$ a new line) and draw them to the form to print?
Posted
Updated 16-Feb-17 5:34am
v3
Comments
[no name] 16-Feb-17 9:16am    
"Is that right to save the prescriptions by this way", last I heard, best practice was to save files to the file system and a path to the file in the database.

1 solution

SQL Server has a theoretical maximum database size of 524272TB.
Maximum Capacity Specifications for SQL Server[^]

Obviously, a database cannot be larger than your available storage capacity, which will almost certainly be several orders of magnitude lower.

If you're using the Express edition, each database is further limited to 10GB of data. (This does not include FILESTREAM[^] data or log files.)

As mentioned in the comments, the best approach remains to store files in the file system. But if the output is simple enough to recreate, storing the raw data needed to recreate it in the database would also work.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900