Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Sharepoint databases? Expand / Collapse
Author
Message
Posted Thursday, March 19, 2009 9:23 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, January 04, 2012 9:40 AM
Points: 54, Visits: 132
can you tell me if you deal with administrating sharepoint databses and give some tips on.
Our sharepoint have been semi-live but we will go live by the end of this month nad i wnat to be prepared as much as I can for maintenance plans. Currently we have 3 full backups done during the night (local, share, evault) and 1 nightly transaction log backup (which I am trying to convince manager to increase frequency to at least 4 times daily) :

1- If you do any maintenance scheduled reboots for your SQL cluster enviornments (as this sharepoint environment is always live)

2- if your tempdb is big and if you don't do scheduled reboots or SQL service retarts,
how do you advise on the size of temp db in this environment?

3- what are the pros and cons of the databases that are set in simple recovery yet are very important to the business, like search databases? how do you deal with them?

4- most important how often do you backup your transaction logs on these databases?

5- Is there any of the following key databases that would have more tranaction once we go full live or require more looking after (e.g. teranaction log manual backup?)
Config_db
adminContent
SSP Databases
SSP search
Content


ANY advice or precaution would be greatly appreciated.

Ellie
Post #679548
Posted Thursday, March 19, 2009 10:11 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, March 16, 2011 3:56 PM
Points: 8, Visits: 89
1- If you do any maintenance scheduled reboots for your SQL cluster enviornments (as this sharepoint environment is always live)

We do reboot our cluster environments one server at the time. Just wait for the rebooted server to fully come backup (without any errors) and then reboot the other server.

2- if your tempdb is big and if you don't do scheduled reboots or SQL service retarts,
how do you advise on the size of temp db in this environment?
Partition your tempdb based on the number of CPUs. So, if you have 4 CPUs create 4 data files for your temp db.

3- what are the pros and cons of the databases that are set in simple recovery yet are very important to the business, like search databases? how do you deal with them?
All of our sharepoint databases were put back to the full recovery mode for us to be able to take transactional logs.

4- most important how often do you backup your transaction logs on these databases?
On the sharepoint farm we create transaction logs every 20 minutes (we just have a requirement for the recovery purposes)

5- Is there any of the following key databases that would have more tranaction once we go full live or require more looking after (e.g. teranaction log manual backup?)
Config_db
adminContent
SSP Databases
SSP search
Content

Config_db shouldn't grow. Your Content database will grow depending on the use of the Sharepoint.
Post #679609
Posted Thursday, March 19, 2009 10:12 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:29 AM
Points: 3,420, Visits: 14,239
I don't do Sharepoint but start with these two links which will help you to understand what you need to maintain Sharepoint database.

http://blogs.technet.com/wbaer/archive/2008/02/27/just-published-whitepaper-database-maintenance-for-microsoft-sharepoint-products-and-technologies.aspx

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



Kind regards,
Gift Peddie
Post #679611
Posted Thursday, March 19, 2009 10:19 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 5:20 PM
Points: 32,249, Visits: 24,735
Make sure you read this one too. http://www.sqlskills.com/BLOGS/KIMBERLY/post/Database-Maintenance-Best-Practices-Part-I-e28093-clarifying-ambiguous-recommendations-for-Sharepoint.aspx


Gail Shaw
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #679625
Posted Thursday, March 19, 2009 11:26 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, January 04, 2012 9:40 AM
Points: 54, Visits: 132
Tony,
thanks for all the information. how often do you reboot your clusters? Does that help the tempdb (s) size?
Also, do you do Re-index for the databases and if so can you tell me which of the aforementioned databases would be more in need of re-index maintenance schedule plan?


again thnak you for all the information
Post #679702
Posted Thursday, March 19, 2009 11:38 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, November 17, 2009 5:33 PM
Points: 81, Visits: 299
I cannot give point to point answer with my expertise. But here are few i know

Create a scheduled task using task scheduler and take backup of your sites and whole sharepoint as needed. In the next step, keep moving them to another server regulary. You can use central administration to take this backup or create a batch file. This will take the backup of Database as well.

Doing this on regular basis will help your site rather than database backups (i feel).
Post #679716
Posted Thursday, March 19, 2009 11:47 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, March 16, 2011 3:56 PM
Points: 8, Visits: 89
Hi,

We have to reboot all of our sql servers once a month. It does help with tempdb size but give it more space initially.
I have a script that gives us a repot for all indexes on all databases. Any index with over 20% of logical defragmentation we should be rebuilding but it is had to get an approval time for that since we run that job for all databases on that cluster (one db at the time).

T.
Post #679727
Posted Thursday, March 19, 2009 11:47 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, January 04, 2012 9:40 AM
Points: 54, Visits: 132
Gila,
thank you so much for the article. I already have update statistics and create updates, I just added DBCC in maintenance plan wizard set to run for Sunday morning in the developement database, I will see how it goes on and how long it will take for my 50 Gb database, if so , then I will apply it for a few other databases. Then the next step would be to add re-indexing schedule.

Thanks as always.
Ellie
Post #679728
Posted Thursday, March 19, 2009 11:50 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, January 04, 2012 9:40 AM
Points: 54, Visits: 132
Tony (3/19/2009)
Hi,

We have to reboot all of our sql servers once a month. It does help with tempdb size but give it more space initially.
I have a script that gives us a repot for all indexes on all databases. Any index with over 20% of logical defragmentation we should be rebuilding but it is had to get an approval time for that since we run that job for all databases on that cluster (one db at the time).

T.


Thanks Tony. I guess I should convince the SE team to plan for once a month reboot.
Post #679733
Posted Thursday, March 19, 2009 11:53 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, January 04, 2012 9:40 AM
Points: 54, Visits: 132
Sudiendra (3/19/2009)
I cannot give point to point answer with my expertise. But here are few i know

Create a scheduled task using task scheduler and take backup of your sites and whole sharepoint as needed. In the next step, keep moving them to another server regulary. You can use central administration to take this backup or create a batch file. This will take the backup of Database as well.

Doing this on regular basis will help your site rather than database backups (i feel).



Sudiendra,
thank you for the input.
We Do have an evault backup of site that is an online and takes care of backing up the whole sites and server as well as SQL backups along with my usual SQL backups. Does that help? Meaning, would that assurance help me to better sleep at night:)
Post #679740
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse