Skip to main content
Sign In |
  Help (new window)
Trans Am

Todd Klindt's SharePoint Admin Blog

Go Search
Home
Blog
Netcast homepage
SharePoint Terminology Wiki
  

Todd Klindt's home page > Todd Klindt's SharePoint Admin Blog > Posts > Upgrade SQL Express to Standard or Enterprise

11/25/2007

Upgrade SQL Express to Standard or Enterprise

Microsoft so very graciously provides a free version of SQL 2005, SQL Express, with MOSS. If you install MOSS using the Basic option or Single Server under Advanced you get SQL Express automatically. So what if as a budding newbie SharePoint admin you chose the Basic option, but now as a wise aged SharePoint admin you've seen the error of your ways and want to use a more respectable version of SQL for your SharePoint backend? You're in luck. In this blog post I'll walk you through upgrading SQL Express to SQL Standard or Enterprise.

First thing you need to do is get a copy of SQL 2005 Standard or Enterprise. Which version you choose depends on the redundancy and availability you want. Either will upgrade from Express. After you have your media you can start the install. This step is important as you have to pass the setup program a parameter to let it know you're doing an upgrade. To upgrade use the command setup.exe SKUUPGRADE=1. It should look like this:

The setup should kick off and it won't give you any indication that you passed it a parameter. Never fear, it will come up later. When the setup gets to the instance selection make sure you don't accept the default instance and you choose the SQL Express instance. First click Installed Instances:

Then choose the OFFICESERVERS instance from the list and hit OK:

Your next screen should confirm that it found SQL Express:

If you click the Details… button you'll see that the setup confirms that SQL Express can be upgraded. This step is optional.

At this point you can Close the box and hit OK until the setup is finished. After the setup is finished you'll want to apply SP2 for SQL 2005 and any post SP2 patches that are available. I don't know if it's required but I always do an IISRESET after this to make sure that SharePoint reconnects properly to SQL.

That's all there is to it. Once you are using full SQL you have quite a few more options available to you like log shipping, database replication, SQL Profiler and more. If you have any questions about how to leverage those tools with SharePoint, leave me a comment and let me know.

tk

 

Posted at 11:13 AM by Todd O. Klindt | Permalink | Email this Post | Comments (159)

Comments

PERFECT...

BEAUTIFUL ANSWER! JUST WHAT WE NEEDED!! THANK YOU!! I´m sure many people don´t know exactly what kind of SQL is installed with the basic option. Thank GOD it can be upgraded!!!
at 12/10/2007 3:34 PM

You are my man!!

thanks god my friend!! you save my life!! mil gracias amigo
at 12/11/2007 8:16 AM

Re: PERFECT...

Always glad to help.  One thing I meant to mention in the blog post was that while MOSS bundles SQL 2005 Express, WSS does not.  WSS uses a product called "Windows Internal Database" or WID.  I don't know of any way to upgrade WID to any flavor of SQL.  The good news is that WSS is pretty simple, so you can just reinstall it with SQL and use the WID database files.  If there's demand I could write something up on it too.

tk
Todd O. Klindt at 12/11/2007 9:19 AM

Re: You are my man!!

¡De nada!  Comments like this always remind me why I spend the time writing these blog posts up.  :)

tk
Todd O. Klindt at 12/11/2007 9:20 AM

Upgrade WID to standard SQL

A light from the sky.
I'm using WID for WSS and with a standard SQL installed currently on the system. I'd like to upgrade WID to standard SQL. Appreciate you very much in advance.
at 12/24/2007 1:20 AM

Re: Upgrade WID to standard SQL

I may have a way to do this, but with the holidays I won't have a chance to try it for a couple of days.  If don't want to wait you could also just use STSADM -o backup to back your site collections up, reinstall WSS using SQL then use STSADM -o restore to restore your content.  Since WSS doesn't have SSPs or anything it can be moved that way very easily.

tk
Todd O. Klindt at 12/24/2007 8:04 AM

parameter is case sensitive

Note that the parameter must be type exactly as shown (not skuupgrade=1).
at 1/3/2008 3:54 PM

EUREKA!!

Thanks for the help. We actually have a previous named instance that we HAVE to upgrade from Express or we're screwed. You're so money and you don't even know it, baby!
at 1/9/2008 3:08 PM

Re: EUREKA!!

Excellent.  Glad to hear it.  Comments like that make me glad I post this stuff.

tk
Todd O. Klindt at 1/11/2008 1:13 PM

No opportunity to upgrade instance

I am using SQL 2005 Developer Edition.  I have been able to upgrade SSMS SSRS clint components, etc.  I do not get the option to upgrade an instance of any databases during the install.  Any idea where I am going wrong?
at 1/16/2008 9:15 AM

Re: No opportunity to upgrade instance

I don't know that you can upgrade the Developer Edition to Enterprise.  At least with Developer Edition it's easy enough to back your databases up or detach them and attach them to an installation of Enterprise.  You may have to uninstall Developer and install Enterprise.

tk
Todd O. Klindt at 1/16/2008 10:02 PM

XELLENT

i tried all best solution to upgrade but nothing works but above solution saved 100+hrs.
thanks
at 1/22/2008 2:17 AM

upgrade went fine but sharepoint pages will not display

Hi, i followed the above and upgraded the database to enterprise.  Upgrade went fine, but when we tried to reopen sharepoint it would not display the portal.  Any additional steps?
at 1/30/2008 2:25 PM

Thank you man

"Shokran Jeddan", it's "thank you very much" in Arabic.
at 2/11/2008 10:31 AM

Thanks..

Hi, Thanks a lot. We installed Symantec Backup EXEC with SQL Express version and now need to go for SQL STD. I will follow ur steps...BTW I am not an SQL expert...
at 2/12/2008 3:13 AM

migrating db's

Great post Todd - but I have a question on a slightly different angle...

Lets say you have an Express based MOSS installation which is considered a development/pilot environment. You then want to disconnect the farm, migrate the db's to a full SQL 2005 cluster then reconnect the farm.
What are the considerations?? are the Express db's locked to only run on Express? are they automatically unlocked when added to a 2005 cluster? is it even possible to do a straight db move like this or should the Express installation be upgraded first then migrate the db's??
I'm sure there are plenty of other considerations - any pointers would be appreciated.
at 2/19/2008 3:49 PM

Re: migrating db's

Sorry I didn't respond to this sooner.  I forgot.

The SQL Express databases are completely compatible with full versions of SQL.  If you didn't want to upgrade your Express instance to Standard or Enterprise then I would recommend just backing your databases up in Express and restoring them to the Standard or Enterprise installation you want them to be in.  You can download a copy of SQL Management Studio that will work with SQL Express here, https://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en .  Install that, then back your databases up.  You should be fine.

tk
Todd O. Klindt at 2/25/2008 9:55 PM

WSS WID to SQL 2005

Todd,

Have you had a chance to look into more migrating from the WIS on WSS to SQL 2005 (on another server). I would like to do this myself.

Thanks,

Kevin O
at 2/26/2008 10:52 AM

WID to SQL Server Standard Edition

I read your blog and I am trying to make sure I understand you correctly.  SO...I cannot just do an upgrade and select the named instance for it to upgrade to  SQL standard edition.  I did check the system and it reflects WSS 3.0 and WID in the programs list.   Sorry to ask for clarification on this....
at 2/27/2008 3:01 PM

Thanks

This is brilliant.
I needed the backup maintenance plans to run bacup for this instance and now it's working.
at 2/28/2008 6:13 AM

migrating moss databases to sql 2005 standard

okay, so I've upgraded from express to standard, but it seems like the tables are still limited in size to the express limit of 4 gigs. How do I get them to be able to grow larger? Do I have to create new tables?
at 3/4/2008 6:48 PM

Re: migrating moss databases to sql 2005 standard

I'm not sure if you need to create new databases or not.  I haven't tested that.  I mentioned this was possible mainly for management purposes.  I haven't tried to grow a database that was capped by SQL Express after it was upgraded.

tk
Todd O. Klindt at 3/5/2008 8:42 AM

Re: Upgrade SQL Express to Standard or Enterprise

if I look at the properties of the database, it still says that it is a sql express database, and I guess the whole instance is (OFFICESERVERS). I'm thinking I have to create a new instance, and migrate everything over, which I can't find any help on - maybe I'll just give it a fresh start and reinstall (I'm assuming it will recognize that I have sql standard and not install an express instance)
at 3/5/2008 11:34 AM

Re: Upgrade SQL Express to Standard or Enterprise

It doesn't sound like the upgrade actually took.  Where in the database properties are you seeing it say it's an SQL Express Database?  I'm looking at an instance I've upgraded and I can't find any references to SQL Express anywhere in the database properties.

tk
Todd O. Klindt at 3/6/2008 9:10 AM

Re: Upgrade SQL Express to Standard or Enterprise

if I look at the properties of the database, it still says that it is a sql express database, and I guess the whole instance is (OFFICESERVERS). I'm thinking I have to create a new instance, and migrate everything over, which I can't find any help on - maybe I'll just give it a fresh start and reinstall (I'm assuming it will recognize that I have sql standard and not install an express instance)
at 3/6/2008 10:43 AM

Re: Upgrade SQL Express to Standard or Enterprise

You shouldn't have to create a new instance.  Did you select the Officeservers instance when you ran the install?  I'm still not sure where you're seeing "SQL Express" in the database properties.  If you do decide to do a reinstall you can use your existing content DBs.  Preferably you'd back them up, then restore them to your full SQL instance once it's installed.  You can also just mount the MDF files, but that's not a good way to do it.  Also, when you reinstall MOSS it will not automatically find SQL even if it's on the same box.  You need to point it to the local instance manually, so DO NOT DO a single server install.  If you do a Basic or Single Server Install you'll get SQL Express again.

Good luck.

tk
Todd O. Klindt at 3/6/2008 11:15 AM

Re: Upgrade SQL Express to Standard or Enterprise

I just ran the sql2005 setup again, this time using the SKUUPGRADE=1 switch, and it seems to have taken. I was seeing that the database was express format in the "connection properties" in management studio. Now it says Product Name = Standard Edition. I was then getting a bunch of 17310 errors in the app log, but it looks like that might get fixed by installing sql 2005 sp2 - which is a big download.
at 3/6/2008 2:06 PM

Re: Upgrade SQL Express to Standard or Enterprise

Good deal.  Glad to hear it's working now.  Thanks for updating us.

tk
Todd O. Klindt at 3/6/2008 5:38 PM

Upgrade SQL Expres vs. 'Custom Install'

Thanks for the great info, you saved me lots of pain with that simple parameter.

I do have a quick question though... Is there any advantage to running a Custom Installation of MOSS in order to create a Farm on a single server? Or is performing the 'Single Server Install' and upgrading the SQL instance just as good?

Other than the potential to expand the installation to a larger farm that is... That part I get...

Thanks again.
at 3/13/2008 9:30 AM

Re: Upgrade SQL Expres vs. 'Custom Install'

Somewhere, Shane Young will be smiling.  He HATES Basic installs and will love me dissuading someone from doing one.  :)

I never recommend using Basic Install or Advanced > Single Server (they're the same thing).  The only time I ever use it is when I'm testing something quickly in a Virtual PC.  Even then it feels dirty.  The functionality is different.  When you choose Basic or Single Server the install IS different.  Just upgrading SQL Express to SQL Standard or Enterprise doesn't put everything on the same level as if you'd done a Complete install.  For one, if you do a Basic install SharePoint uses System Accounts instead of domain accounts.  This makes moving things around or adding more WFEs more complicated.  Second when you install as Basic SharePoint makes some Registry changes that throttle it accordingly, knowing that SQL Express can't spawn as many threads and such.  Richard Riley at Microsoft and I recently spoke about this.  Also, you may have trouble with upgrades in the future if you initially did a Basic install.  Some upgrade options may not be available to you.

I always recommend doing Advanced > Complete.  That gives you all the bits you need and gives you the flexibility if you need to move things around.

tk
Todd O. Klindt at 3/13/2008 10:37 AM

THANK YOU

This is the perfect solution to my current problem.  It is my first time installing SharePoint so I am still learning the in's and outs.  Needless to say I will never install with just Express Edition again.
at 3/13/2008 12:07 PM

Re: THANK YOU

SQL Express is fine.  It's when you install SQL Express as part of a Basic install that you get into trouble.

tk
Todd O. Klindt at 3/13/2008 1:11 PM

Thank you

We just started to use MOSS and had no idea what SQL database sever was installed. Yestersady I noticed SQL express database just has 4GB capacity. I thoght we'll be in big trouble. Seems you article suddenly solve our problem. I'll try soon. Two questions, do I need to back up everything first? Are the Content Databases name same after upgrading?

Thanks again.
at 4/29/2008 10:16 AM

Re: Thank you

Glad to hear it'll help.  You do not _need_ to back up your databases, but you absolutely _should_ back them up.  You should always back them up before any big upgrades like this.  Second, the database names and instance will be the same.  SharePoint has no idea that anything has changed.

If your environment is new, I would recommend considering making STSADM backups of your site collections, then doing a fresh install and choosing the Advanced > Complete method instead of Basic.  Along with installing SQL Express the installer makes some other decisions based on the type of install you do that aren't as easily undone.

tk
Todd O. Klindt at 4/29/2008 10:38 AM

Thanks again

We already have some sites on it and the boss want to create more and more sites on it. That's why it scares me so much beacuse of the 4 GB limit. Do I need to upgrade WID to any SQL?

Thanks.

yd
at 4/29/2008 1:17 PM

Dumb question?

This may be obvious, but on the "Existing Components" screen you show above, do you check the "SQL Server Database Services 9.00.1399.06" box before proceeding?

Eric
at 4/30/2008 1:43 PM

Re: Dumb question?

I believe you HAVE TO check that box to continue.  Regardless I've always checked it and in the times it was grayed out and I couldn't check it, I couldn't do the upgrade.

tk
Todd O. Klindt at 4/30/2008 11:38 PM

Re: Thanks again

If you've done a lot of customizations, and you just have content, I'd consider either using STSADM to backup the site collections or backing the databases up and doing a reinstall and point to SQL.  I do not think you can upgrade WID.

tk
Todd O. Klindt at 4/30/2008 11:40 PM

Help with restoring from SQL Express

We too ran off the Express version and learned the hard way.  Now we have built a new SQL2005 box and installed Sharepoint2007.  Afterwards we restored the databases using SQL server management tool but now we can't figure out how to get SharePoint to see it.  Originally we updated the SQL express as mentioned above but SharePoint does not see it as the full version.  This is preventing us from uploading files.  Could you please let us know what the steps are for restoring this, if we use the built in restore of SharePoint it claims that there is no back up history?
at 5/5/2008 4:56 PM

How about this?

Hi, TK:
Many Thanks.
I'm trying to install a stand alone SharePoint 2007 server. If I install SQL 2005 Enterprise first and select 'Advanced' when I install MOSS, will it choose SQL 2005 Enterprise or automatically install SQL Express?

YD
at 5/6/2008 8:16 AM

Re: How about this?

You're on the right track.  If you want to use a local, non-Express version of SQL you need to do an Advanced > Complete (or Web Front End Only) option.  If you do that when you run the Configuration Wizard after install it will ask you which SQL Instance to use.  Just point it at the local machine and you're good to go.

tk
Todd Klindt at 5/6/2008 8:39 AM

Re: Help with restoring from SQL Express

This situation is tricky.  Did you move all of your databases or just your Content databases?  As far as I know the only supported method for moving all of your databases from one SQL instance to another is using SQL Aliases.  If you did not use an SQL Alias and you moved all of your databases it's a real mess to untangle.  The best recommendation I can give here is to rerun the Configuration Wizard, set up a new Farm (which means you'll be creating a new Config database) and then attach your Content databases to your new Farm.  You might also read up on SQL Aliases (search for
"cliconfg.exe") and see if you can use them to fix your installation.

Good luck,
tk
Todd Klindt at 5/6/2008 8:48 AM

Re: How about this?

Thanks.
at 5/6/2008 3:10 PM

Content Databases

I don't know it's proper to ask this question here or not. My C: doesn't have much space to use, but all the content databases are in C:. How can I move some of them to D: or create new Content DB in D:?
Thanks.
at 5/8/2008 9:26 AM

Re: Content Databases

First keep in mind that SharePoint doesn't care about the physical location of the database files.  Basically all it cares about is the SQL instance name and the database name.  Then it says "Hey {instance name} let me access {database name}"  I mention this because if you want to move your databases from C to D there is nothing to do in SharePoint.  It's all SQL.

You can create new Content DBs on D.  That won't fix the space problems you have on C, but it will reduce how bad they get.  Moving the databases is easy.  Detach the database in SQL Management Studio, move the appropriate MDF and LDF files from C to D, then reattach the databases in SQL Management Studio.  Make sure you give them the same name so that SharePoint can find them.  You have to give SharePoint an IISRESET if it notices the databases are offline while you're moving them.

That's all there is to it.  :)

tk
Todd O. Klindt at 5/8/2008 11:19 AM

Re: Content Databases

Thanks. Very helpful.
at 5/8/2008 1:46 PM

Migration

We are going to build a SharePoint 2007 farm. Can I just back up all the sites from my standalone server and restore to the farm?

Thanks.
at 5/19/2008 9:42 AM

Re: Migration

Yes, that should work.  You can do it at the SQL level and reattach the content databases, or you can do it at the Site Collection level with STSADM -o backup.  Just make sure both environments are at exactly the same SharePoint patch level.

tk
Todd Klindt at 5/19/2008 1:17 PM

Re: Migration

How about use Central Administration Backup/Restore?

Thanks.
at 5/19/2008 2:21 PM

Re: Migration

I haven't done it myself, but it should work.  Central Admin is just doing a SQL dump, so it's no different than doing it manually in SQL, it's just a different interface.  It's worth a try, definitely.

tk
Todd Klindt at 5/19/2008 2:39 PM

Re: Migration

How about use Central Administration Backup/Restore?

Thanks.
at 5/20/2008 7:38 AM

stsadm.exe backup

I know it's not related to this topic, but you already give a quick and a meaningful answer.
If I use -overwrite, does it just keep the latest version? If so, how can I restore the old version?

Thanks.
at 5/27/2008 2:59 PM

Re: stsadm.exe backup

If you use the -overwrite parameter with "stsadm -o backup -filename" STSADM will overwrite the file specified as -filename if it already exists when it creates the backup.  It doesn't have anything to do with versions.

Hope that helps,
tk
Todd O. Klindt at 5/27/2008 9:15 PM

Re: stsadm.exe backup

So if I schedule to automatically backup(I use 'export' to backup a single site) and late the user wants to restore to an older version for his site, how to handle it? Since I can't change the filename automatically?

Thanks.
at 5/28/2008 8:04 AM

SQL Upgrade from express to standard

I upgraged the SQL from Express to Standard just as you have instructed.  However, it did not load the management tools to allow the backups.  Also, in the properties, it states that I am on Standard but the splash screen still says studio express.   Also, now that I am on Standard, can I remove the Express version from add/remove programs??  Thanks for the blog. 
at 6/4/2008 9:12 AM

Still Express?

I upgraged the SQL server from Express to Enterprise weeks ago according to your instruction. Today I checked the version of it by using:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY
('productlevel'), SERVERPROPERTY ('edition')

It gives 'Express Edition'. Do I need to upgrade again?


Thanks.
at 6/12/2008 3:20 PM

Re: Still Express?

Sounds like it didn't take.  When you did the upgrade, did you choose your existing instance (Should have looked like servername\officeservers) and choose to upgrade it?  I know I've forgotten that step in the past.

tk
Todd Klindt at 6/12/2008 5:00 PM

Re: Still Express?

Solved the problem I didn't check SQL Server Database Service 9.00.1399.06 before.

Thanks.
at 6/13/2008 11:09 AM

What's wrong with this(not SQL server)?

I asked this question in several places but nobody answers it.

I have a sharepoint 2007 server with 2 IPs. I used one IP for a web site with SSL. It works fine. Then I used the other one for two web sites(for intranet use). Both the web sites work fine on my computer, all the computers in our office (~10) and some computers on other subnet(i.e. x.x.133.x), but we couldn't access the two sites through other subnets(even some PCs on x.x.133.x). I don't know it is a web site configuration issue or a network issue.

Thanks in advance.
at 6/13/2008 11:16 AM

Re: What's wrong with this(not SQL server)?

Have you checked your IIS logs to see if the machines tha tcan't hit the site are getting as far as IIS?  Do the clients get any errors?  Can the clients ping the IP address that the site is on?

tk
Todd Klindt at 6/21/2008 5:27 PM

Re: What's wrong with this(not SQL server)?

Thanks. Solved.
at 6/23/2008 10:15 AM

failed to load "dbmslpcn.dll".  The specified module could not be found

After the upgrade to SQL server 2005 standard, I get the error, failed to load "dbmslpcn.dll".  The specified module could not be found.  I have the .dll in windows\system32, but always get the error. 

wastoo
at 6/29/2008 9:39 AM

Standalone server question

Can I add my Basic(not Advanced) Standalone SharePoint 2007 server to our domain and then import user profiles from the AD?
The Basic Standalone SharePoint 2007 server couldn't be added to the MOSS farm, right?

Thanks.

YD
at 7/24/2008 10:22 AM

Re: Standalone server question

Servers that have a MOSS installed with a Basic install can certainly be members of a domain.  If you start doing profile imports you'll have to be careful with accounts that are being used.  Basic installs have all of your application pools run as local accounts, which will not have to access to AD.  You might need to change some of your app pool IDs to be able to import profiles.

tk
Todd Klindt at 7/24/2008 2:04 PM

Perfect

I upgraded my SQL Server 2005 Standard Editon to Enterprise with MOSS without troubles.

Thanks  a lot :D:D:D
at 7/25/2008 5:01 AM

Re: Standalone server question

Thanks. Could you give more info about how to change app pool IDs to be able to import profiles?

YD
at 7/25/2008 10:35 AM

Is it possible to move one site collection to another web application?

Thanks.

YD
at 8/6/2008 12:26 PM

Re: Is it possible to move one site collection to another web application?

Sure.  The best (and only way that I know of) is to use STSADM to back the site collection up, then restore it to the other web application.  Use the 'backup' operation.  It will create a single file backup of your site collection.  Just make sure the web app you're restoring it to is at the same patch level as the source and that any Solutions, Features and Language packs are installed as well.

tk
Todd Klindt at 8/6/2008 1:38 PM

Re: Is it possible to move one site collection to another web application?

They are on the same server.
If several site collection are on the same web application, how to let them use different Content database?

Thanks.

YD
at 8/7/2008 7:48 AM

Re: Is it possible to move one site collection to another web application?

You can use the method in this blog post to move site collections from one content database to another, http://home.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=53

If you want to create new site collections in their own content database use the STSADM operation "createsiteinnewdb".  If you would like to create a new site collection in a specific existing site collection, use one of Gary Lapointe's commands, gl-createcontentdb, from http://stsadm.blogspot.com/2008/01/create-site-in-database.html.

You can't do this from the Central Admin UI, unfortunately.

tk
Todd Klindt at 8/7/2008 9:20 AM

Re: Is it possible to move one site collection to another web application?

Thanks so much.

YD
at 8/7/2008 11:25 AM

Re: Is it possible to move one site collection to another web application?

at 8/19/2008 3:30 PM

Re: Is it possible to move one site collection to another web application?

Sorry about that. I paste the wrong link.  Try this instead, http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=53 

tk
Todd Klindt at 8/19/2008 5:02 PM

Profile import from AD to standalone MOSS2007

Our Basic(not Advanced) Standalone SharePoint 2007 server is not in our domain. If I import user profiles from the AD to the SharePoint server, will the accouts from AD become local accounts or else?
Thanks.

YD
at 8/29/2008 1:00 PM

Error: Delete the timer job from the Timer Job Definitions page

When I try to backup my sharepoint 2007 farm from the Central Administration -->Jobe-->Backup, it gives above error message(It worked fine before).
After running stsadm -o enumssptimerjobs –title SSPNAME
I got the following job list:
SSP Timer Job Id="40c5b744-09a3-4ca9-9968-090f9d673540" Display Name="User Profile Change Job"
SSP Timer Job Id="c71f6146-2a8c-4ddf-90c5-31f0b6da922e" Display Name="Distribution List Import Job"
SSP Timer Job Id="e60c4577-724d-4c3e-b914-40537bac5854" Display Name="Audience Compilation Job"
SSP Timer Job Id="ec33af12-2994-45e6-b706-68edb5350ede" Display Name="User Profile Incremental Import Job"
SSP Timer Job Id="70d4a5d4-04c2-411c-86f8-80a3a4e09ba5" Display Name="User Profile Full Import Job"
SSP Timer Job Id="bd39ff86-b5b8-4c9c-a547-fb8c99468415" Display Name="User Profile Change Cleanup Job"

How can I know which is the one I need to delete.

Thanks.

YD
at 9/16/2008 9:31 AM

RE:Delete SharePoint Timer Jobs

I solved the problem.

Thanks.

YD.
at 9/16/2008 10:09 AM

Re: Error: Delete the timer job from the Timer Job Definitions page

Care to share the fix with the rest of the class?  :)

tk
Todd Klindt at 9/16/2008 10:06 PM

Muchas Gracisas

Hombre, escribiste lo que nececitaba....

merci from switzerland.

reto
at 12/11/2008 12:09 AM

Question

I may test this in our test environment...question though, I want to verify...this applies if you did a single-server, basic install...right?  We can still run it all on one server?
at 12/16/2008 3:26 PM

Re: Question

It will work if you did a Basic Install of MOSS, but not if you did a Basic install of WSS. And yes, you can still run it all on one server.

tk
Todd O. Klindt at 12/16/2008 11:32 PM

Another Thank You

Hey there,

Just wanted to say thanks for the instructions - saved me lots of time to do it right the first time.  Appreciate it.

-Randy in Oregon
at 1/14/2009 12:13 PM

Perfect!

Thanks! (Whew!)
at 1/15/2009 12:38 PM

WSS WID to SQL 2005

I have learned so much from your blog, thanks. Have you had a chance to look into more migrating from the WIS on WSS to SQL 2005 (on a remote server).

Thanks

Joshua in Kentucky
at 1/21/2009 1:04 PM

Re: WSS WID to SQL 2005

I haven't looked into this. Though the MDF and LDF files should be the same, so in theory you could stop the WID services, copy the files over to a full SQL server and attach them there.

tk
Todd Klindt at 1/24/2009 8:24 PM

Upload file problem

I konw this is not the right question for this topic, but you are the only one giving fast and helpful answer.
I tried to upload a 1GM mp4 file to my SharePoint site. I set the Maximum Upload Size to 2047MB, but it still failed(It works fine for small size file and the file type is not blocked). I select 'No Quota' for the Default Quota Template.

Anything else I need to check?

Thanks.
YD

at 1/28/2009 4:30 PM

Move all Sharepoint Databases from SQL Express to another "real" SQL 2005 server

We have installed and started to use a WSS 3.0 (not MOSS) server with SQL Express (lastest version) as config/content/search database server.

Now we have installed a "real" SQL 2005 database server that we want Sharepoint to use.

Is there a special procedure you have to use to move (and upgrade) all the databases, both config, content and search from a SQL Express database server to a SQL 2005 server or can you just assume that what MS describes in the following article is valid for this kind of move also: http://technet.microsoft.com/en-us/library/cc512723.aspx

My SQL Express is on the same server as the Sharepoint Front End server. My SQL 2005 server is on another server.

Jon Trygve in Norrway
at 1/30/2009 8:43 AM

Thnak You

Thank you very much for posting this. You save me and the client hours of fustration.
at 1/31/2009 11:06 AM

Re:Upload file problem

Solved the problem in the help of the link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;925083

Thaks.

YD
at 2/3/2009 12:59 PM

Upgrde question

I have SQL Server installed on my server.  However, when I open the console, I am getting a SQL Server Express Console. My Sharepoint content DBs are approx 30GB.  How can I get back the SQL Server Enterprise console?
at 2/26/2009 11:32 AM

Re: Upgrde question

You can have multiple instances of SQL installed on the same machine at the same time, including SQL Express and SQL Standard or Enterprise. In Enterprise Manager you need to connect to the non SQL Express instance on your box. Try just connecting to the machine name as the instance name.

tk
Todd O. Klindt at 2/26/2009 8:35 PM

Thanks

Solved our problem!  You saved me a lot of frustration.  The worst part is we purchased a 2005 Standard licensing but there were 2 instances of SQL and sharepoint was on on the Express version. 
at 3/30/2009 1:28 PM

Legend!

Thanks for this. great article.
at 3/30/2009 3:41 PM

Any reason to use WID?

I am planning a WSS 3.0 (not MOSS) Extranet Portal site.  Currently the dev work is being done using the out of box WID configuration.  What exact limitations will I hit with this rather than SQL Server Standard?  Does anyone go into production using the WID configuration? and if so is it really smart? 
at 3/30/2009 3:59 PM

Re: Any reason to use WID?

There is no reason to use WID. Well, there is one, but to use WID you have to do a Basic install and there's no way I'm going to tell someone in public to do that. If cost is an issue, use SQL Express, which is free. Get the version with the Management Studio built in. The only limitation SQL Express has that WID doesn't, is a 4 GB per database limit.

Don't do Basic installs. Don't use WID. It'll bite you in the butt down the road.

tk
Todd O. Klindt at 3/30/2009 4:33 PM

Todd, did you get a chance to look into my problem? Move all Sharepoint Databases from local SQL Express to another SQL 2005 server

We have installed and started to use a WSS 3.0 (not MOSS) server with SQL Express (lastest version) as config/content/search database server.

Now we have installed a full SQL 2005 database server (on another physical server) that we want Sharepoint to use both as content, search and config db.

Is there a special procedure you have to use to move (and upgrade) all the databases, both config, content and search from a SQL Express database server to another full SQL 2005 server that is not the same physical server or can you just assume that what MS describes in the following article is valid for this kind of move also: http://technet.microsoft.com/en-us/library/cc512723.aspx 

My SQL Express is on the same server as the Sharepoint Front End server. My SQL 2005 server is on another server.

Would really appreceate your answer.

Jon Trygve in Norway
at 4/2/2009 1:51 AM

Re: Todd, did you get a chance to look into my problem?

Hi Jon,
The TechNet article you linked should work. You can also read another approach here, http://stsadm.blogspot.com/2008/06/moving-databases-easy-way.html . Same basic steps.

tk
Todd O. Klindt at 4/7/2009 9:22 PM

How to bypass the 4gb DB size limit

I am looking to upgrade my MOSS 2007 SQL Express install to full SQL std 2005 or 2008 (not sure which one yet) but I was wondering if this will take care of the 4gb DB size limit? If not, do you have an article or post that you can point me to for review on how to upgrade?
at 4/15/2009 8:56 AM

Re: How to bypass the 4gb DB size limit

Yes, if you upgrade your SQL Express instance to SQL Standard it will remove the 4 GB limit.

tk
Todd O. Klindt at 4/15/2009 10:52 AM

Very basic question

How do I get to the command prompt? I'm a neophyte. I have a program with SQL 2005 Express and I want to upgrade to 2005 Standard. Thanks
IA
at 4/24/2009 6:03 PM

Re: Very basic question

Start > Run > cmd.exe or Command Prompt under Start > Programs > Accessories.

tk
Todd O. Klindt at 4/24/2009 10:11 PM

Document Libraries problem

I restored a sharepoint 2007 site collection to an existing sharepoint 2007 site under its /sites/. Everything seems fine, but when I clicked any Document Library link, it gave:
'An unexpected error has occurred.

Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator. '

Any advice?

Thanks.

yd
at 6/1/2009 3:49 PM

re:Document Libraries problem

It solved itself today. I really don't know what happened.

Thanks anyway.
yd
at 6/2/2009 9:36 AM

Is the above relevant to SQL2000 as well ?

hello,

I am looking to migrate my sps 3.0 ssee to an exisitng sql2000 database - is this possible along the lines of the above ?

Cheers
Gav
at 6/4/2009 3:36 AM

Re: Is the above relevant to SQL2000 as well ?

When you say "SSEE" that makes me think you've done a Basic Install of SharePoint. That throws a whole bunch of mess into this. You also mention "SPS 3.0" which doesn't exist. There is "SPS 2003" which is based on WSS v2 and there's "MOSS 2007" which is based on WSS v3. Without knowing which product you actually have I'm not sure what advice to give you.

tk
Todd O. Klindt at 6/4/2009 9:20 AM

Thanks so much!!!

My database size hit the limit, I couldnt free up enough to fix it...sps and hotfixes wouldn't install...site moves failed...good thing it was a vm i just kept going back to my checkpoint....this uprade will do the trick, would have saved me my sleep last night lol!

digitalmek
at 6/19/2009 3:31 PM

Re: Thanks so much!!!

Glad I could help. It's post like this (and the throngs of female groupies) that inspire me to keep doing this blog.

tk
Todd O. Klindt at 6/29/2009 4:07 PM

Thanks! :)

This is by far the clearest description of upgrading from SQL 2005 Express Edition. We had a DB that hit the 4GB limit and needed to upgrade asap - this made it very straightforward for me. I'm not a SQL Admin and didn't realise it could be upgraded (the SQL Admin is on hols...)

Absolutely spot on, many thanks!
at 7/28/2009 10:15 AM

Question

I have two sharepoint sites on a standalone server, one is like https://abc/ and the other is like https://efg:4443/. This morning I just found that https://abc/ works fine but https://efg:4443/ stops working.

What's the possible reason?

Thanks.

YD
at 8/13/2009 7:49 AM

Re: Question

I just figured out one nic card has problem.

Thanks anyway.

YD
at 8/13/2009 11:09 AM

Re: Question

YD,
Thanks for posting, and following up with the answer. :)

tk
Todd O. Klindt at 8/13/2009 10:03 PM

Later Version


Hi
I am trying to upgrade from 2005 express Advanced to 2005 Standard but get the following error. Is there anyway around this
"Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to."

G
at 8/18/2009 7:28 PM

Re: Later Version

I don't know what "2005 express Advanced" is. Are you referring to SQL 2005 Express with Advanced Services? If so, it should upgrade fine. It's just SQL 2005 Express with some management tools included. If you have it patched (like with SP2 or something) you might get this error. I'm not sure if SQL 2005 allows you to slipstream service packs into the install or not. That might be something to try. Or SQL 2008.

tk
Todd O. Klindt at 8/24/2009 1:44 PM

WID/SSEE Clarification and SQL to SQL moves

TK,

Thanks for this wonderful post on SQL Express, but I wanted to specify what I have found in regards to upgrading from SQL Server Embedded Edition (SSEE) aka ##SSEE aka Windows Internal Database (WID) (WIS if you're a typo artist.)

Microsoft has a great document on moving databases in WSS 3.0 http://technet.microsoft.com/en-us/library/cc512723.aspx(The guy earlier meant WSS 3.0 when he said SPS 3.0, it's a common misnomer on the web.)

Here's the real deal as it relates to SSEE/WID. In a typical non SSEE/WID environment, moving SQL 2005 to SQL 2005 on a different server requires a backup and restore of the data, an alias redirect, AND a transfer logins and passwords task.  MSFT provides us a nice query to do this (http://support.microsoft.com/kb/918992/) HOWEVER, that last part (transfer logins) is what eludes us in SSEE/WID. if you're running SSEE/WID, you cannot run this query against the database because it will create 2 stored procedures (sp_hexadecimal and sp_help_revlogin) in the database. Creating stored procedures in SSEE/WID is not allowed.  Those stored procedures would then be executed in yet another query and the results are a 3rd query to copy/paste and run on the new database server instance and will recreate the usernames and passwords.  Works great IF you're not using SSEE/WID.  Since you can't create stored procedures, none of this applies to us.

SSEE/WID is a prepackaged version on SQL Express but is quite simply an OEM SQL Express where only the vendor of the product using it can perform certain functions on the database.

If all you want to do is move the content databases ONLY in SSEE/WID, and not the config databases, this can be accomplished by following the TechNet doc found here: http://technet.microsoft.com/en-us/library/cc287738.aspx

I have not yet found a way to transfer logins from SSEE/WID since there is the cannot create stored procedure limitation, but I'm still trying.
at 8/25/2009 8:33 AM

Typo Artist

Ooops, Guess i'm a typo artist too.  The first link should have read:
http://support.microsoft.com/kb/918992/
at 8/25/2009 9:32 AM

Hi,

Thank you very much for this usefull information.
It has worked for me.
at 8/26/2009 4:07 AM

PowerShell

U the man. Thx for your help ;o)
at 8/28/2009 5:55 PM

Excellence

I really need it. Yaar thanxk you very much

Thanks
http://aspdotnetexample.blogspot.com
at 9/8/2009 8:08 AM

Help please

I'm had a MOSS install with SQL Express and I attempted to follow the steps in this guide to upgrade to SQL Server 2005 and all went well except for the following message:

Build version check:
Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

Everything else went smoothly. I thought that possibly everything was fine with the install but when I went to install SP2 it wouldn't let me check Database Services.

The ultimate issue I'm trying to resolve is that when I go into SharePoint Designer to create a data connection I'm unable to connect to the Database server. The only server I have is OfficeServers and I know that came from the SQL Express install.

I'm a SQL newb. I'm on a tight deadline and I've been working on this to no avail. I don't know what else to do.
at 9/18/2009 3:34 PM

Re: Help please

It sounds like you did a Basic Install, which is bad, bad, bad, for reasons just like this. You are correct that the Basic Install installed SQL Express and created the "OfficeServers" instance. I'm not sure what you're trying to point SPD at that you're aren't able to find in that instance. 100% of what SharePoint has put into SQL is there.

Your upgrade probably is likely becaus you've patched SQL Express past the RTM build of SQL 2005. I haven't done it myself, but it sounds like you need to slipstream SP2 or SP3 into your SQL install. Your other option is to uninstall SQL Express leaving the databases behind. Then install the full version of SQL 2005 or 2008 then adding your databases in. You could use a SQL alias to map your new install to your old instance name.

Good luck. Let me know what you end up doing.

tk
Todd O. Klindt at 9/19/2009 1:55 PM

SQL upgradation

We have insatllled sql express.We have 5 or 6 database. Now we are upgrading from sql express to sql enterprise. is it will effect our database after upgradation.we need to again restore databases?
at 9/25/2009 1:23 AM

SQL express Edition 4GB full

my Content database is fulled with 4GB its not allowing me to Upload any documents.in my portal due 4GB  full. so now i want to upgrade my express edtion to standard edition or entriprise edition,can i follow the above screen shots....

Thanks in Advance
at 10/21/2009 5:12 AM

fyi SQL Edition Upgrade for SQL 2008

Thank you very much for this helpful hint that i found via google while I was looking for a hint how to upgrade SQL Expres 2008 to Standard.

With SQL-Server 2008 there is a feature called "Edition Upgrade"
With "Edition Upgrade" you can upgrade to a different version of SQL-Server 2008.
Just insert the SQL Server installation media of your desired edition and choose "Edition Upgrade" in the Maintainance-Tab. Answer the wizard and choose the instance wich needs to be upgraded, drink some coffee and thats it

at 10/31/2009 2:40 PM

32 bit vs. 64 bit. Can I upgrade?

Todd,

Great tutorial by the way. I am relatively new to the server front. I have spent the last 15 years as a computer technician and due to client demands have had to move more and more into the realm of server installations and maintenance. So now you know I have a bit of history.

I have just finished successfully installing Server 2003 Enterprise SP2 - not updated yet --, Exchange 2007 SP1 - not configured yet -- and MOSS 2007 -- also not configured yet. When I finished the MOSS 2007 install I noticed it installed a 32 bt version of SQL Server 2055 Express. The Sharepoint Configuration Wizard completed and I have the SharePoint 3.0 Central Administration Console but I have not configured anything in it yet. I thought since everything else was at 64 bit in the system I may be able to bring SQL Serve 2005 Express  up to speed as well. Then I can continue to finish configuring the DC - which is working, AD -- I have 1 user in, me non-admin, and it's working, IIS -- tested and working, MOSS - after I figure out this SQL query, Security -- running default for a now, etc.. etc.. and finally read KB's till 3:00 AM every morning to finish all the required security updates to the system with out screwing it up or making it stop doing what it is supposed to do.

So without further ado here are my 2 questions for you:

1) Is it possible to upgrade SQL Server 2055 Express 32 bit to a SQL Server 2055 Enterprise 64 bit?

2) If number 1 is not possible can I upgrade SQL Server 2055 Express 32 bit to a 64 Bit version and if so, how?


Thanks

BJC
at 11/8/2009 11:14 PM

Thanks for your efforts

We used this method to upgrade our environemnt and it seems it was successful.  Thanks for posting this.
at 11/25/2009 4:24 PM

Upgrade to a remote server

Hi,
It seems like it only address if you want to upgrade the SQL version but what if I am upgrading the hardware as well to remote dedicated SQL or a clustered SQL server setup?

How can it be done?

chungwo@hotmail.com

Andy
at 12/10/2009 8:30 PM

Re: 32 bit vs. 64 bit. Can I upgrade?

Hey BJC,
I don't know if you can upgrade 32 bit SQL Express to 64 bit SQL Standard or Enterprise. If I had your environment I would at least give it a try. If not you can take your SQL Express databases and attach them to a 64 bit SQL instance. You could also leverage SQL aliases to make sure ShaerPoint points to the new instance, but with the old name.

tk
Todd O. Klindt at 12/11/2009 10:22 AM

Help with upgrade SQL2005 express to SQL2005 standard

Hey Todd,

I been reading your post on to use the septup.exe SKUUPGRADE=1. When I do this I get the following error
"your upgrade is blocked. For more information abou upgrade support see he 'Version and Editon Upgrade"
Build Version check:
Your upgrade is blokced becasuse the exisitng component is later version than the version you are trying to upgrade. modify and exisiting SQL Server component you would like to modify then click change/remove."

Help got any suggestions. The I have three database on this server and one of them has reached over 3.5, so I have upgrade to SQL2005. Any suggestions.

Thanks
SMM
at 2/7/2010 3:31 PM

Upgrade SQL2005 Express to SQL2005 standard using setup.exe SKUUPGRADE=1

What do you if you have more then one express DB installed.
I followed the steps. I have Mangement I have to use do he attach of the DB, but when I tired I still on see he GRH799/Express.

Went wrong.

SMM
at 2/7/2010 5:53 PM

Re: Upgrade SQL2005 Express to SQL2005 standard using setup.exe SKUUPGRADE=1

Is GRH799 the machine name? It's possible that "Express" is just in the SQL Instance name. When you ran setup did it ask you which instance you wanted to upgrade? If the SQL Express instance is named "GRH799\Express" it won't be renamed when it's upgraded. It will still have the name Express, but it will be Standard or Enterprise.

In Management Studio right click on the instance name and click Properties. The Product field will tell you which SQL Produc that instance is.

tk
Todd O. Klindt at 2/7/2010 6:01 PM

SQL Server 2005 express to SQL Server 2008 standard upgrade

Just curious, Is 'setup.exe skuupgrade=1' work for SQL Server 2005 express to SQL Server 2008 standard upgrade?
Anyone tried? and what message you get?

Thanks.
at 2/8/2010 5:28 AM

Re: Upgrade SQL2005 Express to SQL2005 standard using setup.exe SKUUPGRADE=1

On the server there are two instanaces of express. One called RE_Express and one called FE_Express While running the upgrade.  The only way at present to attach or detach the express db's is Management Console that comes with the application.

So the question is do I need to run setup.exe SKUUPGRADE=1 twice. Once for each instance. So it keeps the instance a it was before the upgrade.

You mentioned right on the instance in SQL Managment Studio, but I can only attach the db's the acutal Mangement that comes with the application. Should it still show.
Thanks
SMM
at 2/8/2010 6:17 PM

Re: Upgrade SQL2005 Express to SQL2005 standard using setup.exe SKUUPGRADE=1

You will have to upgrade each instance individually. SQL treats them all separately.

tk
Todd O. Klindt at 2/10/2010 8:22 AM

Re: SQL Server 2005 express to SQL Server 2008 standard upgrade

Haevn't tried to upgrade SQL 2005 Express to SQL 2008 Express. If anyone has tried it, please post here.

tk
Todd O. Klindt at 2/10/2010 8:24 AM

Microsoft do have information but irrelevant

Microsoft do have a information but some times irrelevant to what we are looking for.

Thanks buddy you saved my time.

Keep up the good work
at 2/24/2010 12:11 PM

SQL Express server 2005 to SQL Server 2005 Standard Upgrade

I upgraded SQL Express server 2005 to SQL Server 2005 Standard after two days.
at 2/28/2010 11:42 AM

Many thanks!

Many thanks for this extremely helpful information! :-)
at 3/2/2010 7:51 AM

need I install sql 2005 cd2?

hi, thank you, I followed yours guide, it works, no 4gb limited.
But in the installation, it didn't let me insert CD2. so should i run setup.exe in cd2?
at 3/2/2010 9:56 PM

SQL Express server 2005 to SQL Server 2008 Standard Upgrade

Could anyone please help me upgrading SQL Express server 2005 to SQL Server 2008 Standard?
at 3/9/2010 10:07 PM

Something strange

Every time when users try to open MS office Documents in MOSS, it asks username and password if they use IE. PDF files work fine and Firefox works fine.
It just happened recently, so I guess it relates to the IE version. Is there anyway it can be fixed on server site? I use a standalone server.

Thanks.

YD
at 3/10/2010 8:36 AM

Re: Something strange

Is your SharePoint site in the "Intranet" security zone in Internet Explorer? If not, set it there and see if that fixes it.

tk
Todd O. Klindt at 3/10/2010 11:58 AM

Re: need I install sql 2005 cd2?

The second CD has tools on it, so you won't need that just for the upgrade. If you run the install and install more components you might need that second CD. I won't expect you to need it doing this procedure.

tk
Todd O. Klindt at 3/10/2010 12:00 PM

Something strange

Every time when users try to open MS office Documents in MOSS, it asks username and password if they use IE. PDF files work fine and Firefox works fine.
It just happened recently, so I guess it relates to the IE version. Is there anyway it can be fixed on server site? I use a standalone server.

Thanks.

YD
at 3/10/2010 12:36 PM

Re: Something strange

Yes. It's in the trusted site. The problem is it didn't happen before.

YD
at 3/10/2010 12:38 PM

Thanks

Thank you very much for this information, it saved me a lot of headaches! :)
at 3/10/2010 9:06 PM

64bit 2008 upgrade

How do I upgrade 2008 Express (64bit) to Standard (64bit). I have tried the path recommended here and I receive an error on the feature upgrade.
at 3/15/2010 11:32 AM

Thanks

clear tutorial !
at 3/15/2010 9:50 PM

Another strange thing

I use a standalone server for SharePoint 2007. The server is not in the domain, so I created all the users locally. After changing several usernames today, I removed  and  re-load the users for the user group of their site, but it still shows the old usernames in the group. Though I use the new username to login, it still shows the old usename after login. I ran iisrest and restarted the aaaweb Application, but it still does the same thing. I think I may need to refresh some part of the SharePoint or reboot the server.

Any Advice?

Thanks.

YD
at 3/17/2010 1:36 PM

Installation of SQL Server Standard didn't install SSBIDS

Hi,

a customer of mine, was using SQL Express and needed to upgrade to Standard Edition to use Business Intelligence Development Studio.

I uninstalled Express edition and later installed Standard Edition with SP2, but when I tried to use BIDS it was never installed. What went wrong in my procedure? Should I uninstall Standard again and try using another procedure?

Please help me by sending me an email with your suggestion at crodriguez1974@gmail.com

Best Regards in advance,
Carlos
at 4/3/2010 8:29 PM

local and ad users

we have a standalone SharePoint 2007 server(not in domain). all users are local users. Right now we want to import user profiles from our AD. will the local user and the imported ad user conflict if they have the same name? Are they stored in different place?

Thanks.

YD
at 4/10/2010 12:58 PM

ad profiles import error

We just add our standalone SharePoint 2007 server to the domain. When I tried to import ad profiles into to ssp, it gave this error: "The specified account cannot be validated at corresponding domain controller.” .

Even though I used a domain account, login by using a domain account and changed the Windows SharePoint Services Timer service to a domain account, it still gave the same error.

Any advice?

Thanks

yd
at 4/12/2010 5:55 PM

RE: ad profiles import error

After battling for more than one days, I solved the problem through changing the 'Default Content Access Account' to a domain account by the help of this link.
http://technet.microsoft.com/en-us/library/cc261796.aspx

Thanks anyway.

YD
at 4/13/2010 2:35 PM

how to move database to NAS

Hi my setup is on a vmware with MOSS and sql express. However I will want to port all my database into a NAS set up. Will like to check how to point to a NAS . Is it even possible?

Raymond
at 4/27/2010 9:57 AM

Re: how to move database to NAS

SQL requires its databases be on local drives. If you can mount your NAS as a local drive (like via iSCSI) then you should be fine. SQL won't allow you to put your MDF or LDF files on a UNC like \\server\share.

tk
Todd O. Klindt at 4/28/2010 10:38 PM

Read every post...Now ready to Move Moss Express to Standalone SQK2k5

Wish me luck.  This was very helpful.  I've done lot's of WSS 3.0 Moves, but no MOSS 2007/Express.  I know that SP levels are KEY! 

Have to start by moving all to Test Environment first, then document all setps so the servers "guys" can move into production. 

Any last minute thoughts?

Thanks for your efforts, they are appreciated.

Jenny

Thanks
at 5/4/2010 10:05 PM

Re: Read every post...Now ready to Move Moss Express to Standalone SQK2k5

If you're moving SharePoint from one SQL server instance to another, you should also read Gary's blog post
http://stsadm.blogspot.com/2008/06/moving-databases-easy-way.html

It's a very good tutorial and might help you out.

Good luck,
tk
Todd O. Klindt at 5/4/2010 10:14 PM

Never get prompted for instance to upgrade

I can't get this upgrade to work. I'm never prompted for an instance to upgrade. Do you have any idea why? There is only one instance on the machine, is that why? It just goes all the way through, but everything appears to still be pointing to SQLEXPRESS and the Windows Service still passes the -sqlexpress parameter. Please help.
at 5/17/2010 1:38 AM

Re: Upgrade SQL Express to Standard or Enterprise

Very good!
at 6/1/2010 1:15 AM

Unable to upgrade from Express to Standard, please help

Hi there - great blog post!  I hope you can assist me with a issue I have.

we are trying to upgrade our Moss 2007 SQL Express 2005 to Standard 2005 but getting the error - Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

We tried upgrading SQL 2005 express to 2008 as well but it seems like you first need to upgrade it to SQL 2008 express and then that to standard.

My question is basically is that the easiest method for this issue or do you recommend anything else? Any help would be much appreciated! (PS: it is a production environment)
at 7/1/2010 8:15 PM

Re: Unable to upgrade from Express to Standard, please help

This normally happens because you've patched your SQL Express instance to something later than the RTM, and then you try to upgrade it to the RTM SQL Standard or Enterprise. Upgrading SQL Express to 2008 and then upgrading SQL Express 2008 to Standard or Enterprise might do the trick. I personally haven't tried it.

tk
Todd O. Klindt at 7/6/2010 10:17 PM

Add Comment
Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.

Title


Body *


Today's date *

Please enter today's date so I know you are a real person
Attachments