I was trying to install SQL server 2008, but I couldn't manage to install SQL Management Studio, and I ended up going through the installation process 3 times before I got it installed properly, but now I have these extra instances of SQL Server installed that I don't need. I followed the instructions on MSDN but all that says to do is go through the Add/Remove programs, which uninstalls SQL server but doesn't remove the instances. Anyone know of a good way to get rid of the additional instances?
They appear as services, if you look through your registry to HKEY_LOCAL_MACHINE\CurrentControLSet\service there will be items for each instance. You can of course, just delete them. as SQL its self is still wanted, but the service just starts another copy with an instance name as a parameter. Eg sqlservr.exe -myInstance
Related
I was wondering if it is possible to create custom MySQL servers in VB.NET while working in visual studio at runtime so that if the server already exists it connects and if it isn't there, the code creates the server. I have searched for this everywhere but couldn't find anything. I would appreciate it a lot if someone guides me to the right path.
You could certainly write some .net code to start a MySQL server on your Windows box when an attempt to connect fails. You simply get a cmd.exe console with administrator privileges and give the command net start mysql.
But MySQL must already be installed on the box for that to work.
You might investigate Sqlite. It provides SQL locally to a .net program, storing your tables in a file called whatever.db. It has very similar .net API access to MySQL's Connector/Net and SQL Server's connector. It's in a NuGet package.
I don't completely understand your "custom MySQL servers" requirement. Sqlite gives you a way to use SQL in your application without connecting to a shared server. That may do what you need.
MySQL does have a CREATE SERVER statement in its SQL dialect. The purpose of this statement is to create a connection to another, remote, MySQL server. With that connection you can use the FEDERATED storage engine to access tables in the remote server. Of course, there is no way to run this CREATE SERVER statement unless your program is already connected to a MySQL server.
With respect, your "task which states to create a server at runtime" doesn't make much sense. Is there more to this requirement? What workflow needs this step? Is it part of the installation of some application software on a new box?
I'm trying to understand what is meant by a Server Instance in MySQL. Googling for the term "MySQL Server Instance" reveals nothing, and the only reference I can find in the documentation refers to using the New Server Instance Wizard, but doesn't seem to explain why I'd ever want to use this.
Coming from a Microsoft SQL Server background, a (named) instance is a completely separate and isolated installation of the server, running in its own process and on its own port. However, in MySQL a (server) instance seems to be a different beast, as for starters it seems to use the same port as my "existing" "instance".
From the Home page of MySQL Workbench, I have the option on the right hand side to create a New Server Instance. What is a MySQL Server Instance, and why would I ever want to create a new one?
A server instance is a MySQL server running somewhere, and also how to connect to it. See the reference manual, which says:
A server instance is created to provide a way of connecting to a server to be managed.
Though it is somewhat circular, it makes sense from configuring the control manager's connection options where one can choose to connect to any number of MySQL servers, or connect to the same server in several different ways (like through a VPN or secondary network).
From this it appears each instance actually does have its own port judging from this guide to setting up an additional instance:
http://www.ducea.com/2009/01/19/running-multiple-instances-of-mysql-on-the-same-machine/
I'm not sure how this interacts in terms of named pipes on Windows though.
I don't know if I'm searching for the wrong queries in google but I can't seem to find an answer to this. I have SQL Server 2008 installed in my pc and according to services.msc, I've got 2 database engines running: SQLEXPRESS (probably one that came along with Visual Studio) and MSSQLSERVER. When I try to connect only SQLEXPRESS is visible in the Server Name drop down list. I tried to explicitly state MSSQLSERVER by typing in
MYPCNAME\MSSQLSERVER
Didn't work. The best solution I could find in the internet was to enable stuff at Configuration Manager. Didn't work either (although I did find that TCP/VIA and all other options were disabled for MSSQLSERVER).
Anyone have any other ideas on what I should try next or probably something that I overlooked?
By default SQL Express installs itself as a named instance (\SQLExpress) so you need to specify that when connecting to it.
SQL Server doesn't do this (unless you tell it to during setup) so you connect to it with just the machine name.
I have done my best to install a copy of SQL Server 2008, but have discovered my "Reporting Services" installation has failed.
Furthermore, when I attempt to "repair" both the installation (and the "Shared Components" only, per a work-around I found here, will update with link if I find it) I have no had any success, as the SQL Server 2008 SP1 Patch reports that there are issues with my server's previous installation.
When I follow the procedure to complete uninstall SQL Server 2008 for a clean install (following instructions such as removing all components via the control panel "Uninstall") I also recieve errors, and when I attempt to re-run the installer I find that the instance I previously attempted to remove still exists: "MSSQL10" for example (see screen shot), and "RS" is listed as it's components, leading me to believe that the uninstall is failing because of this "RS" issue!
I have redownloaded the installer media, and tried to re-running it, and get the same issues when I choose a new name for an instances, and try "adding" features to the one I CANNOT seem uninstall! Any advice would be very helpful, my goal is to uninstall all instances of SQL Server 2008, start fresh, and apply the SP1 patch.
Thanks. I have attached log file, and screen shot. Computer information: Windows 7 Pro.
HP G60
Some error messages:
TITLE: SQL Server Setup failure.
Input string was not incorrect format.
I have pictures but not enough "reputation" to post them )-8
I experienced this problem as well - someone suggests it is corrupted Perfmon counters:
I found this ( http://social.technet.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/c9cb944d-6264-4530-9e00-ee92da3e939f/ ):
================================
Got this one figured out. The performance counters were corrupted. You can see this by opening perfmon and noticing a bunch of numbers instead of the actual counters themselves.
In order to fix (or you might want to check before you install), run:
c:\windows\system32\lodctr /R
This will reload the performance counters
This worked.
I have an existing multi-instance SQL 2008 cluster, and I'm trying to add Analysis Services to an existing instance. I start the installation, pick "Add features", configure SSAS, and then on the final pre-installation check, I fail the "Existing clustered or cluster-prepared instance" check. Of course I'd fail this check - I'm trying to add a feature to an existing clustered instance. Here's a picture of the error:
(source: trycatchfinally.net)
Has anybody successfully added a feature to a clustered instance in SQL 2008? I can't believe it can't be done - my alternative is to remove SQL from one node, try to add the feature again, hoping I don't fail this same check (though I probably will), and then re-add to the second node. This seems dangerous and unnecessary.
I found another person who had the same question, but the people answering it clearly aren't even reading the question, since they're mentioning how to cluster a server, and that he should use SQL 2000, so this is no help at all (though I'd love to point him here once it's answered: http://forums.techarena.in/software-development/1209984.htm
Take a look at the SQL Server 2008 Failover Clustering whitepaper.
http://download.microsoft.com/download/6/9/D/69D1FEA7-5B42-437A-B3BA-A4AD13E34EF6/SQLServer2008FailoverCluster.docx
Page 31 & 32
"Note: SQL Server 2008 does not support adding features to an existing failover cluster instance, so Analysis Services cannot be added to an existing instance of SQL Server. To share a resource group with an instance of SQL Server, you must choose to install Analysis Services during the initial installation of SQL Server."
Warning: I have never added analysis services to my existing cluster environment.
But this is how i would go about it:
1. Remove one node from cluster ( provided u have > 2 nodes ).
2. Install Analysis services.
3. Bring the node back into cluster.
Try to find necessary /skiprules parameter.
I have used the following setup SQL command to install SSRS feature with clustered instance:
Setup.exe
/SkipRules=StandaloneInstall_HasClusteredOrPreparedInstanceCheck
/Action=Install
The option to add or remove features is not supported either when running the setup through SQL Server Installation Center or when running the setup from a command prompt. For more information on the what happens when you try to add a feature through setup you can refer to the following forum post:
Why do I get ‘Rule “Existing clustered or clustered-prepared instance” failed’ error while adding new features to an existing instance of SQL Server Failover Cluster?
This article can be found here.
If you need to add or remove features to an existing installation you need to reinstall the virtual instance with the required features. For additional information you can refer to the following topics in SQL Server Books Online:
How to: Remove a SQL Server Failover Cluster Instance (Setup)
How to: Create a New SQL Server Failover Cluster (Setup)
Note: The SQL Server Analysis Services resource is a part of any SQL Server failover cluster’s resource group where Analysis Services is installed. Although it is possible to install both Database Engine and Analysis Services in the same resource group, it is generally recommended to install them as separate instances. Analysis Services is not dependent on SQL Server, and it should be installed to a separate resource group for maximum availability and performance.