Implement FILESTREAM for blobs into Azure Blob Store
Storing blobs in the database is fairly pointless when you have a dedicated blob store. Implement the FILESTREAM protocol to store blobs in a user's azure storage
Create a table in sql azure that maps to Azure blob storage. That way we can virtually query against blob storage and have foreign keys to blobs. Ex: table of Assets and blob storage table of Asset Photo with a foreign key between the two.
This would reduce costs for those who store files inside their sql server 2008 databases when migrating from on-premise scenarios.
While we understand the scenario here and would love to enable, this isn’t something that’s on the road map as of now, We will share more when we have an update,
I recently upgraded a project to store files in an SQL2014 FileTable, instead of storing the files separately and then just referencing in the database. This has allowed for some significant improvements in site management. It's just unfortunate that at the moment this prevents me from easily moving the site from a dedicated VM to an Azure Web Service. FileTable's and FileStream's are a fantastic feature. I really hope that these will eventually be supported natively by Azure SQL.
Michael LeValle commented
Any movement on this?
Love to see that!
Not because of retrieval speed (varbinaty vs filestream) but because then a retrieval of an object via entity framework, which typically retrieves all fields, would not retrieve the FILESTREAM data and so save a lot of time and bandwidth.
Put my vote on the list for that too.
In Azure, filestream doesn't make sense, but a BLOB data type using BLOB storage would be great.
Does Microsoft already have a position about this in 2015?
a great think about storing files with filestream is to use the same database transaction all over the code and don't care if something goes wrong, because you can just rollback.
Brian McKinley commented
This should include the ability associate a storage account with database, federation or federation "member." If a database, federation or federation member is dropped the associated blobs referenced in the tables should be deleted automatically from the blob storage. When a federation is split we should have the option to specify a new storage devices for the new federation member at the same time.
Daniel Kornev commented
Totally agree; enabling FileTables as part of SQL Azure would also enable full-text search and semantic search scenarios.
Ryan CrawCour commented
Why would you want to store blobs in SQL Azure when storing blobs in Windows Azure Blob storage is orders of magnitude cheaper. Store your relational data in SQL Azure and your blobs in a storage abstract designed for this exact purpose.
Why use a separate API for Azure storage when we can use ADO.Net and get at SQL AND file data?