May 27, 2015 at 7:34 am
This topic was discussed in other posts for different versions of SQL server but I saw no clear consensus so Ill ask in this forum.
We have an existing named instance of SQL 2012 Express. Can we install a full SQL 2012 instance, copy the databases from the SQL Express named instance to the Full instance name, and then delete (or rename the SQL Express version to something else), then rename the full version SQL server instance to the named instance one held by the SQL Express version?
The argument seems to be that you can use sp_dropserver and sp_addserver to rename a named instance. Apparently people have done it successfully.
Our reason for doing it this way would be to minimize downtime for our users. That and of course, we have lazy contractors who do not want to actually go into their application and point their application to a new instance name (heaven forbid!)
There apparently is no way to do an upgrade from SQL Express to full blown SQL. or is the software lying to me?
May 27, 2015 at 7:41 am
I believe you can do an in place upgrade from SQL express, but you have tio keep the named instance, which in your case would not be a problem. One such article
http://blog.fpweb.net/sql-express-to-sql-server-standard-in-place-upgrade/
May 27, 2015 at 7:44 am
I would seriously consider warning those contractors that you're getting ready to execute sp_drop_contractor. :w00t:
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
May 27, 2015 at 7:49 am
Alvin Ramard (5/27/2015)
I would seriously consider warning those contractors that you're getting ready to execute sp_drop_contractor. :w00t:
That would be a great SP!
Another link re upgrading
May 27, 2015 at 8:10 am
Huh, I tried running the upgrade(Express to Full) from the install disk like he said in the article, and I got the message that "there is no upgrade path from SQL Express to this version of SQL server" - I thought this would be the only way to get there. I havent checked the Express version to be sure its 2012. Perhaps its a 2008 edition. That would make sense. You have to be able to upgrade from Express to Standard right?
Love the SP_Drop_Contractor idea. Can you send me the code? 😀
Unfortunately I'm also a contractor - but have had this client for about 10 years.
May 27, 2015 at 8:15 am
you cannot rename a named instance.
Here are the supported upgrade paths for sql server versions
https://msdn.microsoft.com/en-us/library/ms143393(v=sql.110).aspx
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 27, 2015 at 8:36 am
Dimbulbz (5/27/2015)
Huh, I tried running the upgrade(Express to Full) from the install disk like he said in the article, and I got the message that "there is no upgrade path from SQL Express to this version of SQL server" - I thought this would be the only way to get there. I havent checked the Express version to be sure its 2012. Perhaps its a 2008 edition. That would make sense. You have to be able to upgrade from Express to Standard right?Love the SP_Drop_Contractor idea. Can you send me the code? 😀
Unfortunately I'm also a contractor - but have had this client for about 10 years.
I'm a contractor too. Sorry, but I haven't written that SP yet. 😉
Pointing a well designed app to a new data source should be so easy. You should be able to just edit the config data and update the source server and/or database name(s). I guess not all apps are well designed. 🙁
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
May 27, 2015 at 9:01 am
Alvin Ramard (5/27/2015)
Pointing a well designed app to a new data source should be so easy. You should be able to just edit the config data and update the source server and/or database name(s). I guess not all apps are well designed. 🙁
Yes, you would think it would be easy. Just replace the contractors with people who don't see it as brain surgery and rocket science combined. Its maddening :w00t:
As far as renaming a named instance, that seems to be up in the air - or is it? I get opposing posts saying its not possible, and others saying they've done it. I guess I'll just have to try it myself. In my case renaming would be just to get the Express version out of the way. If there are entries in the registry, they would not change, but that may be OK because the new instance could in theory use the existing entries.. possibly... Maybe not. I will have to update y'all once we give it a shot.
May 27, 2015 at 9:41 am
it is not possible or even supported to rename a named instance. The only name you can change is the computername. For instance, a named instance BLOGGS on computer FRED would be
FRED\BLOGGS
You could change the computername to JOE which would produce
JOE\BLOGGS
You cannot change the instance name BLOGGS to SMITH, not with out installing a new instance named SMITH and migrating objects to it, you have been warned!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 29, 2015 at 2:37 pm
For certain... Yes, I actually tried it and you cannot rename a named instance of SQL and have it work. (sometimes you just have to do things yourself, or you don't know for sure):crazy:
June 1, 2015 at 7:22 am
What about creating an alias on the new instance name?
Whenever the old connection string is used, it can be diverted to the new name?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply