May 12, 2014 at 9:17 pm
Comments posted to this topic are about the item Filetable paths
May 13, 2014 at 12:05 am
Thanks for the question, made me do some research.
Has anyone used file tables in production yet?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 13, 2014 at 12:31 am
Koen Verbeeck (5/13/2014)
Thanks for the question, made me do some research.Has anyone used file tables in production yet?
Not me 😎
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
May 13, 2014 at 2:13 am
New to me as well.
May 13, 2014 at 2:27 am
This was removed by the editor as SPAM
May 13, 2014 at 2:32 am
Stewart "Arturius" Campbell (5/13/2014)
Koen Verbeeck (5/13/2014)
Thanks for the question, made me do some research.Has anyone used file tables in production yet?
I replaced the old IBM Doc Store application using FileTable.
About 200 times more efficient, no timeouts, less space consumed, much better all round.
Great, good to know 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 13, 2014 at 3:57 am
Thank you for the post, ST, very very interesting one.
(As I am using this feature for the first time, I just created a FT and was looking in to the detailed information using sp_help, there are several constraints and the associated constraint_key under it has very non-easy understandable rules)
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
May 13, 2014 at 5:55 am
Interesting question. I've never used them.
May 13, 2014 at 6:18 am
This is kind of a trick question. The actual path is not stored in the schema at all. Rather the filetable path_locator is of data hierarchyid that identifies the position of this node in the hierarchical FileNamespace.
I'm still not sure how to extract that actual path (i.e. conventional Windows path name)
May 13, 2014 at 6:41 am
This was removed by the editor as SPAM
May 13, 2014 at 7:52 am
I disagree with the answer and believe it should be nvarchar. The documentation at http://technet.microsoft.com/en-us/library/gg492084.aspx shows that the path_locator is hierarchyid, but the name, which is defined as 'The file or directory name. ' is nvarchar. I could use the name to find something, not the hierarchyid.
May 13, 2014 at 8:02 am
Nice question. Had to do the research, as never had a chance to use them. I can see how the could be used. But doubt I'll ever have any need for them where I work.
Thanks Steve!
[font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
Connect to me on LinkedIn
May 13, 2014 at 8:07 am
gbritton1 (5/13/2014)
I'm still not sure how to extract that actual path (i.e. conventional Windows path name)
During my investigation on this question, I came across documentation on the FileTableRootPath function. "It returns the root-level UNC path for a specific FileTable or for the current database".
http://technet.microsoft.com/en-us/library/gg509104.aspx
I don't know if this is what you were specifically referring to. I am new to FileTables and have not used this functionality yet.
Regards,
Brian
EDIT: forgot to add the URL reference.
May 13, 2014 at 8:55 am
I've run into a few people using this, and Filestream. For Filestream it's mostly been .NET programmers that write thick apps and want drag/drop, easy storage of lots of images.
For Filetables, I've met a few early adopters that used it for Dfs replacements, moving files around on shares and syncing them with AlwaysOn.
May 13, 2014 at 9:12 am
With a little help from BoL... Thanks, Steve!
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply