Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
eashoori
Starting Member
22 Posts |
 Posted - 2009-03-19 : 12:01:41
|
| can you tell me if you deal with administrating sharepoint databases 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_dbadminContentSSP DatabasesSSP searchContentANY advice or precaution would be greatly appreciated.Ellie |
|
|
dewacorp.alliances
452 Posts |
Posted - 2009-03-20 : 00:52:25
|
quote:
Originally posted by eashoori
can you tell me if you deal with administrating sharepoint databases 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_dbadminContentSSP DatabasesSSP searchContent
My comment is:1) We generally don't do any reboot stuff for SQL unless updating patch which what we've done is that updte the nonactive node and then sets as the active node if it's ok update the first node.2) You will notice that after period of time the size of the tempdb is alway the same. So just keep that size.3) Search Database I believe this where indexing sit within sharepoint. The indexing I believe ideally sets as every frequent. I don't think you need the roll back if something goes wrong on this database cause it always get created.4) Generally, we backup the ones for major ones with every 1 hour. Depending how's the critical this database is.5) The content one I guess you need TLog for it and the rest is just configuration database. |
 |
|
|
|
|
|
Sharepoint Databases Maintenace?