| Groups | Blog | Home |
sql server clustering : 3 quick Qurestions about SQL
own name, IP and resources or just a good idea, I am planning on doing it, My last SQL cluster did not have one But I didn't build it. I just want to be sure. Second, When you create a SQL Cluster and use the default instance (MSSQLSERVER) where are the system databases physically located or placed by the install process. and Third, I plan on using "SHARED RESOURCES" that are currently attached to a single server and just move them to a new "Storage group" which contains my new Cluster nodes, This resources already contain all my production databases, When i try to attach them to my new SQL Cluster, Can I expect any issues?, My system )master, model....etc) databases are going to be rebuilt and the Instance name is the same as the old one (MSSQLSERVER) Thanks so much to everyone -- Scott A Cummins Sr. Systems Engineer Equity Analytics ( A division of Merrill Lynch) 14614 N. Keirland Blvd Scottsdale, AZ 85254
Geoff
Again, You have come through, I plan on doing it all that way, and Thanks again. I will make sure that when I am asked where to place my System Databases, I note it because the DBA's want to know exactly where it is -- Scott A Cummins Sr. Systems Engineer Equity Analytics ( A division of Merrill Lynch) 14614 N. Keirland Blvd Scottsdale, AZ 85254 480-998-3515 [quoted text, click to view] "Geoff N. Hiten" wrote:
> Comments Inline > > "Scott Cummins" <scummins@equitymethods.com> wrote in message > news:C508493B-E490-4B9A-855F-21359AEB4B0C@microsoft.com... > > First, Is it Necessary to create an MSDTC Group on your SQL Cluster with > > its > > own name, IP and resources or just a good idea, I am planning on doing it, > > My > > last SQL cluster did not have one But I didn't build it. I just want to be > > sure. > > > You don't have to, but configuring MSTDC on a cluster is a good idea. A > separate group is only necessary on systems with a lot of distributed > transactions. For most clusters, putting it in the cluster group is fine. > > > Second, When you create a SQL Cluster and use the default instance > > (MSSQLSERVER) where are the system databases physically located or placed > > by > > the install process. > > > They are placed on the designated cluster drive. > > > and Third, I plan on using "SHARED RESOURCES" that are currently attached > > to > > a single server and just move them to a new "Storage group" which contains > > my > > new Cluster nodes, This resources already contain all my production > > databases, When i try to attach them to my new SQL Cluster, Can I expect > > any > > issues?, My system )master, model....etc) databases are going to be > > rebuilt > > and the Instance name is the same as the old one (MSSQLSERVER) > > > Turn off all but one node. > Present the LUNs to the new node by changing the SAN storage group. > Make sure the new node cna see the LUNs. > Give the LUNs drive letters. > Create clustered disk resources that map to the new LUNs. > Move the resources into the SQL Resource Group. > Modify the dependencies for the SQL Service to be dependent on the new disk > resources > Now you can start the service and attach the files. > If Geoff ever ends up visiting Arizona or you end up visiting Atlanta, you > buy the beer. :) > > You will still need to reconcile users and logins. See > sp_change_users_login in BOL for details. > > -- > Geoff N. Hiten > Senior SQL Infrastructure Consultant > Microsoft SQL Server MVP > > > > > Thanks so much to everyone > > -- > > Scott A Cummins > > Sr. Systems Engineer > > Equity Analytics > > ( A division of Merrill Lynch) > > 14614 N. Keirland Blvd > > Scottsdale, AZ 85254 > > 480-998-3515 >
Comments Inline
[quoted text, click to view] "Scott Cummins" <scummins@equitymethods.com> wrote in message You don't have to, but configuring MSTDC on a cluster is a good idea. A news:C508493B-E490-4B9A-855F-21359AEB4B0C@microsoft.com... > First, Is it Necessary to create an MSDTC Group on your SQL Cluster with > its > own name, IP and resources or just a good idea, I am planning on doing it, > My > last SQL cluster did not have one But I didn't build it. I just want to be > sure. > separate group is only necessary on systems with a lot of distributed transactions. For most clusters, putting it in the cluster group is fine. [quoted text, click to view] > Second, When you create a SQL Cluster and use the default instance They are placed on the designated cluster drive.> (MSSQLSERVER) where are the system databases physically located or placed > by > the install process. > [quoted text, click to view] > and Third, I plan on using "SHARED RESOURCES" that are currently attached Turn off all but one node.> to > a single server and just move them to a new "Storage group" which contains > my > new Cluster nodes, This resources already contain all my production > databases, When i try to attach them to my new SQL Cluster, Can I expect > any > issues?, My system )master, model....etc) databases are going to be > rebuilt > and the Instance name is the same as the old one (MSSQLSERVER) > Present the LUNs to the new node by changing the SAN storage group. Make sure the new node cna see the LUNs. Give the LUNs drive letters. Create clustered disk resources that map to the new LUNs. Move the resources into the SQL Resource Group. Modify the dependencies for the SQL Service to be dependent on the new disk resources Now you can start the service and attach the files. If Geoff ever ends up visiting Arizona or you end up visiting Atlanta, you buy the beer. :) You will still need to reconcile users and logins. See sp_change_users_login in BOL for details. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP [quoted text, click to view] > Thanks so much to everyone
> -- > Scott A Cummins > Sr. Systems Engineer > Equity Analytics > ( A division of Merrill Lynch) > 14614 N. Keirland Blvd > Scottsdale, AZ 85254 > 480-998-3515
On most clusters, I end up changing tempdb file locations around but the
other files should be OK where they are. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP [quoted text, click to view] "Scott Cummins" <scummins@equitymethods.com> wrote in message
news:BAC1BCB4-9CA2-4C46-BA69-68E8C1A77A00@microsoft.com... > Geoff > > Again, You have come through, I plan on doing it all that way, and Thanks > again. > > I will make sure that when I am asked where to place my System Databases, > I > note it because the DBA's want to know exactly where it is > -- > Scott A Cummins > Sr. Systems Engineer > Equity Analytics > ( A division of Merrill Lynch) > 14614 N. Keirland Blvd > Scottsdale, AZ 85254 > 480-998-3515 > > > "Geoff N. Hiten" wrote: > >> Comments Inline >> >> "Scott Cummins" <scummins@equitymethods.com> wrote in message >> news:C508493B-E490-4B9A-855F-21359AEB4B0C@microsoft.com... >> > First, Is it Necessary to create an MSDTC Group on your SQL Cluster >> > with >> > its >> > own name, IP and resources or just a good idea, I am planning on doing >> > it, >> > My >> > last SQL cluster did not have one But I didn't build it. I just want to >> > be >> > sure. >> > >> You don't have to, but configuring MSTDC on a cluster is a good idea. A >> separate group is only necessary on systems with a lot of distributed >> transactions. For most clusters, putting it in the cluster group is >> fine. >> >> > Second, When you create a SQL Cluster and use the default instance >> > (MSSQLSERVER) where are the system databases physically located or >> > placed >> > by >> > the install process. >> > >> They are placed on the designated cluster drive. >> >> > and Third, I plan on using "SHARED RESOURCES" that are currently >> > attached >> > to >> > a single server and just move them to a new "Storage group" which >> > contains >> > my >> > new Cluster nodes, This resources already contain all my production >> > databases, When i try to attach them to my new SQL Cluster, Can I >> > expect >> > any >> > issues?, My system )master, model....etc) databases are going to be >> > rebuilt >> > and the Instance name is the same as the old one (MSSQLSERVER) >> > >> Turn off all but one node. >> Present the LUNs to the new node by changing the SAN storage group. >> Make sure the new node cna see the LUNs. >> Give the LUNs drive letters. >> Create clustered disk resources that map to the new LUNs. >> Move the resources into the SQL Resource Group. >> Modify the dependencies for the SQL Service to be dependent on the new >> disk >> resources >> Now you can start the service and attach the files. >> If Geoff ever ends up visiting Arizona or you end up visiting Atlanta, >> you >> buy the beer. :) >> >> You will still need to reconcile users and logins. See >> sp_change_users_login in BOL for details. >> >> -- >> Geoff N. Hiten >> Senior SQL Infrastructure Consultant >> Microsoft SQL Server MVP >> >> >> >> > Thanks so much to everyone >> > -- >> > Scott A Cummins >> > Sr. Systems Engineer >> > Equity Analytics >> > ( A division of Merrill Lynch) >> > 14614 N. Keirland Blvd >> > Scottsdale, AZ 85254 >> > 480-998-3515 >> >>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |