Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.

Just a shot in the dark here. Are you using AWE on a 32-bit box? If so,
could you check the BOOT.INI file on each box and ensure that /PAE is in
both?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"M Bourgon" <bourgon (AT) gmail (DOT) com> wrote

Howdy. I'm running an Active/Active cluster on a SQL Server 2005
cluster. Both have identical hardware, and obviously the same disks.
One really odd thing I'm seeing, though: the first Active node,
running on the first box, sucks. When trying to connect, list SPs,
"wait 2 minutes to view a job",etc. However, when we recently ran
both instances on the second box, the performance seems much snappier.

Where should I be looking to try and figure out what's causing this?
Neither node is running extra software the other isn't. But
something's going on.

Thanks.