![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
"Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:%2362fRGJBKHA.4560 (AT) TK2MSFTNGP05 (DOT) phx.gbl... That is a valid scenario. Personally, I prefer having the DTC resource inside the SQL Application or Service. That way there is always a DTC resource local to the instance. Thta cuts down on unnecessary inter-node traffic. The advantage of a dedicated MSDTC resource is you can put it on a more lightly loaded node in a multi-node cluster. That is only important if there is a very large DTC load. To expand on what Geoff said, with SQL 2008 and Windows 2008, it is also possible to have multiple MSDTC resources so a separate MSDTC resource can be used for each SQL instance. As SQL fails over or is moved to another node, it can bring along its MSDTC friend. |
#12
| |||
| |||
|
|
It Depends. As long as the instance count is less than 2x the node count, ine MSDTC per Instance is a good setting. Over that, you will get better resource management with one MSDTC instance per node. GNH "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:0B3EE5E5-4F46-4FAC-91E7-84B6CAE54534 (AT) microsoft (DOT) com... Ok Great, But in a cluster with more than one SQL instance makes sence to have one MSDTC per SQL Cluster Instance, or have only one MSDTC in a dedicated resource? Thank you. "Geoff N. Hiten" wrote: That is a valid scenario. Personally, I prefer having the DTC resource inside the SQL Application or Service. That way there is always a DTC resource local to the instance. Thta cuts down on unnecessary inter-node traffic. The advantage of a dedicated MSDTC resource is you can put it on a more lightly loaded node in a multi-node cluster. That is only important if there is a very large DTC load. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:7CD1899D-DD75-4FF9-9AC8-09AB26182B09 (AT) microsoft (DOT) com... Hi Geoff, Almost done ![]() I've one more question if you don't mind. The MSDTC is assigned to my cluster name and IPAddress, but after some additional reading, I read that in some scenarios the DTC Disk resource is configured outside of the SQL Resource group??!!!! My DTC configuration is using the Network name and ip address of the SQL cluster, and I assigned a Disk resource that is also inside the same SQL Resource Group, should I place the MSDTC Disk resource in a dedicated Resource group? If yes, what are the advantages? Thank you again. "John" wrote: Okay, thanks, I'll give it a try and post the results. Thank you for your help. "Geoff N. Hiten" wrote: Inline. "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:9708AC01-73C3-4563-B2DE-C474A8B333C4 (AT) microsoft (DOT) com... Hi Geoff and thank you for your response. Okay, I read your article, if I understand your thoughts correctly: - MSDTC should be in each Cluster group for each instance of SQL (does this apply to both SQL 2005 and 2008 right?). Yes. I wrote that post before SQL 2008, but the same thought process and rules apply. -MSDTC should use the VS name and IP address that was used in that Cluster group (I mean, you can associate to the networkname and ipaddress that's being used to SQL server as long as you don't associate with SQL server resources, right?) Exactly. This is to prevent problems during subsequent SQL Updates. To install SQL 2008, I'm following the KB 955392 to slipstream SP1 and Update the SQL Server 2008 Setup support files. You can slipstream or pre-patch. Your choice. You say that I need to start with integrated installation? What option is that? "Installation" menu or Advanced menu? Do I need to run in both nodes or just one? In SQL 2005 I needed to create a Cluster group with at least one disk resource in it, is this still true for SQL 2008? You start off by building the "base" node. After that you add to the existing SQL cluster. Very similar to how yoo build a cluster in the first place. Thank you for your time and patience ![]() You are welcome. "Geoff N. Hiten" wrote: Advanced is for sysprepped installations that will be duplicated many times. You need to start with Integrted installation. Before you start, you need to download and run SQL 2008 SP1. This will patch the installation script, which has some cluster-related bugs in the RTM version. You will still need to apply SP1 after the regular installation, since the "pre-patch" only fixes the install script. Here is the official support policy for mixed version clusters: http://support.microsoft.com/kb/327518 Here are my thoughts on MSDTC and Windows 2008 clustering. http://weblogs.sqlteam.com/geoffh/ar...-Clusters.aspx Hope this helps -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:132EA13B-1175-451A-8806-8D51D02C852B (AT) microsoft (DOT) com... Hello Everyone, I'm trying to setup a 2 node SQL 2008 failover cluster in windows 2008 (2 instances). After reading some documentation, I'm confused about the right path to follow. I read that are 2 installation methods, Integrated and Advanced. When I start the DVD I select "Installation" and I have the option "New SQL Server failover cluster installation".???!!! If I go to "Advanced" menu, I have "advanced cluster preparation" and "Advanced cluster completion"??!! What should I use? Should I run advanced cluster preparation" on both nodes an them "Advanced cluster completion" on both nodes as well???!!! Can anyone point me the right direction to start with? Another question is related with having SQL 2008 in a cluster where SQL 2005 is already installed, is this supported? What precautions should I have in a scenario like this one? At last, Windows 2008 supports multiple instances of MSDTC. Assuming the SQL 2008 and SQL 2005 in a 2 node failover cluster, what is the right way to setup MSDTC? Should I create a separate cluster group for MSDTC for each instance of SQL? Or should I integrate a separate MSDTC cluster reasource in each SQL cluster group?? Thank you for your time. |
#13
| |||
| |||
|
|
Okay, So, if I understand correctly, in a cluster with 2 nodes 2 instances of SQL 2005 (active in node1) + 2 Instances of SQL 2008 (active in node2) In a scenario like this one, the best is to have 4 MSDTC instances, one for each SQL instance, is this correct? --------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- "Geoff N. Hiten" wrote: It Depends. As long as the instance count is less than 2x the node count, ine MSDTC per Instance is a good setting. Over that, you will get better resource management with one MSDTC instance per node. GNH "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:0B3EE5E5-4F46-4FAC-91E7-84B6CAE54534 (AT) microsoft (DOT) com... Ok Great, But in a cluster with more than one SQL instance makes sence to have one MSDTC per SQL Cluster Instance, or have only one MSDTC in a dedicated resource? Thank you. "Geoff N. Hiten" wrote: That is a valid scenario. Personally, I prefer having the DTC resource inside the SQL Application or Service. That way there is always a DTC resource local to the instance. Thta cuts down on unnecessary inter-node traffic. The advantage of a dedicated MSDTC resource is you can put it on a more lightly loaded node in a multi-node cluster. That is only important if there is a very large DTC load. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:7CD1899D-DD75-4FF9-9AC8-09AB26182B09 (AT) microsoft (DOT) com... Hi Geoff, Almost done ![]() I've one more question if you don't mind. The MSDTC is assigned to my cluster name and IPAddress, but after some additional reading, I read that in some scenarios the DTC Disk resource is configured outside of the SQL Resource group??!!!! My DTC configuration is using the Network name and ip address of the SQL cluster, and I assigned a Disk resource that is also inside the same SQL Resource Group, should I place the MSDTC Disk resource in a dedicated Resource group? If yes, what are the advantages? Thank you again. "John" wrote: Okay, thanks, I'll give it a try and post the results. Thank you for your help. "Geoff N. Hiten" wrote: Inline. "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:9708AC01-73C3-4563-B2DE-C474A8B333C4 (AT) microsoft (DOT) com... Hi Geoff and thank you for your response. Okay, I read your article, if I understand your thoughts correctly: - MSDTC should be in each Cluster group for each instance of SQL (does this apply to both SQL 2005 and 2008 right?). Yes. I wrote that post before SQL 2008, but the same thought process and rules apply. -MSDTC should use the VS name and IP address that was used in that Cluster group (I mean, you can associate to the networkname and ipaddress that's being used to SQL server as long as you don't associate with SQL server resources, right?) Exactly. This is to prevent problems during subsequent SQL Updates. To install SQL 2008, I'm following the KB 955392 to slipstream SP1 and Update the SQL Server 2008 Setup support files. You can slipstream or pre-patch. Your choice. You say that I need to start with integrated installation? What option is that? "Installation" menu or Advanced menu? Do I need to run in both nodes or just one? In SQL 2005 I needed to create a Cluster group with at least one disk resource in it, is this still true for SQL 2008? You start off by building the "base" node. After that you add to the existing SQL cluster. Very similar to how yoo build a cluster in the first place. Thank you for your time and patience ![]() You are welcome. "Geoff N. Hiten" wrote: Advanced is for sysprepped installations that will be duplicated many times. You need to start with Integrted installation. Before you start, you need to download and run SQL 2008 SP1. This will patch the installation script, which has some cluster-related bugs in the RTM version. You will still need to apply SP1 after the regular installation, since the "pre-patch" only fixes the install script. Here is the official support policy for mixed version clusters: http://support.microsoft.com/kb/327518 Here are my thoughts on MSDTC and Windows 2008 clustering. http://weblogs.sqlteam.com/geoffh/ar...-Clusters.aspx Hope this helps -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:132EA13B-1175-451A-8806-8D51D02C852B (AT) microsoft (DOT) com... Hello Everyone, I'm trying to setup a 2 node SQL 2008 failover cluster in windows 2008 (2 instances). After reading some documentation, I'm confused about the right path to follow. I read that are 2 installation methods, Integrated and Advanced. When I start the DVD I select "Installation" and I have the option "New SQL Server failover cluster installation".???!!! If I go to "Advanced" menu, I have "advanced cluster preparation" and "Advanced cluster completion"??!! What should I use? Should I run advanced cluster preparation" on both nodes an them "Advanced cluster completion" on both nodes as well???!!! Can anyone point me the right direction to start with? Another question is related with having SQL 2008 in a cluster where SQL 2005 is already installed, is this supported? What precautions should I have in a scenario like this one? At last, Windows 2008 supports multiple instances of MSDTC. Assuming the SQL 2008 and SQL 2005 in a 2 node failover cluster, what is the right way to setup MSDTC? Should I create a separate cluster group for MSDTC for each instance of SQL? Or should I integrate a separate MSDTC cluster reasource in each SQL cluster group?? Thank you for your time. |
#14
| |||
| |||
|
|
That is one valid configuration, especially if you plan to add nodes later. I have no problems with that option. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:203EBA73-D0B3-4C84-9467-295046FA0CAC (AT) microsoft (DOT) com... Okay, So, if I understand correctly, in a cluster with 2 nodes 2 instances of SQL 2005 (active in node1) + 2 Instances of SQL 2008 (active in node2) In a scenario like this one, the best is to have 4 MSDTC instances, one for each SQL instance, is this correct? --------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- "Geoff N. Hiten" wrote: It Depends. As long as the instance count is less than 2x the node count, ine MSDTC per Instance is a good setting. Over that, you will get better resource management with one MSDTC instance per node. GNH "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:0B3EE5E5-4F46-4FAC-91E7-84B6CAE54534 (AT) microsoft (DOT) com... Ok Great, But in a cluster with more than one SQL instance makes sence to have one MSDTC per SQL Cluster Instance, or have only one MSDTC in a dedicated resource? Thank you. "Geoff N. Hiten" wrote: That is a valid scenario. Personally, I prefer having the DTC resource inside the SQL Application or Service. That way there is always a DTC resource local to the instance. Thta cuts down on unnecessary inter-node traffic. The advantage of a dedicated MSDTC resource is you can put it on a more lightly loaded node in a multi-node cluster. That is only important if there is a very large DTC load. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:7CD1899D-DD75-4FF9-9AC8-09AB26182B09 (AT) microsoft (DOT) com... Hi Geoff, Almost done ![]() I've one more question if you don't mind. The MSDTC is assigned to my cluster name and IPAddress, but after some additional reading, I read that in some scenarios the DTC Disk resource is configured outside of the SQL Resource group??!!!! My DTC configuration is using the Network name and ip address of the SQL cluster, and I assigned a Disk resource that is also inside the same SQL Resource Group, should I place the MSDTC Disk resource in a dedicated Resource group? If yes, what are the advantages? Thank you again. "John" wrote: Okay, thanks, I'll give it a try and post the results. Thank you for your help. "Geoff N. Hiten" wrote: Inline. "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:9708AC01-73C3-4563-B2DE-C474A8B333C4 (AT) microsoft (DOT) com... Hi Geoff and thank you for your response. Okay, I read your article, if I understand your thoughts correctly: - MSDTC should be in each Cluster group for each instance of SQL (does this apply to both SQL 2005 and 2008 right?). Yes. I wrote that post before SQL 2008, but the same thought process and rules apply. -MSDTC should use the VS name and IP address that was used in that Cluster group (I mean, you can associate to the networkname and ipaddress that's being used to SQL server as long as you don't associate with SQL server resources, right?) Exactly. This is to prevent problems during subsequent SQL Updates. To install SQL 2008, I'm following the KB 955392 to slipstream SP1 and Update the SQL Server 2008 Setup support files. You can slipstream or pre-patch. Your choice. You say that I need to start with integrated installation? What option is that? "Installation" menu or Advanced menu? Do I need to run in both nodes or just one? In SQL 2005 I needed to create a Cluster group with at least one disk resource in it, is this still true for SQL 2008? You start off by building the "base" node. After that you add to the existing SQL cluster. Very similar to how yoo build a cluster in the first place. Thank you for your time and patience ![]() You are welcome. "Geoff N. Hiten" wrote: Advanced is for sysprepped installations that will be duplicated many times. You need to start with Integrted installation. Before you start, you need to download and run SQL 2008 SP1. This will patch the installation script, which has some cluster-related bugs in the RTM version. You will still need to apply SP1 after the regular installation, since the "pre-patch" only fixes the install script. Here is the official support policy for mixed version clusters: http://support.microsoft.com/kb/327518 Here are my thoughts on MSDTC and Windows 2008 clustering. http://weblogs.sqlteam.com/geoffh/ar...-Clusters.aspx Hope this helps -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:132EA13B-1175-451A-8806-8D51D02C852B (AT) microsoft (DOT) com... Hello Everyone, I'm trying to setup a 2 node SQL 2008 failover cluster in windows 2008 (2 instances). After reading some documentation, I'm confused about the right path to follow. I read that are 2 installation methods, Integrated and Advanced. When I start the DVD I select "Installation" and I have the option "New SQL Server failover cluster installation".???!!! If I go to "Advanced" menu, I have "advanced cluster preparation" and "Advanced cluster completion"??!! What should I use? Should I run advanced cluster preparation" on both nodes an them "Advanced cluster completion" on both nodes as well???!!! Can anyone point me the right direction to start with? Another question is related with having SQL 2008 in a cluster where SQL 2005 is already installed, is this supported? What precautions should I have in a scenario like this one? At last, Windows 2008 supports multiple instances of MSDTC. Assuming the SQL 2008 and SQL 2005 in a 2 node failover cluster, what is the right way to setup MSDTC? Should I create a separate cluster group for MSDTC for each instance of SQL? Or should I integrate a separate MSDTC cluster reasource in each SQL cluster group?? Thank you for your time. |
#15
| |||
| |||
|
|
I was thinking about having those 4 SQL instances in both nodes, do you think that is a bad option? SQL 2005 will have 2 instances, one PROD and one DEV, the same apply to SQL 2008. Of course if one node fails the other must be able to do the job for the 4 SQL instances... Perhaps I'm asking to much of it? "Geoff N. Hiten" wrote: That is one valid configuration, especially if you plan to add nodes later. I have no problems with that option. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:203EBA73-D0B3-4C84-9467-295046FA0CAC (AT) microsoft (DOT) com... Okay, So, if I understand correctly, in a cluster with 2 nodes 2 instances of SQL 2005 (active in node1) + 2 Instances of SQL 2008 (active in node2) In a scenario like this one, the best is to have 4 MSDTC instances, one for each SQL instance, is this correct? --------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- "Geoff N. Hiten" wrote: It Depends. As long as the instance count is less than 2x the node count, ine MSDTC per Instance is a good setting. Over that, you will get better resource management with one MSDTC instance per node. GNH "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:0B3EE5E5-4F46-4FAC-91E7-84B6CAE54534 (AT) microsoft (DOT) com... Ok Great, But in a cluster with more than one SQL instance makes sence to have one MSDTC per SQL Cluster Instance, or have only one MSDTC in a dedicated resource? Thank you. "Geoff N. Hiten" wrote: That is a valid scenario. Personally, I prefer having the DTC resource inside the SQL Application or Service. That way there is always a DTC resource local to the instance. Thta cuts down on unnecessary inter-node traffic. The advantage of a dedicated MSDTC resource is you can put it on a more lightly loaded node in a multi-node cluster. That is only important if there is a very large DTC load. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:7CD1899D-DD75-4FF9-9AC8-09AB26182B09 (AT) microsoft (DOT) com... Hi Geoff, Almost done ![]() I've one more question if you don't mind. The MSDTC is assigned to my cluster name and IPAddress, but after some additional reading, I read that in some scenarios the DTC Disk resource is configured outside of the SQL Resource group??!!!! My DTC configuration is using the Network name and ip address of the SQL cluster, and I assigned a Disk resource that is also inside the same SQL Resource Group, should I place the MSDTC Disk resource in a dedicated Resource group? If yes, what are the advantages? Thank you again. "John" wrote: Okay, thanks, I'll give it a try and post the results. Thank you for your help. "Geoff N. Hiten" wrote: Inline. "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:9708AC01-73C3-4563-B2DE-C474A8B333C4 (AT) microsoft (DOT) com... Hi Geoff and thank you for your response. Okay, I read your article, if I understand your thoughts correctly: - MSDTC should be in each Cluster group for each instance of SQL (does this apply to both SQL 2005 and 2008 right?). Yes. I wrote that post before SQL 2008, but the same thought process and rules apply. -MSDTC should use the VS name and IP address that was used in that Cluster group (I mean, you can associate to the networkname and ipaddress that's being used to SQL server as long as you don't associate with SQL server resources, right?) Exactly. This is to prevent problems during subsequent SQL Updates. To install SQL 2008, I'm following the KB 955392 to slipstream SP1 and Update the SQL Server 2008 Setup support files. You can slipstream or pre-patch. Your choice. You say that I need to start with integrated installation? What option is that? "Installation" menu or Advanced menu? Do I need to run in both nodes or just one? In SQL 2005 I needed to create a Cluster group with at least one disk resource in it, is this still true for SQL 2008? You start off by building the "base" node. After that you add to the existing SQL cluster. Very similar to how yoo build a cluster in the first place. Thank you for your time and patience ![]() You are welcome. "Geoff N. Hiten" wrote: Advanced is for sysprepped installations that will be duplicated many times. You need to start with Integrted installation. Before you start, you need to download and run SQL 2008 SP1. This will patch the installation script, which has some cluster-related bugs in the RTM version. You will still need to apply SP1 after the regular installation, since the "pre-patch" only fixes the install script. Here is the official support policy for mixed version clusters: http://support.microsoft.com/kb/327518 Here are my thoughts on MSDTC and Windows 2008 clustering. http://weblogs.sqlteam.com/geoffh/ar...-Clusters.aspx Hope this helps -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "John" <John (AT) discussions (DOT) microsoft.com> wrote in message news:132EA13B-1175-451A-8806-8D51D02C852B (AT) microsoft (DOT) com... Hello Everyone, I'm trying to setup a 2 node SQL 2008 failover cluster in windows 2008 (2 instances). After reading some documentation, I'm confused about the right path to follow. I read that are 2 installation methods, Integrated and Advanced. When I start the DVD I select "Installation" and I have the option "New SQL Server failover cluster installation".???!!! If I go to "Advanced" menu, I have "advanced cluster preparation" and "Advanced cluster completion"??!! What should I use? Should I run advanced cluster preparation" on both nodes an them "Advanced cluster completion" on both nodes as well???!!! Can anyone point me the right direction to start with? Another question is related with having SQL 2008 in a cluster where SQL 2005 is already installed, is this supported? What precautions should I have in a scenario like this one? At last, Windows 2008 supports multiple instances of MSDTC. Assuming the SQL 2008 and SQL 2005 in a 2 node failover cluster, what is the right way to setup MSDTC? Should I create a separate cluster group for MSDTC for each instance of SQL? Or should I integrate a separate MSDTC cluster reasource in each SQL cluster group?? Thank you for your time. |
![]() |
| Thread Tools | |
| Display Modes | |
| |