varbinary - Consequences to saving document/pdf as binary in SQL? Alternatives?
-
Is there a better way (xml) that would prove to be better? Space is not an issue; however, length of time to display is, as always, a major factor. I would save as a file and link to the file, but I fear that in the manner suggested they will not map the network drive to a consistent letter at all workstations. What have you done or would you do?
-
Is there a better way (xml) that would prove to be better? Space is not an issue; however, length of time to display is, as always, a major factor. I would save as a file and link to the file, but I fear that in the manner suggested they will not map the network drive to a consistent letter at all workstations. What have you done or would you do?
PrissySC wrote:
however, length of time to display is, as always, a major factor
..then fetch it once, and put it in the users' temp directory.
PrissySC wrote:
I would save as a file and link to the file, but I fear that in the manner suggested they will not map the network drive to a consistent letter at all workstations.
As a user, I can see everything in that path? Could I delete everything? I can try of course, since you probably have a backup :thumbsup:
PrissySC wrote:
What have you done or would you do?
I'd go for the database-solution, but I'd be putting the files in their own database on the server. That way it could have it's own backup-policy. If the users are only "reading" files then a webserver might be preferable; IIS has nice caching options, and getting the files would be easy.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
Is there a better way (xml) that would prove to be better? Space is not an issue; however, length of time to display is, as always, a major factor. I would save as a file and link to the file, but I fear that in the manner suggested they will not map the network drive to a consistent letter at all workstations. What have you done or would you do?
If you're using MS SQL 2012, you might want to look at FileTables[^]. For 2008 / 2008 R2, FileStream[^] might help.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Is there a better way (xml) that would prove to be better? Space is not an issue; however, length of time to display is, as always, a major factor. I would save as a file and link to the file, but I fear that in the manner suggested they will not map the network drive to a consistent letter at all workstations. What have you done or would you do?
PrissySC wrote:
Is there a better way (xml) that would prove to be better? Space is not an issue; however, length of time to display is, as always, a major factor.
That of course depends on how the user is accessing it.
PrissySC wrote:
I would save as a file and link to the file, but I fear that in the manner suggested they will not map the network drive to a consistent letter at all workstations.
Again this depends on how the users access it.
PrissySC wrote:
What have you done or would you do?
Depends on the system but at least one file based solution is to provide an application\web server which can return a file URL and where the server permissions allow only for read only access into the file system. The database then returns something that can be massaged into a file url. There are other solutions and other factors such as how many files, what sort of access, how often does access occur, size of files, goals of project, etc.
