Home/ Questions/Q 6331417
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T18:03:55+00:00

I’m using MVC 3 and SQL Server 2008 R2. I’m building a File Management

  • 0

I’m using MVC 3 and SQL Server 2008 R2.

I’m building a File Management tool for my client, so they can store images and pdfs, and then insert them onto pages.

I’ve been looking into FILESTREAM in SQL Server, and it looks great. It allows me to store the files, as well as keep a backup of them in case something goes wrong.

But I also want the files stored physically somewhere, so that my client can send a link to someone, like: http://www.mysite.com/files/mydoc.pdf

What’s the best practice here? Is it safe and/or smart to use both?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If serving up the files via URL is your only reason for storing on the server too, I’d say that you don’t want to do this.

    In MVC it’s trivial to create a controller action that handles that URL, looks up the file in the DB and returns it to the user. The filename is simply an action parameter in this case, your action logic takes that parameter retrieves the file from the database and return it with a FileStreamResult

    return File(fileStream, contentType, fileName);

    Here’s some more info. About half way down the page shows an example of using FileStreamResult

    http://www.mikesdotnetting.com/Article/125/ASP.NET-MVC-Uploading-and-Downloading-Files

    • 0