Showing posts with label active. Show all posts
Showing posts with label active. Show all posts

Friday, March 23, 2012

problem in Active / Active clustering

Is active/active clustering is also have load balancing . In Active/ Active
clustering both the node acces the same database or differnt database , In
active/active clustering does the cpu and memory are share by both nodes ?
Please clarify the doubts.
> Is active/active clustering is also have load balancing.
No, it's not for dynamic load balancing, though some may argue that since
you amy be able to distribute your load among the instances in the cluster,
there is some kind of static load balancing. That's really a stretch. SQL
Server clustering is just for high availability.

> In Active/ Active clustering both the node acces the same database
> or differnt database
No two nodes can access the same database at the same time in SQL Server
clustering. This is because Microsoft Cluster Server (on which SQL Server
clustering is built) is designed to allow only one node to have access to a
disk at any given time.

> In active/active clustering does the cpu and memory are share by both
> nodes ?
There is no sharing of cpu or memory. Actually, nothing is shared among the
nodes. You may see terms such as 'shared disk'. That just means that the
disk can be accessed by different nodes (but not at the same time). SQL
Server clustering (or more generally Microsoft Cluster Server) is built on
the shared-nothing model.
SQL Server Books Online has plenty of info on this subject in greater
details. So I'd recommend reading BOL.
Linchi
"sunil" <sunil@.discussions.microsoft.com> wrote in message
news:599435BB-2FE8-4247-BC3A-F92A52FB236F@.microsoft.com...
> Is active/active clustering is also have load balancing . In Active/
> Active
> clustering both the node acces the same database or differnt database ,
> In
> active/active clustering does the cpu and memory are share by both nodes ?
>
> Please clarify the doubts.
>
>
|||Hi Linchi,
Thanks a lot all the doubts have been clarified.Do u have any good white
papaer
Regards
Sunil
"Linchi Shea" wrote:

> No, it's not for dynamic load balancing, though some may argue that since
> you amy be able to distribute your load among the instances in the cluster,
> there is some kind of static load balancing. That's really a stretch. SQL
> Server clustering is just for high availability.
>
> No two nodes can access the same database at the same time in SQL Server
> clustering. This is because Microsoft Cluster Server (on which SQL Server
> clustering is built) is designed to allow only one node to have access to a
> disk at any given time.
>
> There is no sharing of cpu or memory. Actually, nothing is shared among the
> nodes. You may see terms such as 'shared disk'. That just means that the
> disk can be accessed by different nodes (but not at the same time). SQL
> Server clustering (or more generally Microsoft Cluster Server) is built on
> the shared-nothing model.
> SQL Server Books Online has plenty of info on this subject in greater
> details. So I'd recommend reading BOL.
> Linchi
> "sunil" <sunil@.discussions.microsoft.com> wrote in message
> news:599435BB-2FE8-4247-BC3A-F92A52FB236F@.microsoft.com...
>
>
|||This Microsoft whitepaper is worth reading.
http://www.microsoft.com/technet/pro.../failclus.mspx
Linchi
"sunil" <sunil@.discussions.microsoft.com> wrote in message
news:CFB5BA57-42DE-4C27-9CDA-D15CAE961665@.microsoft.com...[vbcol=seagreen]
> Hi Linchi,
> Thanks a lot all the doubts have been clarified.Do u have any good white
> papaer
>
> Regards
> Sunil
> "Linchi Shea" wrote:

Wednesday, March 7, 2012

Problem Creating Publisher

Hello there
I have server who is declered as publisher and distributore already, and i
have already active publisher
Now i'm trying to create new publish for another database.
I get error 14294: Supply either @.job_id or @.job_name ti identify job
Where can be the problem?
Hi Oded,
from the looks of previous posts on the problem this usually occurs if there
are improperly dropped old publications on the server, or possibly restored
databases that had been published.
One option to try is to drop all publications (you can script the existing
ones so you can recreate them with the script if you like - do that by right
clicking the publication name in Enterprise manager then choosing the Script
command) - completely remove publishing and distributing from the server
using the wizard, then put it all back again.

Mary Bray [SQL Server MVP]
Please reply only to newsgroups
"Oded Kovach" <roygoldh@.hotmail.com> wrote in message
news:e$WwxDH0EHA.1452@.TK2MSFTNGP11.phx.gbl...
> Hello there
> I have server who is declered as publisher and distributore already, and i
> have already active publisher
> Now i'm trying to create new publish for another database.
> I get error 14294: Supply either @.job_id or @.job_name ti identify job
> Where can be the problem?
>