Hi all! I am designing a virtualized "Always On" solution for a client using
SQL2k8 (Edition TBD) + Win2k8 Hyper-V.

I will have 8 boxes conforming a Windows 2008 Cluster where my VMs will be
hosted as a High Available service featuring Quick Migration. Now I need to
know how to provide HA to my virtulized SQL Server Service.

Is there any recommended reading regarding this? I have read many about SQL
virtualization but nothing about a HA environment.

My approach would be:
- Create 2 SQL VMs (SQL1, SQL2) hosted on different boxes (Host1, Host2).
- Host1 and Host2 are members of my Win2k8 Cluster
- Create a Fail-over cluster between SQL1 (active node) and SQL2.

Disaster
- SQL1 fails -> SQL Fail-over cluster moves control to the passive node
until recovery.
- Host1 fails -> Win2k8 Fail-over starts the VM on a Host3 and while Quick
migration takes place SQL Fail-over cluster moves control to the passive
node

Hi

We have an application running on an NLB cluster in the DMZ.
Application data is stored on a standalone SQL 2005 Std server located
not in the DMZ but inside the company's private network. Have
recently setup a 2-node SQL 2005 Std failover cluster running on
Windows 2008 Ent, all 64-bit and in the process of pointing the
application to it.

For some reason I'm having problems connecting to the new cluster.
Have tried allowing all traffic thru the firewall between dmz and
trust zones but no luck. I can ping the SQL cluster as well as the
standalone SQL server from the DMZ and vice versa, but can only get a
successful test ODBC connection to the standalone server.

Windows firewall already disabled on the SQL cluster and no antivirus
is installed. Any ideas?

Thanks
TI

Hi,

We are currently looking at setting up 3-Node Cluster with
Active/Active/Passive configuration. I am sorry clustering is my weakness
and I not very good at it, so if the question sounds wrong please let me know.

Configuration we are aiming for (Configuration A):
Node 1: Default Instance (SQL2005) and Named Instance (NI01)
-> Set to Fail Over to Node 3
Node 2: Default Instance (SQL2005) and Named Instance (NI01)
-> Set to Fail Over to Node 3

Configuration I was thinking we should do (Configruation B):
Node 1: Default Instance (SQL2005
-> Set Fail Over to Node 3
Node 2: Named Instance (NI01)
-> Set Fail Over to Node 3

Could someone please tell me if Configuration A is possible? Or do we have
to choose Configuration B as main route?

Thanks.

Hi guys,

Please, how can I write, after clustering process, the final clusters in a
table?

Best,

My 2 -node sql clusters (active/passive) rebooted today because of power
failure. When they came up SQL server agent is showing online pending status
when I check it from cluster admin. I restarted the server again one at a
time thinking that may be there was some resource conflict but that did not
help. When I check sql server agent service on the active node through
service manager, Its showing STARTED. Is there anything I could try? I am not
sure if it will affect the clutser in the long run and put the sql server
service offline.

I will appreciate any input.

I'm trying to install SQL Server 2005 on a one-node Windows Server 2008
failover clustering, but I'm getting the following error message:

"The drive specified cannot be used for program location. Program files must
be installed on a valid local disk available on all cluster nodes. The valid
values are"

No drive is shown.

I found a Microsoft article about the problem:
http://support.microsoft.com/kb/913815.
But even using an administrator account the problem happens.
Has anybody already faced this kind of problem?

Thanks,

Felipe

Hi,
Is SQL2000 supported on a 64-bit Windows 2008 cluster?
These are not Itanium processors, AMD I think.
We just want to run it on there for a few months while migrations to SQL
2005 are going on, then uninstall SQL2000 when the migrations are
finished.

This cluster will also have 2 instances of SQL2005.

Thanks.

Hi,

I tested a failover cluster solution with Windows 2003 and SQL Server 2005
using 2 nodes with optimal result. Now I'm interested to add a third node
and see what happens, but before that I have some questions.

1 - How nodes will work in case of failover?, will use a round robin
schema?, a random schema?, or always node 1 will failover to node 2 and only
if this is down will failover to node 3.

2 - There's any option to create a cluster where only two nodes will
failover automatically and the third manually?, we're thinking on this option
to have a node remote and only put online if local cluster is unavailable.
In this schema we'll only use the virtual sql name capability of cluster and
not the failover automatically.

3 - More generally, I think that when enough resources is better to have
more instances of SQL in the same machine for differents applications than to
have only one instance with several databases, I'm thinking in HA when one of
the applications generate that SQL Server use a lot of SQL cycles, a lot of
memory or the tempdb heavily. What do you think?

Thx,

Hi All,
Currently, our Prod databases located in the 3 SQL instances on the 2
physical nodes cluster servers. I need add three new (powerful) nodes to
existing 3 instances. These instances installed SQL Server 2005 Enterprise
Edition with Post SP2 (3161) version. For the security purpose, I change the
sa password regularly.
Now, I have two following questions:
1) If I use sa account to add those 3 new nodes, will be any problem occur
since sa password changed?
2) What kind procedures (processes) I can follow to add those new nodes?
Regards!
Chen