|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Upgrading from SQL Express to SQL Enterprise
I am fairly new to SQL and have run into a problem where I need some help. I have a test MOSS 2007 installation that is running on SQL Express and I wanted to upgrade it to SQL Enterprise. I used the SKUUPDATE=1 switch making sure not to select the default instance and to select the OFFICESERVERS instance (which is the MOSS setup). The installation said it was successful. However, when I opened up SQL Management and did a query, it told me that Express Edition was not upgraded. After some investigation, I found out there is a SQL Express edition that is linked to the SharePoint Instance and a separate installation of SQL 2005 Enterprise that has nothing but sample databases. I would like to use the full blown version of SQL 2005 but am not sure how to proceed. Should I try to uninstall the version that is in Control Panel and then try to upgrade the SQL Express again. (It says it is SQL 2005 but I am worried it really is SQL Express so uninstalling that would torch my system). Can I just copy the databases from SQL Express and import them into SQL Enterprise? By the way, both instances of SQL have SP3 installed. (I hope I have posted in the right newsgroup. This seems more situated for a SQL problem than a MOSS problem). Thanks for your help, FD
Show quote
Hide quote
"FD" <fd@nospam.net> wrote in message When you connect to the two instances in management Studio, what are they news:#PIX5sO#JHA.4036@TK2MSFTNGP04.phx.gbl... > Hi all, > > I am fairly new to SQL and have run into a problem where I need some help. > > I have a test MOSS 2007 installation that is running on SQL Express and I > wanted to upgrade it to SQL Enterprise. I used the SKUUPDATE=1 switch > making sure not to select the default instance and to select the > OFFICESERVERS instance (which is the MOSS setup). The installation said it > was successful. However, when I opened up SQL Management and did a query, > it told me that Express Edition was not upgraded. After some > investigation, I found out there is a SQL Express edition that is linked > to the SharePoint Instance and a separate installation of SQL 2005 > Enterprise that has nothing but sample databases. I would like to use the > full blown version of SQL 2005 but am not sure how to proceed. Should I > try to uninstall the version that is in Control Panel and then try to > upgrade the SQL Express again. (It says it is SQL 2005 but I am worried > it really is SQL Express so uninstalling that would torch my system). Can > I just copy the databases from SQL Express and import them into SQL > Enterprise? By the way, both instances of SQL have SP3 installed. > called? You can't have two instances on the same machine called OFFICESERVERS. It sounds as though you installed Enterprise into an instance with a different name. You can copy the databases between the two instances. There are several ways you could do this. There's a Copy Database wizard in Management Studio, you could copy the MDF file and attach it or you could back up and restore the database (make sure you restore the files to a different location, though) HTH Thanks for the help, Bob
It looks like the backup/restore procedure would be the best but I have a few questions. When I open up SQL Server Management Studio, one instance is called OFFICESERVERS (Sql Express) and the other instance is just the name of the computer itself, TS2-GX270. (SQL Enterprise) If I open up SQL Server Management Studio and run the query "SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition'), I get Enterprise Edition for the TS2-GX270 instance and Express Edition for the TS2-GX270\OFFICESERVERS Editon. If I understand you correctly, it looks like my MOSS installation (OFFICESERVERS) is what I need to backup. Can I just backup the databases created when MOSS was installed or do I have to back up all the databases including the System Databases? (Since this instance was created with SQL Express) Also, when I do the restore, you said I need to restore it to a different location. Do I just create a folder on my root c: drive and restore it to that or do I have to restore it to a certain place so that SQL Enterprise will see it and connect to the MOSS installation? FD Show quoteHide quote "Bob Simms" <bob.si***@qa.com> wrote in message news:163A01B5-FE24-4628-B24F-BF9F55AC90B1@microsoft.com... > "FD" <fd@nospam.net> wrote in message > news:#PIX5sO#JHA.4036@TK2MSFTNGP04.phx.gbl... >> Hi all, >> >> I am fairly new to SQL and have run into a problem where I need some >> help. >> >> I have a test MOSS 2007 installation that is running on SQL Express and >> I wanted to upgrade it to SQL Enterprise. I used the SKUUPDATE=1 switch >> making sure not to select the default instance and to select the >> OFFICESERVERS instance (which is the MOSS setup). The installation said >> it was successful. However, when I opened up SQL Management and did a >> query, it told me that Express Edition was not upgraded. After some >> investigation, I found out there is a SQL Express edition that is linked >> to the SharePoint Instance and a separate installation of SQL 2005 >> Enterprise that has nothing but sample databases. I would like to use the >> full blown version of SQL 2005 but am not sure how to proceed. Should I >> try to uninstall the version that is in Control Panel and then try to >> upgrade the SQL Express again. (It says it is SQL 2005 but I am worried >> it really is SQL Express so uninstalling that would torch my system). >> Can I just copy the databases from SQL Express and import them into SQL >> Enterprise? By the way, both instances of SQL have SP3 installed. >> > When you connect to the two instances in management Studio, what are they > called? You can't have two instances on the same machine called > OFFICESERVERS. It sounds as though you installed Enterprise into an > instance with a different name. > > You can copy the databases between the two instances. There are several > ways you could do this. There's a Copy Database wizard in Management > Studio, you could copy the MDF file and attach it or you could back up and > restore the database (make sure you restore the files to a different > location, though) > > HTH > > > -- > Bob Simms > Senior Learning Consultant > QA - transforming performance through learning > www.qa.com <inline>
> When I open up SQL Server Management Studio, one instance is called Then SQL Enterprise is installed as the default instance.> OFFICESERVERS (Sql Express) and the other instance is just the name of the > computer itself, TS2-GX270. (SQL Enterprise) > If I open up SQL Server Management Studio and run the query "SELECT Sounds good> SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), > SERVERPROPERTY ('edition'), I get Enterprise Edition for the TS2-GX270 > instance and Express Edition for the TS2-GX270\OFFICESERVERS Editon. If I > understand you correctly, it looks like my MOSS installation > (OFFICESERVERS) is what I need to backup. > Can I just backup the databases created when MOSS was installed or do I At some point every SQL question has the same answer: it depends. Do you > have to back up all the databases including the System Databases? (Since > this instance was created with SQL Express) have anything in the system databases that you need in the new installation? For example, do you want the same logins? These are held in the master. Do you have SQLAgent jobs? These are held in the MSDB. If so, you're probably best off using wizards in the management studio for transferring these objects, or creating an SSIS package specifically. Don't try to back and restore the system databases from one instance to another, because at best it won't work, at worst you could break it. > Also, when I do the restore, you said I need to restore it to a different It can be any location your heart desires. If this is a production database > location. Do I just create a folder on my root c: drive and restore it to > that or do I have to restore it to a certain place so that SQL Enterprise > will see it and connect to the MOSS installation? > ideally the data files should be on a RAID 5 or 0+1 array, and the log files on a separate RAID 1 array, but technically any folder will do. But if you don't say otherwise, the restore will try and restore the files to the location it backed it up from. As these files are there being used by Express, the restore will fail, so you need to stick them somewhere else. Bob Simms Senior Learning Consultant QA - transforming performance through learning www.qa.com Thanks, Bob --you have helped me greatly...
FD Show quoteHide quote "Bob Simms" <bob.si***@qa.com> wrote in message news:50DF2D90-84AC-4F69-907E-EDF14196F761@microsoft.com... > <inline> > >> When I open up SQL Server Management Studio, one instance is called >> OFFICESERVERS (Sql Express) and the other instance is just the name of >> the computer itself, TS2-GX270. (SQL Enterprise) > > Then SQL Enterprise is installed as the default instance. > >> If I open up SQL Server Management Studio and run the query "SELECT >> SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), >> SERVERPROPERTY ('edition'), I get Enterprise Edition for the TS2-GX270 >> instance and Express Edition for the TS2-GX270\OFFICESERVERS Editon. If I >> understand you correctly, it looks like my MOSS installation >> (OFFICESERVERS) is what I need to backup. > > Sounds good > >> Can I just backup the databases created when MOSS was installed or do I >> have to back up all the databases including the System Databases? (Since >> this instance was created with SQL Express) > > At some point every SQL question has the same answer: it depends. Do you > have anything in the system databases that you need in the new > installation? For example, do you want the same logins? These are held in > the master. Do you have SQLAgent jobs? These are held in the MSDB. If > so, you're probably best off using wizards in the management studio for > transferring these objects, or creating an SSIS package specifically. > Don't try to back and restore the system databases from one instance to > another, because at best it won't work, at worst you could break it. > >> Also, when I do the restore, you said I need to restore it to a different >> location. Do I just create a folder on my root c: drive and restore it >> to that or do I have to restore it to a certain place so that SQL >> Enterprise will see it and connect to the MOSS installation? >> > It can be any location your heart desires. If this is a production > database ideally the data files should be on a RAID 5 or 0+1 array, and > the log files on a separate RAID 1 array, but technically any folder will > do. But if you don't say otherwise, the restore will try and restore the > files to the location it backed it up from. As these files are there > being used by Express, the restore will fail, so you need to stick them > somewhere else. > > Bob Simms > Senior Learning Consultant > QA - transforming performance through learning > www.qa.com
Other interesting topics
How to Enqueue Messages With Service Broker in a Timely Fashion
Activity Monitor not showing Database names Server2000 Std Edition Timeouts stats_ver_current? Maintenance did not delete old files Unable to access the tape for database backup purpose share Template location for SSMS using profiler to capture errors Securing MSSQL Missing Index Details |
|||||||||||||||||||||||