Microsoft Details SharePoint-SQL 2008 Integration

Microsoft really wants SharePoint users to upgrade to SQL Server 2008, which was released to manufacturing  Aug. 6. Tuesday, the company's SharePoint hosting and development blog pointed out that IT admins don't have to wait for the documentation to do so.

IT administrators typically look for Microsoft's "supportability statement" document before performing system upgrades. The document for Microsoft Office SharePoint Server (MOSS) 2007 is currently available, and it includes information about upgrading to SQL Server 2008 that was published on July 31.

The document describes MOSS 2007 hardware and software dependencies, along with precautions on upgrading from SQL Server 2005 to SQL Server 2008. For instance, you need to have the latest SharePoint service packs in place before installing SQL Server 2008.

"Office SharePoint Server 2007 supports SQL Server 2008," the document says. "However, you must install Windows SharePoint Services 3.0 SP1 or later and Office SharePoint Server 2007 SP1 or later before you install SQL Server 2008."

IT admins have to download and run the setup program, as well as "the SharePoint Products and Technologies Configuration Wizard," to perform the MOSS 2007 SP1 install.

The SharePoint Hosting and Development blog provides some upgrade tips and suggests that the "upgrade from [SQL Server] 2005 to 2008 is a pretty simple process." IT admins will have to install ".NET 3.5 SP1 and hotfix KB942288-v4" first in order to move to SQL Server 2008.

Microsoft's blog provides a list of features describing why IT admins should upgrade, but most of the benefits seem to apply just to improvements in SQL Server 2008. One potential benefit is data compression, which can be automated by default. Compression can reduce your backup size, although SharePoint stores data in the binary large object (blob) form, which doesn't compress as well as other data types.

"That said, you can probably see up to 30% [size reduction] on your blob-laden content databases and perhaps 90-95% on your other databases," the blog estimates.

Other improvements include a Resource Governor for SQL Server maintenance and administration, although the blog cautions that it "should not be used to control SharePoint's usage of SQL."

Those interested in Microsoft's supportability statement for MOSS 2007 -- which goes by the descriptive title, "Determine hardware and software requirements (Office SharePoint Server)" -- can access it on Microsoft TechNet here.

About the Author

Kurt Mackie is online news editor, Enterprise Group, at 1105 Media Inc.

Featured

  • artificial intelligence on laptop

    OpenAI to Combine AI Products into Desktop 'Superapp'

    OpenAI is reportedly developing a desktop application that would combine several of its emerging AI products into a single platform, according to reports, marking the latest step in the company's effort to transform ChatGPT from a standalone chatbot into a broader productivity and automation environment.

  • Abstract digital data stream with binary code and colorful light trails

    Microsoft Releases Open Source AI Safety Tools for Agent Development

    Microsoft released RAMPART and Clarity as open-source projects intended to help developers test AI agents earlier in the software lifecycle and turn red-team findings into repeatable engineering checks.

  • abstract illustration of artificial intelligence

    CSU Shares AI Learnings in Systemwide Survey

    In a systemwide survey of more than 94,000 faculty, staff, and students, California State University recently documented widespread AI use across its 22 campuses.

  • Profile silhouette of a person thoughtfully touching their chin, overlaid with transparent data visualizations and digital interface elements suggesting artificial intelligence and analytics.

    The Institutional Knowledge Shift Is Reshaping Higher Ed IT

    Higher education IT leaders are navigating a quiet but consequential transition: Experienced team members are retiring or leaving for private-sector roles, and the teams replacing them are smaller, newer, and often stretched thin. The result is a structural shift in how technology decisions are made, executed, and sustained.