April 24, 2010 at 8:08 am
We just installed our Sharepoint MOSS 2007 and the databases Content have already reached 25 GIG. It seems to me that the content data i.e pdf and word etc are being stored in the Database.
I have researched the following thread
http://technet.microsoft.com/en-us/magazine/2009.06.insidesharepoint.aspx
Is the content word/pdf only going to be stored on another storage device if you buy a third party piece of software to use the API .
Any information would be appreciated.
April 26, 2010 at 7:39 am
TRACEY-320982 (4/24/2010)
We just installed our Sharepoint MOSS 2007 and the databases Content have already reached 25 GIG. It seems to me that the content data i.e pdf and word etc are being stored in the Database.I have researched the following thread
http://technet.microsoft.com/en-us/magazine/2009.06.insidesharepoint.aspx
Is the content word/pdf only going to be stored on another storage device if you buy a third party piece of software to use the API .
Any information would be appreciated.
I'm not aware of what a 3rd party solution might offer, but SharePoint 2007 stores everything in the database. If you want the ability to store files, seperate from the database, you need to look at SharePoint 2010, which comes out in the next few weeks I beleive. It has the ability to take advantage of the FileStream object within SQL Server 2008 & R2.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 27, 2010 at 1:03 pm
This is the way SharePoint is designed. You're going to have to plan for continued growth of that content databases. Depending on the size of your organization you and/or your SharePoint admins may have to plan for having multiple content databases and mapping different web apps and site collections to the various content databases to keep any single content DB from growing too large, which can impact performance.
Deploying SharePoint has the side effect of taking some files (sometimes a lot) out of file shares and putting them into a SQL Server database. We've also experienced substancial growth in the size of our content database though we did expect as much. We left it completely up to our folks to use SharePoint or not and we're seeing more and more make the choice to host their project files in SharePoint instead of on file shares.
April 28, 2010 at 7:15 am
Please check whether its .ldf or .mdf file thats growing ...
Tat might be ldf and u can shrink that...
April 28, 2010 at 7:17 am
I agree with Grant - you might want to look at 2010.
You should be able to download a trial of Sharepoint 2010 to test with, and if you have software assurance, the upgrade is free.
They've also started various launch events for the whole 2010 release - which includes much more than Sharepoint.
Also take a look at what filestream means for backups.
Greg E
April 28, 2010 at 6:09 pm
Thanks - I thought you could do it in the MOSS 2007 version too..but it appears from the replies it just the 2010 Sharepoint version.
April 29, 2010 at 5:55 am
TRACEY-320982 (4/28/2010)
Thanks - I thought you could do it in the MOSS 2007 version too..but it appears from the replies it just the 2010 Sharepoint version.
Yep. Just 2010. Kind of stinks, but there it is.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 29, 2010 at 9:27 am
From what I'm hearing, that would mean that requests travel as follows, whether it's 2007 or 2010 using blobs or 2010 using Filestream:
Client sends a request to Sharepoint Server.
Sharepoint Server sends a request to Sharepoint DB
IF Filestream, Sharepoint DB sends a request to file system
IF Filestream, file system sends a file to Sharepoint DB
Sharepoint DB sends a file to Sharepoint Server
Sharepoint Server sends the file to the client.
Which means that the Sharepoint Server <-> Sharepoint DB link is going to have to handle not only request traffic, but also all file traffic too.
Am I missing something? None of the other document or report management systems I've worked with did this; they stored a file location in the database, and the database passed that file location to the server.
May 2, 2010 at 11:39 am
Thanks I will recommend upgrade to 2010 as soon as it out rather than in 5 years 🙂
May 3, 2010 at 6:43 am
TRACEY-320982 (5/2/2010)
Thanks I will recommend upgrade to 2010 as soon as it out rather than in 5 years 🙂
I'd recommend taking a closer look at 2010 before recommending an upgrade.
You could find some other features that you'd want to implement that would work best with other programs being upgraded.
There were a number of programs, like Office, that also were being developed at the same time.
For example, Excel Power Pivot - would you be upgrading all the clients to Office 2010? Would you need another server?
As mentioned by one of the earlier posts, multiple content db's can be done with 2007 version.
Greg E
May 3, 2010 at 7:30 am
Greg Edwards-268690 (5/3/2010)
TRACEY-320982 (5/2/2010)
Thanks I will recommend upgrade to 2010 as soon as it out rather than in 5 years 🙂I'd recommend taking a closer look at 2010 before recommending an upgrade.
You could find some other features that you'd want to implement that would work best with other programs being upgraded.
There were a number of programs, like Office, that also were being developed at the same time.
For example, Excel Power Pivot - would you be upgrading all the clients to Office 2010? Would you need another server?
As mentioned by one of the earlier posts, multiple content db's can be done with 2007 version.
Greg E
Yeah, I agree. From everything I've read, 2010 is shaping up to be a prettty major upgrade for Sharepoint. I know our Sharepoint developers are slathering at the mouth over all the new capabilities.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 3, 2010 at 5:55 pm
Thank multiple content databases. Will look into this.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply