I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
Hi,
I have 2 W2K box's and want to install 4 SQL servers on each box & each different character set and want to setup clustering (Active - passive).
Do any one of you setup this type environment ?, Pl. let me know if you have any suggestions ..
Regards,
Madhu
We have 5 instances on our clients old machine with SQL 2005, now they want us to move on cluster environment with SQL 2012.
Once I have installed and configured SQL cluster with single instance, but how to install SQL Cluster environment for Multiple instances.
Should I install all the instances first and than have to configure cluster ?
OR
Is there any way that first I will install cluster and than we can add the instances ?
What I have- Sql server 2012 (Standard Ed) Cluster on Windows 2012 R2 with both instances running on the same node- just to save on License, i.e. technically it’s Act/Pas cluster.
What I am looking for- how to configure cluster (e.g. via quorum, etc) to force both instances failed together? Means if for some reason 1-st instance will fail to node 2 another instance should follow (otherwise it will be Act/Act cluster and 2-nd license is required).
If there is no standard way (cluster configuration I mean) to do it I should create some custom process to monitor where each instance is running.
My environment has a 4 node cluster , 2 in primary and 2 in sec dc. Storage is sperate for both.
Need to setup always on for 4 Instances there on the 2 nodes of the primary dc. Is there any restriction in setting up always on for multiple instances for a cluster.
Is it possible to have more than one instance of SQL Server on a failover Active/Passive cluster? What are the concerns/ramifications if that indeed is possible?
View 4 Replies View RelatedHi All..
We are planning to build a cluster environment on MS SQL 2005. We want to install multiple named instances in a single database server and use cluster for that database server.
Is this option possible ? Any relevant documentation would be helpful
Thanks in advance
Regards
Madhav
Hi There
I have found no real documentation on this, so any links would be greatly appreciated.
We have an existing 2 node active active cluster.
A default and and named instance SS2005 Enterprise Edition are installed on the cluster.
Recently we acquired new hardware, 2 servers, which we added to the cluster so we now have a 4 node cluster.
The 2 new nodes have OS etc installed.
Now i have installed sql on a new multi node cluster, i have upgraded sql server in an existing cluster BUT i have never installed sql on an existing cluster for new nodes for multiple instances.
Now i presume you simply run the install on one of the new nodes, do this for a default instance, selecting both 2 new nodes to installl on. And do this again for the named instance.
But in the past I have never been promoted for which nodes to install sql on, it simply does all the nodes BUT i do not want this.
And how will the cluster know where the binary files are for each instance on the new nodes?
In a nutshell, how do i install sql server 2005 for 2 new nodes in an existing 4 node cluster for multiple instances ?
Thanx
I an involved in a project that will have five sql server instances on an NT cluster.
I cannot find anywhere on Technet info on what happens when a single instance fails. Do they all have to fail over or just the failed instance. This is important so that we get the disk layout correct.
Can anybody help ? or point me to any docs on this.
Hi
I have a cluster with 4 sql server 2000 instances and would like to upgrade 2 of these to sql server 2005 - is there any document or list of things to ensure I do
Thanks
Hi,
We have a new failover cluster (Windows 2003 SP1, Microsoft SQL 2000 SP4) with each node of the cluster hosting 7 SQL Server instances in a 2-node active-active configuration connected to a SAN. We are planning to move some SQL Server Instances(from existing stand-alone servers) into this Cluster. Any insight into the process of moving SQL Servers into the cluster would be highly appreciated.
Best Regards,
Himansu
Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server.
Got several issues i'd like some advice on.
1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move.
I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance.
For example: cluster install is aiproddbproduction, moved it to a box called aiproddb with a named instance called "production". There's a bunch of tedious network stuff that has to be done to make this work (binding an IP address to the MAC address of the new box and some murky DHCP reservation fiddling), but after the network crew got done cursing me it did finally work.
Does this seem like a reasonable approach?
2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.
3. what's the best way to transfer DTS packages?
4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?
5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way? Is the wizard for copying databases a good thing?
Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.
thanks,
Garth
I'm reading up on Always on and I am confused what is the difference between AlwaysOn Availability Groups and AlwaysOn Failover Cluster Instances.
View 3 Replies View RelatedIt is an active passive cluster which doesn’t allow any testing. All instances have to be failed over together, we aren’t allowed to just failover 1 even for testing purposes. Node 1 is the active node and we can failover to node 2 for 30 days free of charge but services have to then be failed back.
We need to run the cluster with node 1 as the primary node always and 2 just use for failover testing or for less than 30 day periods whilst performing cluster patch upgrades etc.
Now l am sure we could fail over 1 instances at a time for testing and diagnosing issues plus if add a new instance that's not production to get to the platform level as the rest of the instances this would avoid taking production down in the fail over process.
I am trying to install multi instances on my server cluster 2003 R2 Sp2. Because of the compatibility issues with my services I need to install both SQL 2000 and 2005. With 2000 I can easily specify the instance and servername. The server name can be the same, but the instance has to be different. Is this true for 2005? I have found so far that for every new instance that you create that you need to have a different virtual server name. How can you utilize the same virtual name and have multi insances
servername$instance1
servername$instance2
and so on
ThatGuy
We are running with a 2 node windows cluster having three SQL instances on it.
OS: Windows server 2008R2 SP1
SQL : SQL server 2008R2 (10.50.6529)
Currently both nodes have 256 GB or memory and we are having multiple auto failover for resources. What will be the best practice for OS memory reservation (OS+tools) so that we can set SQL max memory settings accordingly?
IF you need to change the IP Address of a SQL Server Failover Cluster instance, here is the steps:
1. Open up Failover Cluster manager.
2. Expand the MS Cluster Instance that your SQL Cluster instance resides on.
3. Expand Services and applications.
4. Select the SQL Server Service.
5. In the main window pane (Middle Screen), you should see your SQL Server Cluster name, expand the plus to the left of it.
6. Under your SQL Server Cluster name, you should now see an 'IP address' section, right click on it and go to properties.
7. In the properties pane, you can change your IP address by entering a static IP.....or assigning a DHCP enabled IP.
We have a SQL 2014 active passive cluster with 5 instances. When the cluster was installed one of the nodes was a virtual machine. As we started to have problems and this is not a Microsoft supported configuration we decided to replace the virtual node with a phyiscal one. On 3 of these 5 instances we configured static ports (1433 TCP) this was required for applications and firewall implementation.
Now with the physical node joined to the cluster we have issues with these three instances. Whenever one of these instances is moved to the passive node the server authentication is changed from mixed to windows only. I'm no SQL expert at all but to me it looks like the configuration of the instances are not replicated to the passive node? I found some similar problems on the net but these are mostly under sql 2008.
Hi,
I think this is a question for the specialists among us.
Can I use one general reporting server (installed on instance MAINREPORTING)
for multiple customers who all have their own sql instance (CUST1, CUST2, CUST3, ..)
I would use UserAuthenciation on the reportserver url to display the specific reports customers can use.
Is this possible, and what do i have to take care off concerning installation and/or configuration (especially on
the reporting side) ?
Greetings
Vinnie
i have sql server 2005 express running. during install, i had issues with a system dll that i found answers online and resolved. i am still very green, but i know much more now than i did at the time. i believe that as a result of the partial then failed installs i have multiple instances either fully or partially installed. when i am in the sql server mgmt express environment, it lists two sql engines. i only ever use one, and would like to safely remove the second without damaging or corrupting anything done with the other instance.
my reasons for wanting to do this are twofold. first, i would like to free up the drive space taken up by the second instance. (i am a stickler for clean harddrive mgmt and maintenance). second, now that i have used the software and am somewhat more familiar with it, i would consider installing a second, intentional instance so that i may attempt to better customize some of the install-time settings and configurations.
can anybody give me any pointers/ guide me in the direction of information on how to SAFELY go about this?
thank you in advance for any help.
I created a second SQL2000 instance on a Windows 2000 server. The strange thing is that I can create an ODBC connection to the default instance but cannot for the new named instance. If I try from a client that has SQL installed on it, I can see both instances. Any idea why this is happening?
Thanks,
Ken Nicholson
We're trying to decide if we should use a single large instance of SQL Server or multiple instances on the same server. This is for a dev environment.Have to limit max RAM per instance so no instance grabs it all.There will be I/O contention and CPU contention between instances since the different instances won't coordinate with each other.It limits the available RAM for In-Memory tables..It sets lower limits to the amount of RAM available for any given query, causing artificial "contention" even when there's nothing else running at the time.
View 2 Replies View RelatedAccording to the Task Manager, on my SBS 2003 Server, I'm running multiple instances of SQL. How do I determine which instance(s) are required to maintain server stability, and which are not. My Server resource use continues to be a perennial problem. Please advise.
View 3 Replies View RelatedSQL Server 2005 Enterprise
Is it possible to have multiple instances attach the same database?
I have a scenario where I want to have on one node, a clustered instance and a non clustered instance and both instances attach the same singular DB on a filer.
Is this possible?
Can SQL Server be setup such that one instance on a server is using SSL and another instance is not? Or is SSL a server-wide all-or-nothing issue?
Dave
Does SQL Server express support running multiple instances of database ?
View 1 Replies View RelatedIf I want to install 2 instances of SQL2000, will it install the SQL2K executable files (inn folder) onto 2 different folders, or all instances in one folder but the databases are in different folders.
Thanks
Please Help me on this.
I installed the two instances SQL on one box. ONe is default instance called ACSQL1(actually machine name) and the other one is called ACSQL1/DEVELOPMENT. THrought the my client site of SQL 2000 I can access both instances. When I try to get connection from VB. I can access the default instance but I can not access the second instance. Any ideas about this???
Qun Lu
I am running SQL 7.0 as the default instance and SQL 2K as a named instance. Each is using a different port....7.0 is using port 1433 and 2K is using 1024. Everything appears to be up and running fine on the server. However, I am not able to access the 2K instance from a client. I have tried to use both TCP IP and named pipes setting them up using the server network utility and the client network utility. No luck anywhere. I continue to get connection errors...check network documentation...
ANY IDEAS??????
Currently, I am running SQL Server 2000 with the default instance. I know SQL2K can run up to 16 instances simultaneously. I would like to add another instance but am unable to find documentation on how to add it. Books online tells me "about" multiple instances, but not how to set it up. I've obviously missed something somewhere. Can someone please direct me to a document that will help explain "how" to add another instance?
Thanks for your time and your help.
We have a DTS package that is submitted every minute by a SQL Agent job (2000). We see instances where before the first job is completed, the second one starts running.
Has anyone encountered this type of behavior before?
Is there any limit on SQL server Multiple Instances? if we require to run 60+ Instances on single machine what will be the minimum hardware requirements.
View 3 Replies View Related