Question Locked

sharepoint documents

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Weve had a sharepoint 3.0 install on a "testzone" for a few months now.
One thing that i cant work out is how to store data onto another drive.

The C drive of the server is very small therefore it is getting full when users are adding documents.
Is there anyway of storing this data to another drive on the same server? We have an E drive that has plenty of space.

Someone else must have experienced this problem

Thanks

9 replies

by darryl~

Why not just ghost it to a larger drive and replace your c drive with the larger drive?

by danny_teal

we dont want to spend any money on it. there must be a way of passing it over to another drive..?

by darryl~

It looks like it should do what you want.
Have a look at this link.

http://technet.microsoft.com/en-us/library/dd277864.aspx

Below is the series of suggestions for a similar problem by another SharePoint Admin.

The first comment is not so relevant to you but the other comments seem to explain how to move the data files to another drive.

It's worth looking into also

*****************************************
Have you check all of the database files are in E drive? Since there are configuraton, index and content databases of WSS 3. Perhaps the content database is on C drive?

*******************************************
You should be able to move the data file to another drive as long as it handles by SQL server since WSS only talk to SQL server, and then SQL Server retrieve data from databases
*****************************************
I would agree with cobrachen -- I would also search for log files (specifically IIS and SharePoint ones) those puppies can take up alot of space if you do not have a process to clean them up. I know by default that IIS will put it's log files on the C: under the Windows folder.
****************************************
Liebrand is correct. By default the IIS logfiles and the SharePoint logfiles both reside on the c: drive.

In order to move the SharePoint logfiles, you need to go to:

Central Administration > Operations > Diagnostic Logging

and change the path of the log files from there.

In order to move the IIS log files, you need to go to the properties of the web site in IIS and on the web site tab go to properties under enable logging and enter a different path where it says log file directory.

by darryl~

I took an interest in this because I'm going to be required to do the same thing in a few months time....but mine will be to move it to a new server...basically the same thing though.
**************************************
WSS 3.0 uses Microsoft SQL Embedded Edition (MSEE) for its data store. When MSEE is installed, the data files are installed to your C: drive by default. Since you do not want to have a file on your system drive that can grow exponentially, you need to move it to another drive. Here is how you do it.

Note: While completing this process your WSS site will be offline to your users.

Shutdown all Windows Sharepoint services & IIS Admin service: This will ensure that there are no locks on the files you need to move.
Open a cmd prompt and cd to C:\Program Files\Microsoft SQL Server\90\Tools\binn
Enter sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E: This starts the Microsoft SQL Server 2005 Command Line Query Utility
Enter the following commands to view the available databases & hit Enter after each:
SELECT name from sysdatabases
GO
You should see a number of DBs, move the following 4 databases (GUID?s may be different):

SharePoint_Config_c464b7ce-59ef-4820-9f75-f46a0937c08e
SharePoint_AdminContent_451452bf-9dc0-40c9-be18-14f14bc23007
WSS_Search_NETSERVER_86a140c5958d4a5d97c8c2cbee745424
WSS_Content
Enter the following commands & hit Enter after each line. Repeat for each database.
EXEC sp_detach_db @dbname = ?Content_Database_name?

GO
Move the databases to their new location. They can be found in C:\Windows\SSQL\Data\.mdf and _log.ldf
After the files have been moved run the following commands (Make sure to change the itialic sections to your specifics):
EXEC sp_attach_db @dbname = ?Content_Database_name?, @filename1 = ?drive:\path\Data\.mdf?, @filename2 = ?drive:\path\Data \_log.ldf?
Go
Repeat step 7 for each database you moved.
Restart IIS Admin services and all Windows Sharepoint services
Ensure your Sharepoint site is working
If this is done before you build your site it will take no time at all to move the DBs to the new location.

by danny_teal

seem just what i need. i had actually found the first article after i posted this question.
im going to give it a go on monday.
microsoft never make anything simple do they...!
thanks again

by danny_teal

did this on our test environment and it worked a treat!
weve got a new production server so i thought id try it again. followed the documents but once i turn the sharepoint on i get "Cannot connect to the configuration database."
Can anyone advise? ive been banging my head against this for days now..

by scorpaenopsis

Hi Danny,

i dit a testinstallation of the new SQL Express version (http://www.microsoft.com/express/sql/register/) some month ago. This version let you choose where to store the Databases.

I would try it in this way:
- export all content via stadm command
- create a new WSS server using the new SQL Lite
- if possible separate (to different partitions) log files, temp.db, dbfiles <-- here i'm not 100 shure whats possible with SQL express.
- import via stadm

here are some usefull links:
http://tinyurl.com/6hp8dh
http://tinyurl.com/lf64kx

This discussion is closed to new replies.