I Uninstalled SQL Server Express 2012 from my PC. But after that, I noticed that there were other things at Programs and Features, like "Microsoft SQL Server Native Client", "Microsoft SQL Server 2012 Native Client", "SQL Server Browser for SQL Server 2012" and another programs.
What can I uninstall from my PC to completely remove SQL Server 2012, without having problems with my Windows system?
Honestly, Microsoft software is a pain to uninstall.
None of those things will uninstall eachother.
What I personally use for such an occasion is the IOBit uninstaller portable
http://portableapps.com/apps/utilities/iobit_uninstaller_portable
It lets me remove all of them at once.
Note the following important scenarios before you uninstall SQL
Server:
Before you remove SQL Server components from a computer that has the minimum required amount of physical memory, make sure that the
page file size is sufficient. The page file size must be equal to two
times the amount of physical memory. Insufficient virtual memory can
cause an incomplete removal of SQL Server.
If you have multiple instances of SQL Server, the SQL Server Browser uninstalls automatically when the last instance of SQL Server
2016 is uninstalled.
If you want to uninstall all components of SQL Server 2016, you must
uninstall the SQL Server Browser component manually from Programs and
Features in Control Panel.
Also note that,
Before You Uninstall:
Delete the local security groups. Before you uninstall SQL Server, delete the local security groups for SQL Server components.
Stop all SQL Server services. We recommend that you stop all SQL Server services before you uninstall SQL Server components. Active
connections can prevent successful uninstallation.
Use an account that has the appropriate permissions. Log on to the server by using the SQL Server service account or by using an account
that has equivalent permissions. For example, you can log on to the
server by using an account that is a member of the local
Administrators group.
Documentation: MSDN - Uninstall an Existing Instance of SQL Server
Related
can vb.net connect to MDF file without SQL Server installation
I want to install this application to client machine without installing sql server
I am fairly certain that the closest you can get to what are asking for is to use LocalDB -- which is available as an install option with SQL Server Express installation media.
LocalDB by itself should be sufficient to allow your app to connect to and query the MDF file.
LocalDB represents the lightest, most-minimal install that you could choose for your scenario.
The docs describe what I am talking about in this way:
LocalDB installation copies a minimal set of files necessary to start
the SQL Server Database Engine. Once LocalDB is installed, you can
initiate a connection using a special connection string.
When connecting, the necessary SQL Server infrastructure is automatically
created and started, enabling the application to use the database
without complex configuration tasks. Developer Tools can provide
developers with a SQL Server Database Engine that lets them write and
test Transact-SQL code without having to manage a full server instance
of SQL Server.
I installed SQL Server 2017 Express as a named Instance alongside my default instance. After rebooting once - both were showing but the I could not connect to SQL Server Express remotely. I then followed the instructions to enable IP on SQL Express using configuration manager and rebooted. Now I can connect remotely but my default instance is showing NO databases!
Also in configuration manager, SQL Server Services does not show any of my instances so that I can check they are running (this was the care even prior to enabling the IP address on the protocol, and when I knew it definitely was running as I could connect to it)
--
Update:
I discovered if I launch SQL Server Configuration Manager 2016 rather than "SQL Server Configuration Manager" I can see all my servers.
SQL Server 2016 appears to be running as is SQL Server Express. There is also a "MSSQLServer" that is stopped - think this may be SQL Server 2012. Not sure at this stage which one had the databases.
Ok so for anyone in a similar situation / panic. Do the following.
Look to see what other SQL Server configuration mangers are showing up. If you have installed multiple versions over the years chances are you'll see more than one.
Try using one of the later ones. You can see the file path too if you need it here.
If you manage to see a list of your database servers, check which are enabled and disabled. I had to disable SQL Server (SQLExpress) first before I could enable SQL Server (MSSQLServer), which in my case referred to SQL Server 2012.
If you want to have SQL Server Express running as a named server running alongside your default server, make sure you assign it a different port number (e.g. 1435) in the SQL Server Network Configuration>Protocols for SQL Express>TCP/IPALL section in SQL Server configuration manager.
I need to deploy a WCF service with a database on client machines. I am confused about SQL Server Express. I need to verify all of the following.
When attaching database files in the App_Data folder, do I still need to install SQL Server Express engine (Windows service) on client machines?
There is a flavor called SQL Server Express LocalDb. That one does not need an engine (Windows service)? But I think it need a prerequisite installation of LocalDb.
Localdb is introduced with SQL Server 2012. There is NO localdb for SQL Server 2008. Correct? I could not find 2008 version on MS site.
Do I still need to install SQL Server Express engine (A win Service)
on client machines?
Yes, they need it installed for your application to query the database. Can't really get around it.
There is a flavor called SQL Express localDb. That one does not need
an engine (win service)? but I think it need a perquisite installation
of localdb.
Yes, you'd still need to install LocalDB on the client machine. It's pretty hassle-free to do, but I think it's overkill unless you really need the full features of a SQL Server instance for your webservice.
Instead of LocalDB I'd strongly recommend using SQL Server Compact Edition - it performs the role you're thinking of (your WCF Service can simply connect directly to the database file on your client machines without installing SQL Server, and is lightweight), but doesn't need to be installed (it's simply included as a DLL with your WCF application):
Unlike other editions of Microsoft SQL Server, SQL CE runs
in-process with the application which is hosting it.
In Microsoft's own words on the differences between LocalDB and SQLCE:
LocalDB and SQL Server Compact?
Small and simple database, lightweight installation, connecting to a
database file -- this will sound familiar to any developer using SQL
Server Compact. The similarities are not accidental, as our goal for
LocalDB was to be as easy to use as SQL Server Compact (while being as
powerful and compatible with full SQL Server as SQL Express).
There are significant differences between LocalDB and SQL Server
Compact:
Execution mode: SQL Server Compact is an in-proc DLL, while LocalDB runs as a separate process.
SQL Server CE is kind of like an updated version of MS Access, the file goes with the application which can "just connect" to the database file without involving any database server installation, and its syntax/features are very close to SQL Server standard.
I'm trying to connect a local SQL Server database to an ETL utility called Pentaho. Pentaho very easily connects to full versions of SQL server without issue.
I've set mixed mode authentication and created a sql server account for the sql server express instance that can be used to login through SSMS.
When I try to log in via Pentaho, I get errors about it not knowing what the server is, or the server not responding. I've tried {localhost, myip, localhost\SQLEXPRESS, myip\SQLEXPRESS, just SQLEXPRESS} as the server name (and SQLEXPRESS is the instance name).
I know I've had trouble connecting other programs to SQLEXPRESS databases in the past. Can someone tell me why it acts different than when using a full install of SQL Server and how I can get around these differences?
If SQL Server Express is on a different server, have you enabled TCP/IP protocol?
I cannot get my local computer to run SQL Server. I looked in the SQL Server configuration manager and noticed that there are no SQL Server Services listed. That can't be right. I also noticed that There are two Managers listed in the SysWOW64 folder (I'm running Win7): SQLServerManager10.msc and SQLServerManager.msc. Neither show any services at all. When trying to connect via SSMSE, I get the standard:
A network related or instance specific error occurred while establishing a
connection to SQL server...
I haven't installed a prior version, but did try to uninstall and reinstall using the Web platform installer from Microsoft. Any suggestions?
Thanks
I had the same problem and as Brian said, I was missing SQL Server Express. So I download SQL Server 2008 R2 Express and I installed it. now everything works fine.
Note that I thought I already installed it when I installed SQL Management Studio R2. Now, be aware that when installing SQL Management Studio R2, you are not installing SQL Server and you won't get any SQL Server Services in your Sql Server Configuration Manager -> SQL Server Services. You also need to download and install SQL Server Express.
Is SQL Server listed in services? (Start->Run->Services.msc)
If so, is it running?
That is an instance error, meaning you cannot connect to the instance. Most likely there is no instance installed on this machine. Meaning your not connecting correctly to the instance. Connect to the database engine again and check the server name and make sure your connecting to the correct server name or the local host, depending if this is a local machine or if this is on a server. Go back through setup and see if there are any features that didn't get installed. Try that and see if it works. If not then reinstall SQL Server and make sure all folders are removed and nothing is left behind before you reinstall.