Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Moving Groups (SQL and Cluster Group)

Author  Topic 

dewacorp.alliances

452 Posts

Posted - 2007-06-20 : 16:18:13
Hi all

I need a clarification regarding this:

"In MS Cluster 2003, if I do the moving groups (SQL and cluster groups) from one to another. It seems that the SQL Service service gets restarts? Is this true?"

I thought that there is smooth transition between one to another as long as you do it this ways unless you shutdown unproperly.

Any input I really appreciated.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-06-20 : 16:21:14
Yes the service gets restarted when you move from one node to another node.

And yes this is considered a smooth transition.

This is how clustering works.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

dewacorp.alliances

452 Posts

Posted - 2007-06-20 : 16:25:02
Thanks Tara.

But if it's a smooth transition, how come one of my job is failed then during this moving groups within cluster?

Thanks.

quote:
Originally posted by tkizer

Yes the service gets restarted when you move from one node to another node.

And yes this is considered a smooth transition.

This is how clustering works.

Tara Kizer
http://weblogs.sqlteam.com/tarad/

Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-06-20 : 16:33:41
Restarting sql resources will disconnect all processes.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-06-20 : 16:44:41
What is the error of your failing job?

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

dewacorp.alliances

452 Posts

Posted - 2007-06-20 : 16:51:05
It's actually not failing. It's said CANCELLED. So SQL must terminate all jobs. That's interesting.





Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-06-20 : 17:12:53
Well of course because the agent service restarts too. The agent is a dependency, so when the main service stops, the agent must stop too. That's how dependencies work.

You could setup your job to start automatically when the agent service starts.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

dewacorp.alliances

452 Posts

Posted - 2007-06-20 : 19:15:10
Hi Tara

How about if the other machine have a connection into that SQL Cluster (during this moving groups)? Does this means it has a potential few seconds lost connectivity then?

Thanks


quote:
Originally posted by tkizer

Well of course because the agent service restarts too. The agent is a dependency, so when the main service stops, the agent must stop too. That's how dependencies work.

You could setup your job to start automatically when the agent service starts.

Tara Kizer
http://weblogs.sqlteam.com/tarad/

Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-06-20 : 19:25:50
Everything will lose connectivity to SQL Server when the resources are moved. And this isn't cluster specific. The same thing happens on stand alone servers. The whole point is that the service is stopping and then starting.

And the move usually takes around 30 seconds. It has taken 5 minutes on my systems occassionally though.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page
   

- Advertisement -