I am looking for a best practice or any suugestion on the best way to install an additional Sql 2005 instance in a cluster environment. We have a production environment that is active/active/passive and need to install an additional instance with a little impact to the current production instances as possible. Ant suggestions or articles I can review?
View 1 RepliesWe have a SQL 2008 Instance existing on active/passive cluster with 2 nodes running on Windows server 2008 R2 Ent. Edn.
Now we need to install another SQL instance on this cluster. So what are the prerequisites apart from new IP address? Do we need shared disks or can the existing disks can be utilized?
Hey,
I have a 3 node cluster running 6 instances of SQL Server, I want to install Analysis Services along side of one of the SQL 2005 instances. Thus one of the cluster instances would host SQL Server DB, Analysis Services and SQL Agent. Is this possible or does Analysis Services need it's own Cluster Instance.
Thanks!
If i initially installed SQL Server 2005 Developer Edition using the "default instance", how do i create an additional (new) SQL Server 2005 (90) "named instance" without reinstalling SQL Server 2005?
I ran the Advanced cluster preparation for a new sql instance on an existing cluster.
Slq Server 2012.
After is completed, it was successful, I realized I specified the wrong Instance Root directory.
Is it possible to remove what the preparation installed? Or is it possible to change the root directory?
How can i add additional SQL server instance to existing clustered environment on SQL 2005.
View 7 Replies View RelatedI have installed a SQL Server cluster recently.Noticed below errors logged in the error log. I understand that SPN is not getting registered, hence this error.What permissions SQL Server service account? Service account is admin in local nodes anyway.
"SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service.
This is an informational message. No user action is required.SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon atte
2015-06-12 18:11:06.970 Logon Error: 18452, Severity: 14, State: 1.
2015-06-12 18:11:06.970 Logon Login failed. The login is from an untrusted domain and cannot be used with Windows authentication "
Hi all
SQL Server 2005 cluster. Active-Active. We want to create two instances. The two nodes are named:
mike-940-01
mike-940-02
I read somewhere that there can only be ONE default instance in a 2005 cluster. So I interpret that as meaning that I can only have one instance named after a virtual server (example: mike-940-03) and the other instance has to be a slashed instance (example: mike-940-03/instance1). But what if I create another virtual server (example: mike-940-04). Can I install a default instance in that server? Can someone help me clarify this?
Also, if I'm using all slashed instance names, then what does it choose as the base name before the slash? In other words, what decides which virtual server name is used? Is it the management node? Is it one of the nodes?
My objective is to keep consistency in the naming on the cluster. If I have to use slashed instances, then I want all sql server instances to have a slash.
Sorry about the confusing explanation, but that's probably a symptom of MY confusion.
Thanks!
Hi There
If i have a 2 node cluster running a single instance (default) and i want to add another instance to the cluster , can i install the second instance as a defualt instance ?
Since the cluster instances are referred to their virtual names/ip's and if i choose to intall the binaries of the second instance to a different location is this possible?
Since in theory you never have 2 default instances running on a single server but each within a virtual server?
Normally i install a named instance but do i have to ?
Thanx
We have an active/active two-node QA cluster with four instances of sql. I need to add a fifth. In the past I always moved existing instances to the other node while installing a new instance.
Other than impacts to users from install reboots, is that a hard requirement?
QA is reluctant to have me put the four existing instances on one node for most of a day, fearing big performance slowdowns. Each node has 250GB of memory and each instance is allowed 50GB. Netapp disk backend.
Hi all,
Newbi to sql clustering.
I have a sql server 2005 standard edition with Active/Passive Cluster in production.
I have a new requirement where i need to create a new instance on this active/passive cluster that can be used by our sharepoint servers. Can somebody please let me know what are the steps that i need to follow like
1.What i need to ask my network admin?
2.How i need to proceed installing?
I am planing to do this over the weekend where i have the liberty of some down time.
Any help greatly appreciated
Thanks
I have a SQL 2008 R2 2 node cluster. For DR testing, I need to restore an instance on a new server (completely isolated). The existing instance runs on what I would call an alias. The actual cluster host name is SQLPROD (cluster nodes are SQL01 and SQL02). The instance runs on server SQLPROD-APPLE. The instance is called APPLE. In production, I use SQL Management Studio and I connect to SQLPROD-APPLEAPPLE.
I've setup a new VM to run SQL. Not a cluster. Host name is SQLREC. The new Vm has all the IP addresses that were on the cluster and the DNS for all the aliases are correct. I've installed instance APPLE. I created an alias called SQLPROD-APPLE. When I try to open SQL Management Studio and connect, I can't connect to SQLPROD-APPLEAPPLE. I can connect to localhostAPPLE, SQLRECAPPLE, 192.168.168.50APPLE.
When I attempt to connect to the alias I get error 18452. Pinging the alias resolves correctly. I haven't gotten to the database restore yet, so that's not a concern. I'm just trying to validate the connection first with the correct server and instance names.
I'm using Windows Authentication.
I understand most of the concepts for the Active/active setup. I am setting up a 2 node cluster. My question is can I use the default instance name (one default instance name per group) when setting up each instance or do I have to use named instances . I am assuming that since each group is a virtual machine that I can get away with using the default instance, but I cant find any documentation to confirm my frequently wrong perceptions.
I want to set it up like this
Instance1 Group
Group resources
Default SQL Instance Name Installation
Preferred Owner Node1
Instance2 Group
Group resources
Default SQL Instance Name Installation
Preferred Owner Node2
Thanks
Hi,
I am trying to remotely connect to a SQL 2005 Instance on a cluster. I see the following error:
No retry on exception System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I have enabled TCP/IP , Named Pipes on the node. I have turned off IPSec on the clients as well. I am using the following connection string : "Integrated Security=SSPI;server=servernameinstancename;Pooling=false;database=TrialDB"
Is there something I am missing?
Any pointers will be appreiciated.
thanks.
I have a system running a sql 2000 instance w/ multiple databases located in a SAN. I would like to cluster my SQL 2000 environment on the same system. Can I do this without reinstalling another database instance? Can I put my current default instance and put it to my virtual server instance? Help is really appreciated. Any tips and links can be helpful to me.
View 3 Replies View RelatedHello,
I install Cluster naming instance of MSSQL 2005 Enterprise edition with SP2 and latest patch.
When I try connecting this instance from outside of the server by "server nameinstance name" I got connection error.
But when I connecting by "server name,port number" it's connecting with no problem.
Can someone help me resolve connection outside of the server with "server nameinstance name"?
Thanks
Having problems running the BPA for 2012. We setup using a clustered environment, SQL Server installed using default instance, and a static port not 1433. When I try to run the BPA using the instance name it says it doesn't exist, and won't let me add a port number. However, if I use MSSQLSERVER as the instance name it runs with no port specified and returns results. I assume that it doesn't require a port because the default instance would pull from the Browser Service and the using MSSQLSERVER is the same as running the default on a standalone server. Are those assumptions correct?
View 2 Replies View RelatedI've a fresh installation of SQL Server 2014 Enterprise on Windows Server 2012R2. I've setup de Windows Server Failover Cluster and the validation test has been successfully passed. I use mountpoint so I've disk M: that is the host drive for mounted volume m:Isql2014A that is the base folder for mounted volume
On that folder I've 5 mountpoint:
1) m:isql2014a empdbdata
2) m:isql2014a empdblog
3) m:isql2014auserdata
4) m:isql2014auserlog
5) m:isql2014auserlog
into these 5 mountpoint I've placed the SQL Server files.
After the installation of the first FCI I've re-run the cluster validation wizard and again it has passed successfully. When I try to failover the instance from one node to the other I have 2 problem:
1) every time I do failover, some disks fail to come online for a while and then succeed :
Cluster resource 'CLD - IstA - TempDB Data' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
2) sometimes the SQL Server service fails to start, in the error log I see that the master database is not accessible. The master database in into the m:isql2014abinbackup.
I have a SQL 2000 clustered environment with 4 SQL instances and i need to remove a specific instance from the cluster the resources(physical drive,virtual IP,instance name) being used by it
View 5 Replies View RelatedIs there a way for multiple SQL 2005 instances in a cluster to share drives for user databases.
Once we install our instances in the cluster using seperate disk resources. Can we then have multiple instances share the same physical disk for user databases only. This is for a test environment.
Thanks
I am new to SQL Server 2012 clustering.I added a new instance to one of the two nodes.when I try to move it to the other node it fails.Do I need to install it on both?If so, what options do you install on the second node?
View 7 Replies View RelatedI'm have been assigned the task of installing SQL Server 2005 as a cluster on a Windows cluster that has already been setup with a sans.
I've done alot of reading the past two days and I still have a few questions which I need answered before I begin.
Our setup-
DC - nothing but domain controller
S1 - SQL server 1
S2 - SQL server 2
S1 and S2 share the following drives (database) (transaction logs) (F) (G)
Do I install SQL on each of the clusters? If so, do I just follow the instructions the exact same? And am I suppose to power S2 down while I install SQL on S1 and then vice-versa?
Thanks.
2 issues:
1. have 4 drives and all are within the SQL resource group but can see only 1 drive through management studio when doing a backup
2. Is restore only possible through the /backup folder on the default installation path as it is a small drive so can a restore be possible from any other locations
Any help
In QA we have a two-node cluster with four instances of sql. In trying to add a fifth, I was given an IP address already in use so the install hung.
I removed it from the cluster but it is still there in the registry etc on the node I was working on.
I read about using the maintenance tab of the sql server install to "remove a node" but the terminology is confusing. To me a node is a physical server and an instance is an instance of sql server -- not the same at all but they are often referred to as the same thing.
I definitely don't want to remove one of the servers from the cluster.
I need to create a named instance on a sql cluster.
How do I perform this? Is it as simple as creating a named instance on a standalone machine? Is there anything I need to consider?
Hi all. I have ran into a annoying situatin on sql cluster. Config is:
w2k3 EE x64 r2 - two nodes
sql 2005 x64 standart v2153
2instances, active-active cluster.
While changing tcp port configuration of one instance (using configuration manager) I have acidentaly created that setting:
- All IP dynamic port and All IP port was set to same number while separate IPs have enabled dynamic ports and does not have static port set.
This situation leads to unability of starting the instance anymore. There is no need wide explanation, its quite clear - while starting instace, it was configured with static port and with dynamic port with the same number, so port conflict error takes place. Problem was how to escape from this situation. On non clustered sql is quite easy, because these settings are stored in registry and also can be changed thorough Configuration manager, easy solution. Nor on the cluster.. Modifying the registry even on both nodes was unefective, every try to start instance fails with port conflict error and bad config was saved to registry again. I wasnt able to find where this config resides and change it to corect values. I have revealed only that it is not stored in instance master DB (restoring it from backup). Looks like its held somehow by cluster service itself, but I didnt find where it should be and how to edit it. So the last possible option take place (time was against me) - reinstalation of whole clustered instance. Nice example of how one click can create you a 2 days of work... Iam still interested if there is a smooth and easy way out of this situatin:-) So if anyone knows..... If there is not, I realy warn everybody.
DAvid
I have two clustered server. (ms sql 2000 server, windows 2003 server) now i need to add one new server to the cluster and take the secondary node off.
I have installed SP4 & hotfix in my SQL Server cluster before.
My question is do I still need to install SP4 & hotfix in my new server?
Thanks in advance
I have YET to have a 100% CLEAN install of SQL 2005 in a clustered environment. SQL 2005 Std. was not so bad, I think I finally managed a 99% clean install (no script errors on patches) on the third try.
SQL 2005 EE keeps erroring off on 2153 patch install. The error logs are no help at all; they simply stop logging activity at about the point that the error occurs.
For a premier product, this installation SUCKS.
Whooo. Okay. I feel better.
Here's my situation:
4-node Cluster (Windows 2003 Enterprise Edition), SP1
SQL 2005 Enterprise Edition
Process:
Install OS
Patch OS to SP1
Cluster OS on SAN
Configure Cluster Groups (DBC01, DBC02, DBC03) with cluster disks
Configure MSDTC (network access, configure cluster resources)
Start SQL Installation
Install RTM Binaries on Node 1 for Default Instance
Install Workstation and non-cluster components on remaining nodes
Install RTM Binaries on Node 2 for Named Instance
Reboot all nodes
Install SP1 for all instances from node 1
Install SP1 for all local services/applications for all other nodes
While attempting to install the 2153 SQL patch/hotfix, the process will either:
Hang while waiting for the first passive node for the default instance; or
Crash immediately with no error messages in the logs.
This is no nearly detailed enough, I know. I'm missing error messages and more. It's snowing outside and I have to get home. I just think that the installation for this product in a clustered environment is very unstraightforward at best, and at worst is a real liability to an organization since it's practically impossible to get it clean the first time through.
Regards,
hmscott
I'm trying to install SQL into a new cluster. The cluster service is up and running fine. I can even fail it from Node 1 to Node 2 with no problem.
However, when I try to install SQL, I get a screen that tells me that SQL is performing required operations on the cluster nodes...this may take a few minutes.
After hanging on that message for a looong time, SQL comes up with a generic message that the install failed and that SQL is cleaning up. Then, nothing. No error message, nothing that I can track down.
Some system information:
Node 1. Dell PE2650, 2x 2.8 GHz, 2 GB RAM
- Windows 2000 Advanced Server
- Dell Perc3/DC RAID/SCSI Controller
- Dell Perc3/DI Integrated RAID Controller
Node 2. Dell PE2650, 2x 2.8 GHz, 2 GB RAM
- Windows 2000 Advanced Server
- Dell Perc3/DC RAID/SCSI Controller
- Dell Perc3/DI Integrated RAID Controller
Shared Storage. Dell PV220
- Q: Quorum (1 GB)
- S: Data (136 GB)
- T: Logs (20 GB)
Additional Notes:
1. I am using a checklist from Dell and another from MS.
2. I have also downloaded and read the checklist from sql-server-performance.com.
3. I have ensured that the comclust.exe was run on both nodes prior to starting the SQL installation
4. I am using SQL Enterprise Edition. We used the same CD to install a cluster server two weeks ago.
Questions:
1. Where can I find an installation error log that might point more specifically to where the problem might be?
2. Any thoughts on what the problem might be?
3. Anyone ever experience something similar?
Have SQL 2000 SP4 clustered instance running now. Attempted inplace upgrade to SQL 2K5 standard edition.
Boxes are Windows 32 bit Ent Edition, SP2. Install wizard installed pre-req's just fine, and I got past the "components to install" box of the install wizard. When I clicked next, the current 2000 instance (already installed component) was grayed out and I could not select it. Checking the messages in the install wizard, I saw that my "upgrade was blocked".
I cancelled out of the install wizard to verify all requirements.
Bounced both boxes, and now when I try to run the install wizard, it tried to install the required support files (ASP.net 2.0, SQL Native Client and what not) and then the install wizard hangs..... and never comes back. I have to kill it from taskmgr. Bounced the boxes and tried again, same thing. Install wizard hangs forever.
Yes, I am running from the active node holding the cluster resources. Yes, SQL 2000 instance is cold. Yes, I've checked add/remove programs and there is nothing to uninstall.
Checked event viewer and I see the following errors:
Hanging application setup.exe, version 2005.90.1399.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Fault bucket 238575085.
I've reached out to our TAM, but any help would be appreciated. No matter how many times I try, the install wizard now chokes and never comes back.
When you try to re-apply SP2 for SQL 2005 on node added to cluster it continously fails?
Only way to apply SP2 is to shut down original node(with SP2 allready applied) and then apply SP2 and hotfixes on additional node!
I would like to see some reply from SQL support team for this 'issue'. Is this normal? This bring many issues when you have more than one sql on 2 node cluster....etc
any explanation is appreciated
rgds
Sinisa
I'm running into issues installing SQL 2005 Enterprise on a Win2003 server. They seem to be related to missing rights. I've done a lot of research and have come up empty. Does anyone know why I'm getting these log entries? Thanks for any help.
Running: OpenPipeAction at: 2006/0/31 11:35:35
Complete: OpenPipeAction at: 2006/0/31 11:35:35, returned false
Error: Action "OpenPipeAction" failed during execution.
Error: 0x80070005 TaskScheduler::SetTargetComputer for \SERVER
Complete: RunRemoteSetupAction at: 2006/0/31 11:35:35, returned false
Error: Action "RunRemoteSetupAction" failed during execution. Error information reported during run:
Attempting to determine log files for remote install.
Connection to remote computer's scheduler service.
Error: 80070005 Access is denied.
Skipped: InstallASAction.11
Waiting for actions from remote setup(s)
Breaking wait state and aborting package due to cancel code received: 1602
Remote setup(s) are ready
Notify package action is determined: 1602
Error Code: 0x800700e9 (233)
Windows Error Text: No process is on the other end of the pipe.
Source File Name: remotemessageliboverlappedpipelistener.cpp
Compiler Timestamp: Fri Jul 29 01:13:51 2005
Function Name: sqls::OverlappedPipeListener::writePipe
Source Line Number: 294
Notification failed to send.
Just to confirm I do need to run SQL 2005 SP2 on the passive node. but the passive node should be rebooted.
View 1 Replies View Related