Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Loading

MOSS Content Database Conciderations

Some random thoughts:

When attaching a content database to Sharepoint the SQL Log file can be the same to twice the size of the current data size. the reason for this is that sharepoint takes an internal backup of the data verifies it (as well as some other magic) then attaches it to sharepoint, once attached the backup is removed (you may need to shrink the log)

Suggest using command prompt to attach rather than UI. run “stsadm.exe -o addcontentdb -url http://yourwebapp  -databasename WSS_Content_yourwebapp

To attach a content DB of 100GB can take between 30 – 1h 30m depending on the hardware (for a resent attach I performed it took 1h 30min) and can consume between 60G – 200Gb worth of Tlog (for a resent attach I performed it consumed 79GB)

Note: Tlog will still grow in simple mode

Suggest keeping content databases to 50Gb (100Mb being the Microsoft maximun recommendation)

Leave a Reply

Your email address will not be published. Required fields are marked *