How can I remove these instances totally and install a fresh SQL. I have uninstalled everything linking to SQL in my machine, but these protocols are still here in my computer management(local). I used revo uninstaller to uninstall
Related
I am trying to install the Oracle SOA stack of products on my MacBook but I am stuck at one very crucial point. Need a database on my machine for OER but cannot figure out what to do?
Here is what I have already done:
Successfully installed Oracle SOA Suite 12c
I have downloaded OER
I have tried installing Oracle Database 12c, with Linux version even though as there is no download choice for Mac. I faced following error : ./runInstaller: line 252: /Users/madhu/Oracle/product/18.0.0/dbhome_1/install/.oui: cannot execute binary file
I checked supported database for OER but did not find MySQL or SQLlite or any other product than Oracle and Microsoft SQL server.
Microsoft SQL server is obviously not supported in MacOS
So at the as for OER a database is essential and I cannot install any supported database on MacBook.
Can you please help me?
Even if the installer script doesn't instantly fail, that doesn't mean that the Linux version of ODB 12c will magically work on OS X.
Install ODB or SQL Server on something else and configure OER to connect to it. That "something else" can be a virtual machine running on your Mac.
Install VirtualBox (or your preferred hypervisor);
Install Linux or Windows on a virtual machine;
Install and configure Oracle Database or SQL Server on that VM;
Consult the manual to configure networking for your virtual machine so the database is accessible from your host machine.
WebLogic will run on the Mac but FMW/SOA will not - at least not stable. Neither will the database.
& I know I teach/install/admin these products and am a certified Oracle trainer. I’ve tried...my time was worth more than it took to try and get it to work outside a vm-natively. I assume yours is too.
Unless you are actively trying to learn how to install them, then yes #backgammon is right, install them in a VM.
BUT, if you just want to use them and are not as interested in installation, then use one of the prebuilt -preconfigured FMW virtual box images here that will run on the Mac under virtual box.
Then Install OER in that image.
But, be advised OER is no longer sold by Oracle, even though it’s available for download.
It has been replaced by the API cloud service product.
I just upgraded my PC from Windows 7 to Windows 10. I did this because I need to upgrade SQL Server from 2014 to 2016 to match our production environment. I am unable to uninstall SQL Server 2014 due to a bug that seems to be due to SQL Server 2000 MSDE also being installed on my PC (I did not install this - can only assume it was bundled with some other software, maybe an old version of Visual Studio?)
The error message when attempting to uninstall SQL Server 2014 is:
SQL Server Setup has encountered the following error: '.', hexadecimal
value 0x00, is an invalid character. Line 1, position 212550. Error
code 0x84B10001.
The proposed fix for this issue is to uninstall MSDE. Unfortunately I cannot uninstall MSDE either. If I try to remove it via Control Panel, after clicking the UAC prompt, the dialog closes and nothing happens.
I found this page that claims to show how to remove MSDE manually if it won't install from Control Panel:
However none of this works either. The registry entries don't exist, so I cannot determine the product code from them, so I can't use MSIZAP.EXE. I managed to delete the files under Program Files as directed, and removed the registry entries for the services, but this does not fix the issue - Microsoft SQL Server Desktop Engine (SQL2000) is still list on Programs and Features on Control Panel, and I still can't uninstall SQL Server 2014.
I have attempted to install SSMS 17.3 only, but install fails with error code 0x80070643.
I think all I can do at this point is wipe my laptop and reinstall Windows 10 from scratch if I can't solve this.
There is the sql-cli utlity (installed with npm) which I am using to connect to various SQL Server machines. It works perfectly, however when connecting to localdb it responds with an error. So the next command line works:
mssql -s SomeServerAddress
But this one doesnt work:
mssql -s (localdb)\v11.0
And it responds with
\v11.0 was unexpected at this time.
Is there any special formatting for the server name to work?
Thanks.
its because (localdb)\v11.0 is not an actual instance as it can only be used inside visual studio.
"The localdb is at the heart of SSDT; it’s similar to SQL Server Express under the hood and runs a full version of sqlserver.exe. However this is throttled by the numbers of CPUs and limits on resources. There are quite a lot of limitations; you cannot upgrade the instance and there is no management and the sqlserver.exe does not run as a service. It is not similar to SQL Server Compact as this is feature-less (no stored procedures or functions) it is actually a DLL file that runs in a process from within Visual Studio, but is not available to task manager or windows. It is awakened when the SQL Server Native Client requests a connection from within Visual Studio. It doesn't stay online forever, it shuts down after time. You can configure where it creates the SQL files required to run. The localdb does not support table partitioning or data compression at the moment. However there are not many features that it does not support. You can however configure SSDT to use a full version of SQL Server i.e. the Developer edition, if your project requires unsupported features; by changing the Debug Connections tring in the projects properies." - Andrew J Fenna
This works:
mssql-cli -E -S (localdb)\mssqllocaldb
The -E is for integrated auth, the -S is the server.
If it does not connect, try to start localdb:
sqllocaldb start mssqllocaldb
This is all that is needed. No need to start Visual Studio or any other tool.
You may alreaady have gone on to bigger and better things, but
mssql -s "(localdb)\MSSQLLocalDB"
has worked for me.
Regards
I have a SQL Server 2005 64-bit cluster, and I need to import from a Progress DB frequently. I tried installing the Progress Openedge 10.0B driver on each VM in the cluster, but after I enter the serial number and CD key, select "Client networking", and click "Next", the setup freezes then has to be closed because of Not Responding.
Is there a standar way to deploy a driver like this to a cluster? I've already installed msdasql on both VMs, so I assumed it'd be a similar process. The openedge driver is 32-bit, but it's installed fine on a SQL server 2012 that was 64-bit.
If there's another way to easily transfer the data between SQL server and Progress/OpenEdge/QAD, please let me know.
Thanks!
Turns out the problem was trying to install the driver off a shared drive on a virtual machine. I had the same problem on other machines, and the only thing they had in common was the virtual machine status.
Once I copied the install files to each machine's local drive, everything installed fine.
Check to see if isdel.exe is running. If it is, kill it. It seems to be chicken soup for hung Progress installs.
I have a managed C++ application that connects to SQL Server 2005 Express databases on the same computer and over a network. My problem is that if the database is located on another computer over the network, the client machine will not have the needed DLLs files installed from SQL Server.
I can't force my users to install SQL Server 2005 Express on the client machine just to get the needed support files. So my question is, is it safe to installed the dependent files to the GAC on the user's computer? Or, does MS have a command line install package for just this purpose?
The files from SQL Server that my application show as being dependent on are as follows:
Microsoft.SqlServer.BatchParser
Microsoft.SqlServer.ConnectionInfo
Microsoft.SqlServer.RegSvrEnum
Microsoft.SqlServer.Replication
Microsoft.SqlServer.Rmo
Microsoft.SqlServer.ServiceBrokerEnum
Microsoft.SqlServer.Smo
Microsoft.SqlServer.SmoEnum
Microsoft.SqlServer.WmiEnum
If it helps, I'm using the Inno-Setup program for my installer. This has to be a common problem.
You dont have to install the full version of SQL Server, but you do need the necessary drivers. Installing the SQL 2008 SMO package on the client should resolve these issues.
http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en