Hi, not sure if the question is directed to the correct forum, plase let me know if not.
Hello I was hoping that someone can clarify the SQL Server FILESTREAM usage in N-TIER architecture.
I have concern on performance with N-Tier architecture. I am considering refactoring an application with the following physical tiers (Rich Client -> Web Service - >
Database), currently all the files a stored on the web service tier.
If clients need to download files (2 MB – 50 MB), the files will need first to be transfer from the DB server tier to the Web Service tier and then transfer from the Web
Service tier to the client tier.
It’s seem a lot of network overhead using FILESTREAM compare to local file stored on the web service tier local disk, do you have any performance experience on the real
impact in the above scenario using FILESTREAM .
Any opinion would be much appreciated.