255-char limitation on path name + file name
I am a user on a SharePoint site, my project is being asked to migrate all files from Windows Explorer to SP.
We are not using subfolders because the migration team said there is a limitation of 255 characters for the file path. This restriction seems odd to me because my not so casual observation of web sites is that you can have VERY long URL's. I realize that the back end is Sql Server, so that must account for the 255 char limitation.
For example, here is a path on the site, 263 chars,
http://sharepoint.mycompany.com/operations/ci/t00017999/Requirements/Forms/Subfolder.aspx?RootFolder=%2foperations%2fci%2ft00017166%2fRequirements%2f09%2dPharm%20Mgmt%2fSupporting%20Documentation&FolderCTID=&View=%7b247DBD03%2dDF47%2d46CB%2d863B%2dB0121436F09A%7d
So this file is on the site and it's more than 255 chars? Where does the limitation come into play?
We are not using subfolders because the migration team said there is a limitation of 255 characters for the file path. This restriction seems odd to me because my not so casual observation of web sites is that you can have VERY long URL's. I realize that the back end is Sql Server, so that must account for the 255 char limitation.
For example, here is a path on the site, 263 chars,
http://sharepoint.mycompany.com/operations/ci/t00017999/Requirements/Forms/Subfolder.aspx?RootFolder=%2foperations%2fci%2ft00017166%2fRequirements%2f09%2dPharm%20Mgmt%2fSupporting%20Documentation&FolderCTID=&View=%7b247DBD03%2dDF47%2d46CB%2d863B%2dB0121436F09A%7d
So this file is on the site and it's more than 255 chars? Where does the limitation come into play?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Chris, ok, that makes sense, thanks.
Roos - thank you for the links, I will review shortly.
Roos - thank you for the links, I will review shortly.
The links are more to support the statement that the actuall path should not be longer then 255 chars.
Bassically I found the last article most interessting as it mentioning that the restriction to path <255 chars.
Just keeps us informed.
If you need further assitance then let us know.
Bassically I found the last article most interessting as it mentioning that the restriction to path <255 chars.
Just keeps us informed.
If you need further assitance then let us know.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Roos, I looked at the articles, the 2nd one (as you said) was right on. I'm not a Web person, but it just doesn't make sense to me that there is a limit, since on the Web URL's can be VERY long. Perhaps it is a Sql * Server limitation.
baev and others, recently (in my SharePoint migration effort), I could not open a file in normal Windows Explorer since the path was too long. Ok, that's understandable.
Now, hope I can explain this clearly.
In Windows Explorer, I created a link to the SharePoint site, this is in "My Network Places". This is exactly like Windows Explorer for navigating, even though the files are on the Web (just like if you had a FTP tool and where ftp'ing to a web area - it just looks like Windows Explorer).
Anyway, when you hover on the "Internet address", the file name in the little pop-up is
http://sharepoint.company.com/operations/ci/t000174444/Requirements/My File Name.doc
However, on SharePoint, the URL is
http://sharepoint.carefirst.com/operations/ci/t000174444/Requirements/My%20File%20Name.doc
the only difference being the spaces.
So obviously there is a limitation.
We were told not to use subfolders and I just thought that was weird since subfolders are visual and logical. What we have to do is "categorize things" (to four levels), and this is problematic since you can only group things to two levels.
Anyway, I guess I'll have to live with it, thanks for the feedback.
Bill
baev and others, recently (in my SharePoint migration effort), I could not open a file in normal Windows Explorer since the path was too long. Ok, that's understandable.
Now, hope I can explain this clearly.
In Windows Explorer, I created a link to the SharePoint site, this is in "My Network Places". This is exactly like Windows Explorer for navigating, even though the files are on the Web (just like if you had a FTP tool and where ftp'ing to a web area - it just looks like Windows Explorer).
Anyway, when you hover on the "Internet address", the file name in the little pop-up is
http://sharepoint.company.com/operations/ci/t000174444/Requirements/My File Name.doc
However, on SharePoint, the URL is
http://sharepoint.carefirst.com/operations/ci/t000174444/Requirements/My%20File%20Name.doc
the only difference being the spaces.
So obviously there is a limitation.
We were told not to use subfolders and I just thought that was weird since subfolders are visual and logical. What we have to do is "categorize things" (to four levels), and this is problematic since you can only group things to two levels.
Anyway, I guess I'll have to live with it, thanks for the feedback.
Bill
ASKER
A little further research . . .
As I (might have) mentioned, the 255-char limitation is (essentially) the same in Windows Explorer as SharePoint.
Our current project was moving from this path on Windows
S:\Shared\Corporate Shared\Corporate Initiatives\2007 Initiatives\[My Project], which by itself, is 80 characters, 30% of the total !
So folders on WebSphere are the same as Windows Explorer, and my initial consternation (that we couldn't use folders on WebSphere) was justified.
As I (might have) mentioned, the 255-char limitation is (essentially) the same in Windows Explorer as SharePoint.
Our current project was moving from this path on Windows
S:\Shared\Corporate Shared\Corporate Initiatives\2007 Initiatives\[My Project], which by itself, is 80 characters, 30% of the total !
So folders on WebSphere are the same as Windows Explorer, and my initial consternation (that we couldn't use folders on WebSphere) was justified.
Hello Bill,
I don't know the size of the company you work for. I can imagine that though you seems to be a correct user, who is using path and files names which makes sence. Perhaps they made a basic rule for the whole company not to use more folders as others are not that strict on using good names. Which might result in exceeding the 255 char restriction. If that is the case then it seems that you belong to that small % who has to pay for the way of working of others.
to me it seems you have enough information what are the restrictions and to get into a discussion, though would it make sence?
I wish you all the good luck on it. And im curious how it will end. Still you have gathered enough information to talk with them without looking a fool.
with regards,
Jeroen
I don't know the size of the company you work for. I can imagine that though you seems to be a correct user, who is using path and files names which makes sence. Perhaps they made a basic rule for the whole company not to use more folders as others are not that strict on using good names. Which might result in exceeding the 255 char restriction. If that is the case then it seems that you belong to that small % who has to pay for the way of working of others.
to me it seems you have enough information what are the restrictions and to get into a discussion, though would it make sence?
I wish you all the good luck on it. And im curious how it will end. Still you have gathered enough information to talk with them without looking a fool.
with regards,
Jeroen
ASKER
Jeroen, thanks again.
As far as not looking like a fool, I think I am now well-armed regarding this question, but I still might have to get some new clothes, ha ha.
Yes, the company here decided not to use folders, so we have to live with it. The company is a large regional company. We'll see after several months how things go.
And, the real problem is NOT the 255-char limitation. This was used as an excuse to not use folders, but the real reason was to force discipline in file management.
My project is fairly big (6 PM's, 8 or so Business Analysts, etc.) So there are a lot of files, and as I was planning the migration from Windows Explorer to SharePoint, I kept finding mounds upon mounds of junk folders, crazy stuff people were hoarding onto, archive files out the wazoo, etc.
Anyway, I appreciate the discussion, and the links have been very helpful.
As far as not looking like a fool, I think I am now well-armed regarding this question, but I still might have to get some new clothes, ha ha.
Yes, the company here decided not to use folders, so we have to live with it. The company is a large regional company. We'll see after several months how things go.
And, the real problem is NOT the 255-char limitation. This was used as an excuse to not use folders, but the real reason was to force discipline in file management.
My project is fairly big (6 PM's, 8 or so Business Analysts, etc.) So there are a lot of files, and as I was planning the migration from Windows Explorer to SharePoint, I kept finding mounds upon mounds of junk folders, crazy stuff people were hoarding onto, archive files out the wazoo, etc.
Anyway, I appreciate the discussion, and the links have been very helpful.
Good to hear your now well armed, If you need new clothes I can post you some links :)
regarding this question as you might know there is still some final step to make. Perhaps this gives you further support.
https://www.experts-exchange.com/help.jsp#hs5
regards and good luck,
Jeroen
regarding this question as you might know there is still some final step to make. Perhaps this gives you further support.
https://www.experts-exchange.com/help.jsp#hs5
regards and good luck,
Jeroen
ASKER
sorry for the delay in points, but thanks again for the assistance.
The 255 character limitation is actually a database limitation in the SharePoint DB. The link that you provided
http://sharepoint.mycompany.com/operations/ci/t00017999/Requirements/Forms/Subfolder.aspx?RootFolder=/operations/ci/t00017166/Requirements/09-Pharm_Mgmt/Supporting Documentation&FolderCTID=&
does not have anything to do with the 255 character limit and is way under the limit. The limit is strictly on the folder path length and nothing else, now certain apps may have issues opening extremely long URL paths, but you dont want to be counting GUIDs, URL encoding, and other items in the URLs as going towards the length limitation.
Example: http://sharepoint.mycompany.com/operations/shared_documents/sub_folder_1/sub_folder_2/sub_folder_3/sub_folder_4/sub_folder_5/sub_folder_6 (that is what it looks like in the SharePoint DB) is only 137 characters long towards the 255 limitation. If you would look at the URL for sub_folder_6 that would show up in your browser it would look very long and be way over the 255 and this is were the confusion sets in for most users.
My recommendation to my users is to keep folder names short (ie no full sentences as folder names) and you shouldnt really have a problem.
http://sharepoint.mycompany.com/operations/ci/t00017999/Requirements/Forms/Subfolder.aspx?RootFolder=/operations/ci/t00017166/Requirements/09-Pharm_Mgmt/Supporting Documentation&FolderCTID=&
does not have anything to do with the 255 character limit and is way under the limit. The limit is strictly on the folder path length and nothing else, now certain apps may have issues opening extremely long URL paths, but you dont want to be counting GUIDs, URL encoding, and other items in the URLs as going towards the length limitation.
Example: http://sharepoint.mycompany.com/operations/shared_documents/sub_folder_1/sub_folder_2/sub_folder_3/sub_folder_4/sub_folder_5/sub_folder_6 (that is what it looks like in the SharePoint DB) is only 137 characters long towards the 255 limitation. If you would look at the URL for sub_folder_6 that would show up in your browser it would look very long and be way over the 255 and this is were the confusion sets in for most users.
My recommendation to my users is to keep folder names short (ie no full sentences as folder names) and you shouldnt really have a problem.
ASKER
Ok, sounds good. Thanks for the info, helps in understanding the issue.
What got you to this question?
What got you to this question?
Chris