please see my post in the previous thread;
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2606008&SiteID=17&mode=1
We are making our final decission of using either transaction log replicant or a database mirror replicant and which solution would provide the biggest ease of provisioning as well as the fastest turn around in recovery.
"Good Morning Team,
I have a client whom has a 2 node SQL 2005 cluster with over 100 databases, their schema design is that they create a new database for every customer that signs to their services.
The problem I am encountering is that for every new database created in the cluster we like to setup a SQL2005 mirror replicant at a remote site for disaster recovery should the cluster ever fail.
i'm looking at the SQL professionals to help me with 2 questions.
#1 Upon creation of a new database in the cluster is there an easily scripted method that could be used to automatically create the mirror replicant, what about if not being aware of the new databases having been created? since we do not know when the customer creates databases or perhaps a SQL job that could be done based on new databases created that would automatically script the procedure of a database mirror.
#2 understanding the procedures required in a mirror replicant from a cluster primary involving, database backup, database restore to mirror replicant, transaction log backup and then transaction log restore with both points of the restore leaving the mirror replicant in NO RECOVERY mode and lastly creating the connection end points.
has anyone encountered such a situation with a database cluster with a mirror replicant consisting of such a wide span of individual smaller databases and would anyone have suggestions on how to make this highly available with a mirror replicant?
We currently have one instance of SQL2k5 SP1. We have a couple of publications, and 30 subscribers, on the instance and are considering going to either a cluster environment or db mirroring. Currently our instance seems to be busy and I am wondering if clustering really gives it a performance boost. What are your thoughts/suggestions on going to a cluster environment versus just db mirroring? Can mirroring be used for real-time failover as we need to add that as well? Thanks in advance.
I have configured active passive cluster in production environment. And we also have a dr which we have configured with asynchronous mirroring with no witness. Currently active node(node
a) is in sync with dr. When failover happens and the second node(node b) becomes active, the mirror is broken and goes to disconnected mode.
But when we failback again to node a mirror is connected again and is in sync again. In our setup we have active passive cluster and a standalone server as dr.
if an app sits in an environment where both clustering and mirroring are available for HA, are there some simplified best practices, perhaps patterns or .net classes suggested by MS for making the app aware of both clustering and mirroring?
If the mirror db is also contained in the original connection string as a retry partner and SQL failed over automatically, the app wouldnt have a say in first retrying against the cluster. It might prefer cluster first because the mirroring is asynchronous and therefore a bit less up to date than the cluster. This of course assumes the app is ok with the longer failover time. If the partner isnt included, the app needs to be aware of two connection strings.
Is there some feature in SQL for having the best of all worlds, ie one connection string but having a "say" or "rule" in exactly what sql does and doesnt do for you and in what order?
We are going thru the process of scoping an active/active cluster at one site. I was wondering whether there will be any issues with mirroring (DB by DB) off the cluster into non clustered server at an alternate DRP site.
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
I am using SQl Server 2012 Database Mirroring with around 40 gb as mdf and 1 gb as ldf. Now my ldf size increased . How to reduce ldf size while mirror enabled with mirror server and witness server. Can shrink the ldf with mirror enables.
I'm trying to setup a SQL 2005 SP2 Mirror in between two mashines with no witness server.
I have successfully established the following:
1. Backup The Database on Principal Server: OK!
2. Copy the backup over to the mirror server: OK!
3. Restore the Database on Mirror Server: OK!
4. Establish Endpoint on Principal Server: Encyrption Disabled OK! TCP - PORT 5022
4.1 Test Script: Checks fine (values match)
SELECT e.name, e.protocol_desc, e.type_desc, e.role_desc, e.state_desc, t.port, e.is_encryption_enabled, e.encryption_algorithm_desc, e.connection_auth_desc FROM sys.database_mirroring_endpoints e JOIN sys.tcp_endpoints t ON e.endpoint_id = t.endpoint_id 5. Establish Endpoint on Mirror Server: Encyrption Disabled OK! TCP - PORT 5022
5.1 Test Script: Checks fine (values match) (same script as above)
6. Specify Principal server from Mirror server: OK! Connecting with IP
7. Specify Mirror server from Principal server: OK! Connecting with IP
8. View Mirror Information:
8.1 Test Script: Shows everything in NULL
SELECT mirroring_state_desc, mirroring_partner_name, mirroring_witness_name, mirroring_witness_state_desc, mirroring_role_desc, mirroring_safety_level_desc FROM sys.database_mirroring
Mirror endpoints are still in red even though they initialized correctly. Mirror monitor shows no mirrors are up. SQL Logs shows: The Database Mirroring protocal transport is now listening for connections. Any help would be appreciated.
I have SQL 2005 mmirroring sucessfully working in an ASP.NET 2.0 web application. I also have session state being maintained in SQL Server using the built-in functionality in ASP.NET. The problem is, even with "allowCustomSqlDatabase=True" and specifying a failover partner in the DSN, it appears that ASP.NET does not work with the failover partner. It always tries to get the session info from the "data source" server specified in the DSN.
Is there a way to get the session state to fail over to the mirrored server without writing a custom session state provider?
I have a SQL Server 2005 DB server (SRV1) and a mirror DB server (SRV2) without witness server. I saw that there is a "Failover" button on Mirror window of SRV1. When click it servers changes roles.
My question is that: If my mirrored DB server crashs and I can not open windows or if I lost all data on SRV1, how can I failover from only mirror DB (SRV2)?
I hope this is in the right forum, I'm new to MSDN. I'm also not an expert in SQL, so please bear with me as I was unable to find an answer by searching the archives.
We have a single SQL 2005 Standard installation with 30 user CALs on a Server2003R2 box. We have another Server 2003 box in a remote but connected location that we previously used for backup replication. What we'd like to do is use some of the replication features in SQL 2005 to replicate the data over every night to the other box, onto which we would install another copy of SQL 2005. This would not be a server accessed by clients, but simply a "live backup", that in the event of a catastrophic failure, could be manually set up to operate as a SQL server in place of the failed primary server. I don't need any kind of automatic "failover", just the ability to replicate the data over to the other system so I have two SQL Servers that synchronize from one to the other overnight.
I was told that I wouldn't need to buy the user CALs again, that the 30 user cals would translate over if the primary server fails and has to be replaced by the cloned server. But what do I buy for the SQL server itself? A boxed version is a bit pricy and comes with 5 CALs which apparently I wouldn't need. Then I noticed that on softwaremedia.com the open license version, which can be bought a la carte, lists a requirement of buying at least 5 cals or a processor license. What exactly do I need to do this, and how can I get it for the least amount of further spending?
I've tried to replicated exactly what it says in the online documentation. At the end of the post are the SQL statements issued.
1. Enable encrypted outbound connections on the primary server 2. Enable encrypted outbound connections on the mirror server 3. Enable encrypted outbound connections on the witness server 4. Enable encrypted inbound connections on the primary server 5. Enable encrypted inbound connections on the mirror server 6. Enable encrypted inbound connections on the witness server 7. Set mirror''s partner to the primary 8. Set primary''s partner the mirror 9. Set principal€™s witness. Every step run''s normally,but why can''t auto failover.
I used the following Script:
/* -------- 1. ENABLE OUTBOUND CONNECTIONS ON THE PRIMARY -------- */ use master; go DROP USER PrincipalLogin1 DROP LOGIN PrincipalLogin1 DROP USER PrincipalLogin2 DROP LOGIN PrincipalLogin2 GO
Create login PrincipalLogin1 with password='PrincipalLogin' go Create user PrincipalLogin1 from login PrincipalLogin1 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin1 go ---stop
create certificate MirrorCertForPartnerPub authorization PrincipalLogin1 from file = 'd:BackupCertMirrorCertForPartner.cer'; go
Create login PrincipalLogin2 with password='PrincipalLogin' go Create user PrincipalLogin2 from login PrincipalLogin2 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin2 go create certificate WintnessCertForPartnerPub authorization PrincipalLogin2 from file ='D:BackupCertCertForDBRole.cer' GO
ALTER DATABASE Mirrortest SET PARTNER = 'TCP://10.1.40.158:5022' GO
ALTER DATABASE Mirrortest SET witness = 'TCP://10.10.11.30:7000' GO
select * from sys.certificates
/* -------- 2. ENABLE OUTBOUND CONNECTIONS ON THE MIRROR -------- */ --On Mirror --Remove the database --Connect to either partner. --Issue the following Transact-SQL statement:
ALTER DATABASE Mirrortest SET PARTNER OFF
--Optionally, you can recover the former mirror database. On the server instance that was the mirror server, enter:
--RESTORE DATABASE Mirrortest WITH RECOVERY;
RESTORE DATABASE [Mirrortest] FROM DISK = N'D:BackupCertMirrortest.bak' WITH FILE = 1, NORECOVERY, NOUNLOAD, REPLACE, STATS = 10 GO select * from sys.endpoints
drop endpoint Mirror_Endpoint_Mirroring
select * from sys.certificates
Create certificate MirrorCertForPartner with subject ='this is the certificate for mirror', start_date='06/25/2006'
backup certificate MirrorCertForPartner to file='d:ackupcertMirrorCertForPartner.cer'
CREATE ENDPOINT Mirror_Endpoint_Mirroring STATE=STARTED AS TCP (LISTENER_PORT=5022) FOR DATABASE_MIRRORING ( Authentication=Certificate MirrorCertForPartner ,ROLE=ALL) GO
/* -------- 3. ENABLE OUTBOUND CONNECTIONS ON THE WINTESS -------- */
--On Witness
USE [master] GO
select * from sys.certificates
drop certificate CertForDBRole GO
create master key encryption by password='asdf'
Create certificate CertForDBRole with subject='this is a certificate for pricipal role', start_date='06/25/2006'
backup certificate CertForDBrole to file='c:CertForDBRole.cer'
select * from sys.endpoints
drop endpoint Witness_Endpoint_Mirroring
CREATE ENDPOINT Witness_Endpoint_Mirroring STATE=STARTED AS TCP (LISTENER_PORT=7000) FOR DATABASE_MIRRORING ( Authentication=Certificate CertForDBRole ,ROLE=ALL) GO
/* -------- 4. ENABLE INBOUND CONNECTIONS ON THE PRIMARY -------- */ use master; go DROP USER PrincipalLogin1 DROP LOGIN PrincipalLogin1 DROP USER PrincipalLogin2 DROP LOGIN PrincipalLogin2 GO
Create login PrincipalLogin1 with password='PrincipalLogin' go Create user PrincipalLogin1 from login PrincipalLogin1 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin1 go ---stop
create certificate MirrorCertForPartnerPub authorization PrincipalLogin1 from file = 'd:BackupCertMirrorCertForPartner.cer'; go
Create login PrincipalLogin2 with password='PrincipalLogin' go Create user PrincipalLogin2 from login PrincipalLogin2 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin2 go create certificate WintnessCertForPartnerPub authorization PrincipalLogin2 from file ='D:BackupCertCertForDBRole.cer' GO
ALTER DATABASE Mirrortest SET PARTNER = 'TCP://10.1.40.158:5022' GO
ALTER DATABASE Mirrortest SET witness = 'TCP://10.10.11.30:7000' GO
select * from sys.certificates
/* -------- 5. ENABLE INBOUND CONNECTIONS ON THE MIRROR -------- */ use master; go DROP USER MirrorLogin1 DROP LOGIN MirrorLogin1 DROP USER MirrorLogin2 DROP LOGIN MirrorLogin2 GO
Create login MirrorLogin1 with password='MirrorLogin' go Create user MirrorLogin1 from login MirrorLogin1 go
Grant connect on endpoint::Mirror_Endpoint_Mirroring to MirrorLogin1 go
--stop create certificate PrincipalCertForPartnerPub authorization MirrorLogin1 from file = 'd:BackupCertPrincipalCertForPartner.cer'; go
Create login MirrorLogin2 with password='MirrorLogin' go Create user MirrorLogin2 from login MirrorLogin2 go create certificate WitnessCertForPartnerPub authorization MirrorLogin2 from file ='D:BackupCertCertForDBRole.cer' GO
Grant connect on endpoint::Mirror_Endpoint_Mirroring to MirrorLogin2 go
ALTER DATABASE Mirrortest SET PARTNER = 'TCP://10.10.116.42:5022' GO
ALTER DATABASE Mirrortest SET WITNESS = 'TCP://w7mis02:5024' GO
/* -------- 6. ENABLE INBOUND CONNECTIONS ON THE WITNESS -------- */
use master; go DROP USER WitnessLogin1 drop login WitnessLogin1 DROP USER WitnessLogin2 drop login WitnessLogin2
Create login WitnessLogin1 with password='WitnessLogi*n@' go create user WitnessLogin1 from login WitnessLogin1 go
create certificate PrincipalCertForPartnerPub authorization WitnessLogin1 from file = 'c:ackupcertPrincipalCertForPartner.cer'; go --*************************************** Create login WitnessLogin2 with password='WitnessLogi*n@' go create user WitnessLogin2 from login WitnessLogin2 go
create certificate MirrorCertForPartnerPub authorization WitnessLogin2 from file = 'c:ackupcertMirrorCertForPartner.cer'; go
Grant connect on endpoint::Witness_Endpoint_Mirroring to WitnessLogin1 go Grant connect on endpoint::Witness_Endpoint_Mirroring to WitnessLogin2 go
After adding the Witness Server to the Mirror session, the Witness Connection state between the Mirror and Witness Connection is Disconnected and the state between Principal and Witness Connection is Connected.
The procedures defined in Books Online was used to setup Database Mirroring...when the Witness server was added to the Mirror session, only the alter database T-SQL statement was executed on the Principal server.
ALTER DATABASE <db_name> SET WITNESS = 'TCP://<servername>:<port>'
After executing the above statement, a few seconds later the state between Principal and Witness Connection changed to Connected and the state between Mirror and Witness Connection remains Disconnected.
The Mirror session is not using Certificates, every server is on the same domain, using the same domain login account, and all servers have SP2 installed running Enterprise Edition.
Any idea's why the state between Mirror and Witness Connection remains Disconnected?
I was trying to test mirroring and now would like to delete the mirror database but it says I need to remove database mirroring first. I deleted the endpoint and cannot figure out how to remove the mirroring. Can someone please help.
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
When I run sp1 on the active node of a 64-bit cluster the setup just hangs when it gets to the Database services part. It does not return any errors as mentioned by others in this forum. I also do not have SqlSupport.msi in the add/remove programs (one suggestion on this forum was to uninstall it reinstall). I have let it run for up to 12 hours with no result.
There is no SQL9_Hotfix_KB913090_sqlrun_sql.msp.log file only SQL9_Hotfix_KB913090.log
this is the content
05/09/2006 12:41:12.274 ================================================================================ 05/09/2006 12:41:12.274 Hotfix package launched 05/09/2006 12:41:15.634 Product discovery successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 SP Level check successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 Product language check successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 Product version check successfully completed during the install process for DEV01 05/09/2006 12:41:15.681 Product discovery successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 SP Level check successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 Product language check successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 Product version check successfully completed during the install process for DEV02 05/09/2006 12:41:15.743 Product discovery successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 SP Level check successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 Product language check successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 Product version check successfully completed during the install process for DEV03 05/09/2006 12:41:15.790 Product discovery successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 SP Level check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Product language check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Product version check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Command-line instance name check completed during the install process 05/09/2006 12:41:15.868 Baseline build check completed during the install process 05/09/2006 12:44:25.795 Attempting to install instance: DEV02 05/09/2006 12:44:25.795 Enumerating passive cluster nodes 05/09/2006 12:44:25.873 Patching available passive node: TTCSQL62A 05/09/2006 12:44:25.873 Waiting for first successfully completed passive node 05/09/2006 12:44:25.873 Attempting to patch running passive node: TTCSQL62A
we want to have an activepassive and active passive cluster.
node a install sql instance 1 failover over to node b
node b install sql instance 2 failover to node a
do I have to setup 2 cluster ? ie. quorum, msdtc etc..
or just one cluster(quorum, ip and name), one msdtc group( as per MS msdtc doc) and 2 san disks (one for node a and one for node b.
is this correct? I have looked and looked for a step by step on setting this up, no where can I find what i need. I downloaded the failover cluster doc from microsoft, book online etc..
I want to create an activepassive on both nodes. (onenode will be the active node for on sql install while the other is passive.
I want to repeat this fo rthe second node, the second node being active and node 1 passive.
I logged into node 1 and I installed sql 2005 in failover cluster into sqlinstance 1., everyhting was fine, failover etc.
Now I logged into node 2 and ran sql 2005 setup to create a failover cluster.
I chose to install into sql instance 2.
Database unable to install with error "failed to set registry settings for server network libraries. acition is setdefaults.error 11001, no such host is known.
If I am not setting this up correclty please let me know
thanks
everything was fine. I logged onto node 2, was going to
I'm having trouble finding the recommended process for doing a full Disaster Recovery on a two node active/passive sql 2005 cluster. I've been able to locate the procedure for rebuilding a failed node on the msdn site but no procedure for recovering the entire system. Any assistance or points in the right direction are appreciated.
I have just recently inherited a sql server 2005 cluster (2 nodes) we have a situation coming up where i need to power down the whole cluster for several hours as a result of some power mains work.
I just need to confirm with someone the correct way to power down the whole cluster and power it back up once the power is restored the company. I appreciate this may not be the best place to have posted this but i am desperate and couldn't find another location.
Anyone know before I invest in the hardware if it is possible to have Two Clusters on the same hardware both in Active/Passive Clustering where Cluster1 and Cluster2 both use the Default SQL Server 2005 Instance (No Named Instances)?
This would be a Virtual Cluster with Two separate 2 node Clusters on the Same Hardware sharing the same OS and SQL.
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.
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.
According to SP1 documentation patching the Active node in a cluster will automatically apply the SP1 patch to the Passive nodes. However, I found a MS document that says if you have management tools installed on the passive node, you must patch this node separately. Is this correct?
Also, since Integration Services is not cluster-aware and therefore must be installed separately to the passive node(s), does SP1 need to be applied directly to the passive node(s) to patch Integration Services or is it automatically patched when I patch the Active node?
I am trying to remove Analysis Server from a cluster. I have done the research and according to MS you can't use the regular add/remove programs dialog to remove a component. You have to use the setup.exe from the command line. This article (http://support.microsoft.com/kb/910230) explains at the very bottom to run this command "Start /wait <DiskDrive>setup.exe /qb REMOVE=Analysis_Server INSTANCENAME=<InstanceName>". Well I do that and I get the installer up and running but when it gets to that system configuration check screen, where it runs a bunch of checks on the nodes, it just closes before it does any checks and nothing further happens. I can't find any error in the event log or find any log files on disk related to why its just closing.
Just to investigate further, I wondered what executable was running when you ran the installer though the add/remove programs dialog, so I looked in the registry. Well along with the SQL Server 2005 entry, which runs the setup bootstrap program in your default install folder, I noticed an entry that was idenified only by its GUID. Looking at the sub keys I noticed the DisplayName was Microsoft SQL Server 2005 Analysis Services. The UninstallString key was set to "MsiExec.exe /I{52B0D62A-860D-4136-9A8A-9FD877E8EE89}" so I ran that. The installer seems to work, but it doesnt run any configuration checks. I get to the screen with the big button to change components with no errors. Then it acutally shows Analysis Services installed (the disk icon is not xed out), I can then click and select entire feature will be unavailable. I haven't proceeded on this step because I am worried about the cluster.
I am assuming that this uninstaller will only remove analysis services from the node its running on. This is fine, cause I can just run this same procedure on all the nodes... and then i would assume I would have to manually clean up the cluster resource. But I have not tested this, and unfortuanlly I don't have a development cluster to try this on.
Does anyone have experience with removing Analysis Services from a failover cluster environment?
Our production server is currently running SQL 2005 on a stand alone machine. SQL Server is installed as a default instance.
Can we upgrade to a cluster without having to change the instance name i.e currently applications connect to this server with hostname of the server i.e SERVERA, can we install a cluster such that sql server can still be called SERVERA.
...so got the below information from the cluster log:
000009fc.00000d68::2007/02/13-12:36:53.210 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] OnlineThread: QP is not online. 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 0000088c.00000af8::
Looked at the system log to see if there are any errors , but could not found any during that time....The last message in the system log was
Event Type: Warning Event Source: Print Event Category: None Event ID: 3 Date: 2/13/2007 Time: 5:03:04 PM User: NT AUTHORITYSYSTEM Computer: xxx Description: Printer ITGHP8N1 on rchprt01 (from R6911497-XP) in session 1 was deleted.
before that there were messages of creating and deleting the printer...and R6911497-XP is my laptop which was not really running during that time...
From some research came to know that this might be because of network issues, but let me know for what errors I need to look for network issues...does the above error in the system log suggests network errors...
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
We are trying to install SQL Server on a cluster that has 4 nodes, 3 of them running SQL2k. We're getting an error in the setup after it is done with Framework:
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache ... Source File Name: datastoremachineconfigscopeproperties.cpp Compiler Timestamp: Wed Aug 24 13:40:04 2005 Function Name: SqlInstallConfigScope.InstanceName ....- Error: Could not find an install of type 3 for instance SQL ##
We think it's due to a directory and item in the registry for a server instance we used to run on this server, but no longer due as it was uninstalled and the server moved to this cluster. The directory doesn't show in other nodes in the cluster, but does in the cluster it was moved from. We continue to find that 2nd instance refuses to failover to this server also. We have determined that it€™s only the SQL server which is having issues as we were able to move the disks over. When we start the SQL service it pops back to 2nd instances home server.
