October 4, 2007 at 7:28 am
I am rolling out a w2k3 ent cluster with sql2005 ent. and a 3rd party product. This is my first implementation of a sql2005 cluster.
I have 3 questions
1: I was told by the vendor to install with sql2005 sp1. I was also told you need to install integration services for the maintenance plans . Do I really need to do that ?? The app does not require SSIS and I prefer running SSIS on its own server.
2: If I do install SSIS on the cluster when I do the install do I select SSIS and just install it on one node ?? It is not cluster aware.
3: Is it true I must have a domain Windows Group ?? I guess I add the domain account for the services to that group ??
Any input would be helpful.
October 4, 2007 at 7:56 am
71 camaro (10/4/2007)
1: I was told by the vendor to install with sql2005 sp1. I was also told you need to install integration services for the maintenance plans . Do I really need to do that ?? The app does not require SSIS and I prefer running SSIS on its own server.
2: If I do install SSIS on the cluster when I do the install do I select SSIS and just install it on one node ?? It is not cluster aware.
3: Is it true I must have a domain Windows Group ?? I guess I add the domain account for the services to that group ??
1. SSIS is required for maintenance plans. Maintenance plans are not an SSIS package. However, if you don't want to install SSIS, you can build SQL jobs which execute the T-SQL statements for most of the maintenance plan options.
2. When you do the install, the installation application will ensure it installs on all nodes. This is required because any node which SSIS isn't installed on can't execute a maintenance plan.
3. Yes, several actually. This is because with SQL Server 2005 file and registry permissions are assigned to the groups. This means that when you have to change out a service account (if you have to change out a service account), you don't have old permissions left behind that have to be cleaned out manually. On a non-clustered SQL Server 2005 install the groups are created locally. However, groups that are local to one server cannot be used by another server. Therefore, for a clustered install, the groups must be domain groups. You may want to refer to the following KB article before beginning your cluster install:
K. Brian Kelley
@kbriankelley
October 4, 2007 at 7:57 am
The words "are not an SSIS package" should read "are now an SSIS package."
K. Brian Kelley
@kbriankelley
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply