Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8130593
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T08:46:17+00:00 2026-06-06T08:46:17+00:00

Are there any pitfalls when upgrading SQL Server Express to SQL Server Standard 2008

  • 0

Are there any pitfalls when upgrading SQL Server Express to SQL Server Standard 2008 R2 that serves a Microsoft Sharepoint 2007 (MOSS 2077) implementation?

We recently completed an update of a team foundation sql server by installing the Standard Edition of SQL over the top of the existing Express edition with no issue. So we plan to upgrade the Sharepoint server the same way.

Are there any pitfalls or hints we should be aware of? I am concerned that the data and customizations done in Sharepoint are not lost or damaged.

We will as a matter of course be taking backups prior to any change.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T08:46:18+00:00Added an answer on June 6, 2026 at 8:46 am

    Question: Are there any pitfalls when upgrading SQL Server Express to SQL Server Standard 2008 R2 that serves a Microsoft Sharepoint 2007 (MOSS 2077) implementation?

    There are no real pitfalls, but definitely some items to put on your migration checklist. You need to convert the whole instance from Express to a 2008 R2 “real database solution”. This is a good move to make.

    Given that you have an Express edition that came with the Sharepoint installation, it is mostly likely not a SQL Server 2008 or SQL Server 2008 R2 edition, and most likely have not SSMS tools installed. You will need the Standard Edition installation media and the product key. That is a given. Run the setup program from the standard edition media directly. Do NOT try to run setup from the installed SQL Server and use Edition upgrade option.

    Verify the installation using SQLCMD once you have the Standard Edition in place. Run setup from installation media again and install the desired shared components such as SSMS, Integration Services, Books Online, etc. The Sharepoint setup installed SQL Agent installed with SQL Express by the Sharepoint installation may be disabled and set to run as “Network Service” and not have the SysAdmin SQL Server rights.

    Change the service account for the Agent to have the sysadmin rights. The SQL Agent will then start. Check database options, file size, auto grow settings, and other maintenance items for the sharepoint databases. You probably want to move the Sharepoint databases to a better location than the default folders in Program Files –> Common Files. Good luck as you move off of the Express Edition.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Just wondering if there are any pitfalls using .net as the extension for a
Are there any other similar packages that help identify and provide capabilities for browser
Are there any libraries available that allow Android applications to transcode videos to different
Is it considered correct/ are there any pitfalls in returning partial templates to ajax
I would like to know if there are any pitfalls on calling a static
I am considering buying an Apple MacBook Pro. Are there any pitfalls developing C#/.NET
Question says it all: Are there any pitfalls with allocating exceptions on the heap?
Are there any pitfalls to code like this? var Foo = function() { this.bar
Is there any way in which I can automatically convert a Custom Class Object
Is there any JavaScript/jQuery library for creating step-by-step forms? It's better if it has

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.