Last post Jul 24, 2017 08:09 AM by Deepak Panchal
Jul 23, 2017 07:59 PM|Bad Wolf|LINK
I have been using VS 2012 .NET C# MVC for apps that use generic ODBC connections to access remote Oracle datasources/databases for 2 1/2 years. I was just loaned a laptop from another client with an absolute mess of differing versions of SQL Server, Visual
Studio, & IIS/IIS Express (See included lists below). Aside from not being a SQL Server user for many years, I am wondering if these systems are stepping all over each other. I just need to create & manage a simple localhost database that I can create tables
on and have my data access objects talk to them using a simple ODBC Connection object. This is what I currently see on the machine:
I have .NET frameworks up through 4.6.1 and copies of VS 2012 Ultimate and VS 2013 Professional I would use for generating the project.
All I need to do for them is use Visual Studio Express 2012 and its matching Management Console, (I usually use TOAD or Embarcadero & don't have MS Mgt. Console experience). SQL Server Express 2012, (MS only offers d/l of 2013 & higher, but 2013 seems to
use 2012 MVC), IIS Express compatible
I'm at sea as to what to keep, what I should delete, and how they should be integrated. At this stage, the only dbs I use on the machine are MySQL and PostgreSQL,but they want to stick with MS all the way down the line.
Suggestions on what to delete or download are welcome as well as any help in how to register a new datasource & create a new database? I assume once I have the right MS Management Console, I'll be able to use SQL to Create Tables and define Columns in them
according to standard SQL Server commands.
This looks like the Gordian Knot to me - like they've just downloaded everything in sight and nothing is aware of any other component.
Jul 24, 2017 08:09 AM|Deepak Panchal|LINK
Hi Bad Wolf,
I can see there are many instances of SQL in the list.
try to check and also confirm with your client that how many of them are actually in use by the applications on that machine.
once you know about that you can try to take a proper backup of the database and then format this machine.
because if you try to remove it one by one then also you will not able to remove it properly and its creates more confusion.
so better to remove all and start with fresh OS and then you can only install that you are going to use.
if anything goes wrong and you want all back then you can recover it from the backup.
for more information you can refer link below.
Uninstall an Existing Instance of SQL Server (Setup)
Cleanly Uninstalling Stubborn SQL Server Components