locked
SharePoint using C:\ drive for data RRS feed

  • Question

  • Hello everyone,

    As an introduction, basically the requirements are, 

    • The Database can accommodate over 4GB worth of content
    • All the content is to be stored on D:\ drive and not the C:\ drive

    More points,

    • I have configured SharePoint Foundation 2010 to work with MSSQL Server to elminate the 4GB database limit.
    • The SQL Server has been installed to D:\ Drive.
    • Going through MSSQL Management Studio I can go through each database individually and confirm their storage location is on D:\ drive.
    • I have to import 100GB worth of documents into a document library in the site.
    • D:\ Drive has 1TB of storage left, and C:\ Drive has 10GB of storage remaining.

    So here are the issues,

    When I attempt to copy (via explorer view) the 100GB worth of files into a Document Library on the site, I get an error saying there is not enough disk space to complete this operation.

    If it helps, when I map a drive (ie., W:\) to the document library, the icon in My Computer shows the same storage information as C:\ drive and not D:\ drive (which is where the database is located)

    I noticed that if I do a copy, the files are individually copied to the Tfs_dav folder, filling C:\.

    Is anyone able to explain the mechanics or design behind this?

    I am having a great deal of difficulty trying to find a solution to this and/or understanding. I have been working on this for well over a week!

    Thanks in advance for your time and help guys.


    Patrick Huerto


    • Edited by patrick.huerto Friday, May 4, 2012 2:44 AM Details of issues
    Friday, May 4, 2012 2:41 AM

Answers

  • Are you doing your copies from the server into SharePoint? Or from a workstation to SharePoint?

    Windows Explorer uses WinDav for the transfers. This discussion provides some background on WinDav and the Tfs_DAV folder:

    http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/threads?page=2

    It looks like if you are copying using Windows Explorer from the server to SharePoint then the files are first copied to the Tfs_DAV folder and then uploaded.

    Do you have the same issues when you are using SharePoint's multiple file upload feature?


    Mike Smith TechTrainingNotes.blogspot.com

    Monday, May 7, 2012 9:48 PM

All replies

  • Just one suggestion here that you can check the properties in the Sql server services and find out the location(path of the executable) being used there.

    Thanks


    Pandey

    Friday, May 4, 2012 10:55 AM
  • Patrick...

    I agree with Pandey here... Can you go into SQL and verify where the db's and master are located?   use this link to help with the details in SQL.   SharePoint isn't storing that content on a local drive but in the DB like you thought.   There's also a memory swap issue when there is a system SQL db left on the drive with not enought space.   Make sure you move backups and and trans logs form the old location to the new location as well.

    http://support.microsoft.com/kb/224071 

    Thanks

    Kris


    Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

    Friday, May 4, 2012 2:26 PM
    Moderator
  • Are you doing your copies from the server into SharePoint? Or from a workstation to SharePoint?

    Windows Explorer uses WinDav for the transfers. This discussion provides some background on WinDav and the Tfs_DAV folder:

    http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/threads?page=2

    It looks like if you are copying using Windows Explorer from the server to SharePoint then the files are first copied to the Tfs_DAV folder and then uploaded.

    Do you have the same issues when you are using SharePoint's multiple file upload feature?


    Mike Smith TechTrainingNotes.blogspot.com

    Monday, May 7, 2012 9:48 PM
  • Hi Guys

    Thanks for the replies! Sorry it has taken me this long to respond, was a long weekend (Labour Day, QLD).

    Anyway, I managed to start getting the files to upload without filling the Tfs_DAV folder (in C:\WINDOWS\%restofpath%) by using http://www.orbitone.com/EN/CODEPLEX/Pages/SharePoint-2010-Bulk-Document-Importer.aspx. This tool is great! However, there were some files that did fail, (file size issues) but this is another issue in itself and I will have to check the log when it has finished the import.

    As Mike said, copying through Windows explorer was filling the Tfs_DAV folder, which includes copies made through the command prompt to a drive mapped to the document library (eg, Y:\).

    I never tried the multiple file uploading feature as there are thousand's of files and was unsure of how copy errors were handled.

    Thanks again to everyone!!


    Patrick Huerto

    Monday, May 7, 2012 11:57 PM