Migration from SQL Server 2008 R2 Express to SQL Server 2008 R2 Developers Edition - sql-server-2008-r2

I've done some reading on the installation but it's not clear to me whether I will be UPGRADED to the SQL Server Developers edition or whether the install will create another instance. I want to get rid of SQL Server Express. Will the install give me that option?
If the install does not provide that option
What files must be deleted?
Are there any configuration items I need to gather before the install?
Anything else to be aware of?

You definitely can install a separate instance.
Don't even try to delete or replace sql server files manually - use standard windows instrumentation instead - uninstall it as regular application.
As far as I know - there were no any options to upgrade from express edt. to developer, if you need so - just keep your db in safe place, uninstall express, install developer, attach the db. And be aware of developer license restrictions!

Related

Umbraco via Nuget - how do I change the database?

I have installed Umbraco 7 via Nuget
Empty ASP.NET 4.5 project
Package Manager console command: install-package umbracocms
Build & run, following the Umbraco wizard
Looking in the web.config this is writing to the SQL Server CE database on my system which I definitely DO NOT WANT because of a known issue with Web Matrix / IIS Express and SQL CE
Link to known issue on Umbraco forums
How do I tell Umbraco to use my SQL Server 2012 Express database? Is it just the web.config that I change? Do I do this before building & running for the first time?
Build the project and run in (without debugging).
When you are asked to enter a username, email address and password do so.
Before hitting the green INSTALL button, click 'Custom'.
The custom install screen allows you to choose which database to install to. In my case I have two versions of SQL Server (2008 R2 and 2012 Express and the former I don't have admin rights to) but there is only one SQL Server option. I had to specify a custom connection string like so:
Data Source=APIWSEMMA\MYSQL2012;Initial Catalog=MyUmbraco;User ID=sa;Password=MyPassword
Now begin the installation. You should see all the tables created in your database when it is finished.

instance servername sql server 2012

Hello I have installed management studio 2005(x64) alse I have microsoft sql server 2012 in my pc. But cant connect server due to dont know server name. (if sql server 2008 express were in my pc, default servername would be "./sqlexpress")
How can I connect server in my own pc ? And also I wanted to know;
Should I use another management studio ? can there be a problem use ms2005 with sqlserver 2012 ? Do you recemmond other studio ? (with exp. reason please)
Thank you anyone who just feel to help.
At least one of them must be a named instance. So, open the SQL Server 2012 version of SQL Server Configuration Manager, and see what the services say (and make sure the one you want to connect to is started - you can right-click to do so). Mine are all named instances:
So, if I wanted to connect to the SQL Server 2008 SP3 instance, I would use any of the following to connect:
.\SQL2008SP3
LOCALHOST\SQL2008SP3
(local)\SQL2008SP3
YOURMACHINENAME\SQL2008SP3
127.0.0.1\SQL2008SP3
The exception is if the subtext has (MSSQLSERVER) - this is a default instance rather than a named instance. In that case you would just connect to YOURMACHINENAME or ..
Also, no, you should not use Management Studio 2005 to manage SQL Server 2012 instances. In fact I think the above Configuration Manager won't show your 2012 instance. So before you do anything, you should uninstall the 2005 version of Management Studio, and go get the 2012 SP2 version here:
http://www.microsoft.com/en-us/download/details.aspx?id=43351
Click Download, the file you want is SQLManagementStudio_x64_ENU.exe. The nice thing about this version in 2012 SP1 is that it's the first version of SSMS Express that is actually fully functional and license free. Previously you had to live with limitations like no SQL Server Agent management, well those restrictions are now all gone.
(When you instal the client tools, this should also give you a new version of Configuration Manager, if your previous installation of SQL Server 2012 did not provide that for some reason.)

Sql Server 2008 R2 Web setup throws application error when starting FixSqlRegistryKey_x86.exe

I have Windows 7 64bit. I had Sql Server 2008 R2 Express installed. I unistalled it and then I tried to install Sql Server 2008 R2 Web. Unfortunatelly on the Setup Support Rules page for 'Consistency validation for SQL Server registry keys' I got 'Failed'. I spent half of a day trying to solve it, but then I assumed that there must be realy something wrong with registry keys and it will be faster just to reinstall Windows.
After formatting the disk and reinstalling Windows 7, rebooting dozen of times I installed all Windows upadtes as well. I also did install some programs like Skype, Thundirbird etc. which has no influence on Sql Server setup.
And then I tried again to install Sql Server 2008 R2 Web. And again an error. A bit different one. Now when the setup is on the Setup Support Rules page I get an error message box with the title "FixSqlRegistryKey_x86 - Application Error" and content: The application was unable to start correctly (0xc000007b). Click OK to close the application. 'Consistency validation for SQL Server registry keys' gets 'Failed' status as well.
My team mate has exactly the same machine as mine. He had no problem with installation (he didnt even need to reinstall Windows).
I run the setup as administrator, from a local folder. I even tried to use the setup files copied from my team mate, for a case if my copy is corrupted. In the setup options I have chosen the 'x64' version.
Any ideas what can be the reason of the problem?
Problem solved.
Someone suggested to me that Web edition should not be installed on Win 7 (just on Windows Server). So perhaps installing a different version would work. My team mate perhaps succeeded acidentially - due to having sql server installed already in express edition... but it is just a guess.
Before I tried to install another edition of SqlServer, I downloaded 2008 Express version and I started the install. From the temporary folder created by the express edition I copied FixSqlRegistryKey_x86.exe file and I had overwritten the problematic file in the Web setup with this file.
I started the setup again. It passed the verification this time. But has crashed on a later point - setup unpacks the installation files to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 and runs from it. So I needed to again overwrite the problematic file in this location. Now the installation succeeded.

ZendServer CE - change database type?

I am using the trial version of the Zend Server edition. From all the videos/documentation supposedly you are able to change the database version from SQLITE to MySQL, but all I get when deploying an application on Zend Server is to set the Host, Database name, username and password?
Just install mysql on your system and use it. ZendServer does not care what database engine you use. When installing Zend Server it is supposed to ask if you want to install mysql (possibly you have to chose manual installation or custom or extra stuff) you might of mised that option so perhapds reinstalling is the simpler solution.
But really, you should be able to just install mysql and start using it.

Error when installing SQL Server 2012 Express

When I attempt to install SQL Server 2012 Express, I get an error
However, I have installed service pack 1. BTW, I am using windows 7.
Could someone help me?
My best guess is that you're trying to install 64bit Sql Server on 32bit Windows 7. Other than that, make sure you right click and choose "Run as Administrator" when starting the installer, and that your copy of Windows evaluates as "genuine".
Sql Server also requires .Net and PowerShell, but if either of those were the problem I would expect to see a different error, or even just a prompt to allow them to be included with this installation.