Re: Saving WSS site prior to upgrading SQL Server 2005 Express to Standard/Enterprise

You decide when you install WSS 3.0 whether you use the embedded version of SQl Server 2005 Express or whether you want to use a different database system.

If you choose Basic Installation or 'Advanced Installation + Single-Server' it will use the embedded version even if another version of SQL Server 2005 is available.

The advantages of the embedded version ("Windows Internal Database") over the standard SQL Server 2005 Express is that there is no limit to the database size (4GB with SQL Server 2005 Express). The disadvantage is that you can only use the embedded version for SharePoint databases (and other "windows components").

From the above you should know whether you have only one database system or two. If you have two, your SP databases will be in the Windows Internal Database and you can migrate them by following that article.

Mike Walsh

Zaur Bahramov wrote:
Sorry. As you know I'm a newbie in wss. So I appologize if my question might seem stupid.
I have a Microsoft SQL Server 2005 Express Edition installed. I also have a database used by WSS visible under databases in the default instance of SQL Server Express as:
SERVER\SQLEXPRESS.

Or WSS daes make a use of the embedded version for internal wss stuff?
Please, explain, how do I check this.

I've found this link, so, I thought this might be what I need to do. Of course after using stsadm tool to create a backup as mentioned in the link you've provided.

Thanks!




"Mike Walsh" <englantilainen@xxxxxxxxxxx> ha scritto nel messaggio news:OwXyQjTzIHA.3504@xxxxxxxxxxxxxxxxxxxxxxx
I presume you don't really mean the standard SQL Server 2005 Express edition but embedded version called the "Windows Internal Database".

If so this is a description of how to move it to SQL Server 2005

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1144

Mike Walsh
WSS FAQ http://www.wssfaq.com / http://www.collutions.com
no private questions please

Zaur Bahramov wrote:
Hi!

I have set up a WSS site using SQL Server 2005 Express edition. Now I need to make an upgrade to Standard edition of SQL server 2005. How can this be implemented? Can I just detach my databases from Express and re-attach them to Enterprise? How about the instances, like now I have the following SERVERNAME\SQLEXPRESS?

Is there a documented procedure on this?

Thank you!


.

Relevant Pages

  • RE: WSS install locked into MSDE DB - Can not install for SQL Serv
    ... We have been using the WSS Web Admin interface. ... directing WSS to use SQL server. ... > Extend And Create A Content Database. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Why use WSS and not MSSX?
    ... SQL Server is usually enough and is something to move to when a single server WSS 3.0 installation is having load problems. ... Look at the sticky post I wrote in the General and Setup/Admin forums for information on which forum is suitable for what. ... The major difference I can suggest is that MSSX comes with a database ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: SharePoint Services 3.0 unable to display content
    ... When connecting to the original configuration database, ... You are correct about the SQL Server. ... I am 100% about the WSS. ... Microsoft Windows SharePoint Services 2.0 ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: installing help for sql 2005
    ... you have database users that are not mapped correctly to logins. ... SQL Server Documentation Team ... installation help with snap shots because i installed the sql server ... remote connections are disabled by default. ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL SERVER 2008 Express + SP1
    ... I installed the SQLXPR_X64, and before I attempted the SP1, SQLEXPRESS database was 64bit for the configuration, better yet the repair do work anymore because SP1 changed them somehow to 32 and the original install was 64 ... If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. ... And regarding your sql server installation, ...
    (microsoft.public.sqlserver.setup)
Loading