Installing SP2 for SQL Server 2008 R2 Express - sql

I need to upgrade SQL Server 2008 R2 Express from SP1 to SP2. Select ##Version reveals 10.50.2500.0
I've downloaded what I think is the correct package but when I try to install I'm prompted to install a new instance or upgrade an existing instance. Choosing the 2nd option eventually gets me to the point of choosing Mixed Mode or Windows Authentication. I know what that is, but, why is it asking me this? I do not want to change ANYTHING about my environment other than installing the Service Pack, including authentication mode, or the password of the SA account, etc.
Am I doing something wrong?

You probably downloaded SQL Server 2008 R2 Express with Service Pack 2 (emphasis mine), from here. This is actually an installer to install an Express instance, not the service pack. The distinction is subtle, but it's important.
Download the Service Pack 2 package independently from here:
http://www.microsoft.com/en-us/download/details.aspx?id=30437
You'll want one of these files, depending on whether your machine (or Express instance) is x86 or x64:
SQLServer2008R2SP2-KB2630458-x64-ENU.exe
SQLServer2008R2SP2-KB2630458-x86-ENU.exe
Running this installer should allow you to select your Express instance as a target of the service pack without offering you options to install a new instance or upgrade an existing instance.
While you're at it, you'll also want to download and install SP2 CU#8:
http://support.microsoft.com/kb/2871401

Related

Error installing Accelerator for HL7. Installation cannot be performed because user account is not a member of Biztalk Server Administrators group

Please consider the following error when trying to run the HL7 Accelerator Setup.exe executable.
I'm installing on a Windows Server 2012 R2 VM.
BizTalk 2013 is already installed and configured successfully using Global domain groups for BizTalk Server Administrators (and all other groups for that matter). I am a part of all groups.
SQL Server 2012 SP3 was installed prior to BizTalk
When I go to run the HL7 Accelerator MSI, I get the error pictured above, which states:
Error: Installation cannot be performed because the BizTalk server has not been configured or user account is not a member of the BizTalk Server Administrators group
Like I said, BizTalk is configured, the groups are Global and I'm a member, I'm also a local admin on the machine.
I've also tried this altered MSI from this post to no avail, I get the same error.
I'm at a loss. I can't find anything anywhere explicitly saying that any of these versions are incompatible, and I know SQL Server 2012 SP1 is compatible based on other installations we have running.
Could it be something with Windows Server 2012 R2? I don't know how I'd get this far and not be allowed to install the accelerator of all things.

Is this important to install sql server with an windows application set up

I have developed a application in c# which is windows based application. It stores data into database sql server. I want to know, when I create setup in VS and install it in a client computer should I install sql server software also or Is there any way without installing SQL Server in client's PC My application can function correctly.
sIf you use a filebased implementaion of SQL (localDB) you should be able to get away with a "setup" installing the neccecary dependencies to bootstrap the DB. (Someone correct me?)
If you use the DB in a hosted SQL environment (SQL Server running as a service), you will need to install SQL server on the deployed pc, and get the database up.
I am no sure if you can "automate" installing SQL server and getting the DB up from a setup app.
You have two deployment options for applications that contain SQL Server Compact 3.5 databases. The method of deployment you choose depends on the servicing requirements of your application and whether your users will need administrative credentials on the computer on which the application will be installed.
Following are the deployment options for SQL Server Compact 3.5 databases:
1. Traditional Microsoft Windows Installer (Microsoft setup technology)
a. Users need administrative credentials to install the application.
b. SQL Server Compact 3.5 will be serviced by Microsoft Update.
c. Can use ClickOnce deployment.
-or-
Private file–based deployment (deploying the SQL Server Compact 3.5 DLLs as part of the project)
1. Users do not need administrative credentials to install the application.
2. SQL Server Compact 3.5 will not be serviced by Microsoft Update.
3. Can also use ClickOnce deployment.

sql server agent start disabled (grayed out)

I've just built a new dev machine and I can't get SQL Server Agent working. What I've done so far:
Install VS 2010 (I think this installed an express version of SQL Server)
Install SQL Server 2008 R2 Developer edition.
I'm not sure if I did something wrong in step 2. All I want is a fully working version of SQL Server with SQL Server Agent running and no limitation on the amount of data I can store (I will need more than 10GB).
Currently, in SSMS I have the following instance: ./SQLEXPRESS. I thought that during step 2, this would have been upgraded, but it doesn't seem so.
Can anyone help?
Note: I ended up resolving this by uninstalling everything that had "SQL Server" in it in Control Panel > Programs and Features. I then reinstalled from scratch.
Note: I ended up resolving this by uninstalling everything that had "SQL Server" in it in Control Panel > Programs and Features. I then reinstalled from scratch.
The agent account is disabled. If you aren't able to enable it through configuration manager, try enabling it through services. After its enabled, try starting the serivce. If you still have issues starting the agent, try changing the account the service is running under. There may also be an issue with the account that the SQL Server service is running under. Trying changing the SQL Server service account and restarting it. The agent should then start up successfully.
You have two installations, with two named instances. The Express named SQLEXPRESS and the developer edition named MSSQLSERVER (unless you changed this during install). connect to .\MSSQLSERVER and see, it should be there available to be started.
SQL Server Express does not ship with the SQL Server Agent.

Can SQL 2008 R2 and a SQL express installation coexist on same machine without problems?

I have SQL 2008 R2 on my computer and it works fine with the database. If I install Visual Web Developer 2010 express it says I have to install SQL Express , per it is a dependency. I would prefer to only install web developer.
Will an express installation effect my current installation's operation at all?
Yes they can coexist as they will be installed as separate services - see this forum post
Officially, they can coexist.
Unofficially, my experience with a joint installation is painful. SQL Server patches would fail mysteriously on machines with a joint install. Sometimes you could find fix information in a KB article, sometimes not. Sometimes reinstalling SQL Server worked, sometimes an OS reinstall was required.
You can take the risk on a development server, but I wouldn't do this in production.

How to install Bug Tracker .Net tool software in my System?

I have installed ASP .NET 2.0 MVC3, SQL server express 2005 and SQL server Management studio express 2005 and IIS 7 in my system. If I am opening the install_btnet file, and providing the SQL server details also it is not getting connect. It is giving error as Service unavailable. Any one suggest me how to install Bug tracker .NET tool in my system with examples.
Thank you.
First thing to check it that your SQL 2005 express instance is running and allowing remote connections. Open the Administrative Tools >> Services and look for the service called "MSSQLSERVER$SQLEXPRESS" and ensure it is started.
Next, open the SqlServer Configuration Utility (on the server or PC where SQL 2005 Express is Installed) Look for the Client Configuration Option and Select "Client Protocols".
Set TCP/IP to "Enabled" and you should now be able to connect to your SQL server.
Note that even if your BugTracker.NET install is on the same machine, it may still be using the network to connect to your SQL Instance.
Hope this helps,
Dave