This project is read-only.

Any plan for Filestream support? or audit table access

Oct 29, 2009 at 3:58 AM

Just wondered if there was any plan for filestream support in the datamodel??

Also is there any plan to be able to access previous version information through the model?

Oct 29, 2009 at 1:24 PM

What exactly do you mean by filestream support? Please give me an example. Also how would you use previous version information? Please give me an example or some uses and we will discus it.

Oct 29, 2009 at 3:05 PM

The filestream support is a fairly new feature in mssql introduced in mssql 2008 I think..  It basically allows you to store binary data outside the database but it is still associated with the database.  This keeps the DB itsself from getting big fast when storing a lot of binary data such as PDFs or Word Docs.  I think it is a pretty cool feature and it also allows you to use the full text indexing on documents such as PDF, word, or any type of document that has a search filter for installed on the server.  In summary, a separate filegroup needs to be defined and then that filegroup is used for any column that you wish to use file streaming with.  The column must also be of type varbinary(MAX) and I think you can write to it as  you would any other blob...  Here is a link to MSDN docs    

As for the previous version information, I was thinking that when auditing is enabled if there were some rudimentary query functions that would allow you to get previous versions of the row by primary key.  This functionality might also be achieved by simply importing the audit table into the model after installing it on the database, but I have had trouble adding the generated audit table to the model, I don't know if there is an inherent incompatibility with the audit table, or it is just due to this issue: that I posted last night.

Let me know if you need any more info,



Oct 30, 2009 at 2:34 AM

I have transferred the suggestion to our roadmap blog

Oct 30, 2009 at 6:47 PM

Sounds good.  Could a custom stored procedure be used until it is natively supported??  Do the custom stored procedures run after the generated ones run?