Hi all,
we have two Win2003 machines in a Microsoft clustered environment. Each machine is running different SQL Server 2000 instances. Let's say we have machines sql1 and sql2. If sql2 goes down, sql1 automatically takes over the SQL Server instances that were running on the m/c that went down (sql2). As we are using some third party s/w (IBM's TWS sceduling tool) to run jobs on SQL Server instances (mostly backups), the TWS connects to a particular m/c and starts the SQL Server job.
The problem is that if one m/c goes down, TWS dowsn't know this, so the job fails, although the SQL Server instance runs on the other m/c.
The question is: is there a way to identify (through a script) which machine a particular SQL Server instance runs to? If yes, then we can amend our scripts, triggered by TWS, to identify this, and connect to the correct machine.
Thank you in advance.
we have two Win2003 machines in a Microsoft clustered environment. Each machine is running different SQL Server 2000 instances. Let's say we have machines sql1 and sql2. If sql2 goes down, sql1 automatically takes over the SQL Server instances that were running on the m/c that went down (sql2). As we are using some third party s/w (IBM's TWS sceduling tool) to run jobs on SQL Server instances (mostly backups), the TWS connects to a particular m/c and starts the SQL Server job.
The problem is that if one m/c goes down, TWS dowsn't know this, so the job fails, although the SQL Server instance runs on the other m/c.
The question is: is there a way to identify (through a script) which machine a particular SQL Server instance runs to? If yes, then we can amend our scripts, triggered by TWS, to identify this, and connect to the correct machine.
Thank you in advance.