Is it possible to rename a SQL Server 2008 Express installation? - sql-server-2008-express

I am attempting to install (and un-install and re-install numerously) SQL Server 2008 Express. I selected install as a default instance but the setup insists that my installation be a named instance localhost\sqlexpress.
Has anyone else had this issue?

You cannot rename it after it is installed. Additionally, if you are using WPI you must install with default options. Are you using WPI or did you get your installer from the Download Center?
From MSDN:
Specifying an Instance Name other than SQLEXPRESS
SQL Server 2008 Express uses the default instance name of “SQLEXPRESS”. Changing the instance name or installing additional instances requires a custom installation. You cannot change instance names once the installation is complete

Related

Blue Prism, regarding SqlServerExpress

I have two set up files for SQLServer
SQLServer2017-SSEI-Expr 5Mb
SSMS-Setup-ENU 540 Mb
Which file need to be installed.
If the setup file need to be installed then what is the use for the first one?
can someone please advice?
Thanks
SQLServer2017-SSEI-Expr is an installation package for installation of SQL Server Express binaries required to run the database server. You must install it to have your server.
SSMS-Setup-ENU is an installation package for GUI client which allows you to connect to SQL Server database instance and manage it. Although it's not required to be installed on the machine with running SQL Server it's recommended to be installed on administration/developer machine to interact with the database using T-SQL.

How do I uninstall and completely reset all data from SQL Management Studio?

I have tried uninstalling every SQL related program on my computer and the management studio itself, but when I re-install I get the same databases and data.
I just want a fresh install as if I had never touched it. Is this possible?
My Version: 17.9
You must uninstall the instances that you have on your pc.
Uninstall an Existing Instance of SQL Server and Steps to remove SQL Server 2016 Instance

Using SMO with VS2013 Windows Desktop application project

I am building a VB.NET application in VS2013 that uses a database created in SQL Server 2012 (which is installed locally and on the only computer that the application will be run on).
I need to execute a SQL script when the user clicks on a button. I know that I need to Import resources from SMO but when I run the SharedManagementObjects.msi installer I get a message that says,
"Installation of Microsoft SQL Server 2012 Management Objects failed
because a higher version already exists on the machine. To proceed,
uninstall the higher version and then run Microsoft SQL Server 2012
Management Objects Setup again."
What do I need to do to get SMO installed to use in my project?
I am assuming you are using nuget??
It appears that you must have 2014 installed, search for this in your installed packages and click uninstall. Now try and install the 2012 version.
Or in the Package Manager Console:
Uninstall-Package Unofficial.Microsoft.SQLServer.SMO.2014
Followed by:
Install-Package Unofficial.Microsoft.SQLServer.SMO
http://www.nuget.org/packages/Unofficial.Microsoft.SQLServer.SMO.2014/

Installing SqlServer 2005 Express using InstallShield and creating a unique named instance

I'm using Installshield 2008 express to create an installation package. My application relies on Sql Server 2005 express edition. I know I am able to check the "microsoft sql server 2005 express" prerequisite under the redistributables tab. However, this leaves the installation entirely in the hands of the end user, and if he/she chooses the defaults all the way through, we end up with a installation with the named instance SqlExpress. At the very least, I'd like to have the installation proceed with a MyCompany named instance as the default.
How do I accomplish this?
Do I have to upgrade to a more powerful version of installshield?
If the express addition supports install script you can use the following bit of code. You need to include the Sql Express redist in your install somewhere
LaunchAppAndWait(SRCDIR+"\SQLEXPR32.EXE",
"INSTANCENAME="+ instName +
" SECURITYMODE=SQL " +
"DISABLENETWORKPROTOCOLS=0 SQLAUTOSTART=1 ADDLOCAL=SQL_Data_Files SAPWD=" +
sapass /qb" ,
LAAW_OPTION_WAIT);
In the above code instName is the name of the instance. If you are using Windows Authentication only you can ommit the secuirty and password options.
Check the MSDN docs for other command line options
I sure this could be ported to VB or could even use one of the built in MSI action types
I have not used InstallShield Express. InstallShield Professional allows you to define the command line that is passed to the SQL Server installation. This allows you to define an instance name along with other parameters such as 'quiet' mode.

Replacing SQL Server 2005 Express Management Studio with the full version

I have been running SQL Server 2005 Express Management Studio ("SSMSE"), and I now have a need to install the full version of Management Studio ("SSMS"). This is a known hassle, but I've not found a comprehensive way to carry it out.
At first, I uninstalled SSMSE, and then ran SqlRun_Tools.msi to install the toolset. I got this error message:
A component that you have specified in the ADD_LOCAL property is already
installed. To upgrade the existing component, refer to the template.ini
and set the UPGRADE property to the name of the component.
I had no idea what template.ini was. So I looked around, and decided to uninstall the rest of the minimal installation of SQL Server 2005 Express on my computer by following Microsoft's advice in KB 909967, "How to uninstall an instance of SQL Server 2005 manually." That bit was very successful.
But when I attempted to run SqlRun_Tools.msi again, I faced this mess when the installer was "Preparing Installation Wizard":
The setup has encountered an unexpected error in datastore. The action
is SetDialogs. The error is : Source File Name:
...\datastorecachexmlschema.cpp
**** Compiler Timestamp: Fri Jul 29 01:13:50 2005
**** Function Name: DataStoreCacheXMLSchema::initScopeRecord*****Sour...
(but replace the asterisks with box chars, which were probably CR-LF's in the original message)
This is very frustrating. Does anybody have any advice for installing the full version of SSMS over top of SSMSE? Any help you can provide would be greatly appreciated!
I have also installed SQL Management Studio before just using the SqlRun_Tools.msi package without any problems but I think if you have previously had any other SQL Server 2005 components installed then you will need to install the Setup Support Files first as this is probably what sets up the component installation sequence. This can be done either by installing from the SQL Server installation media or by running the sqlsupport.msi file as described in the Microsoft KB article.
I resolve this problem
Steps
Go to Add\remove program
unstall SQL server browser
Install support files from CD
Install SQL_Tools.MSI
Well, I roughly found out what the problem was, based on a somewhat cryptic resolution mentioned across a few different forums. This solution suggested that I needed to install Setup Support Files. Maybe it was reinstall, since I removed something with the same name when uninstalling SQL2K5 Express. I'm not sure if they were the same files, between the full version and the Express Edition.
I had tried reinstalling SQLXML4, the Native Client, and MSXML6 just to see if I could get beyond the error involving datastorecachexmlschema.cpp, and each time, I got the same error again. But I tried the technique mentioned in the above link, and it worked perfectly.
Basically, you insert the CD and run just the first part of the installation process, which installs the installation tools, including Setup Support Files. Then you cancel the rest of the installation process, and run SqlRun_Tools.msi instead.
I got great results when upgrading 2008 express to 2008 developer by (running setup) first going to Maintenance->Upgrade Edition, and then (since Management Tools etc was still "express" and I mainly needed the Sql Profiler) I also did a complete "new" installation (Installation->"New installation or add features.."), selecting the existing instance and then selecting all features.
No uninstall or command line necessary.
Behaved the same afterwards, just with new features.