none
SSIS的问题 RRS feed

  • 问题

  • 环境:windows 2003 EE+sqlserver 2005 cluster

    一共有2个问题:
    之前安装sqlserver服务的时候忘记选择SSIS服务了,现在是否可以单独安装?
    第二个:
    大家在sqlserver 2005 cluster上是怎么配置SSIS服务的?
    我在网上看了下,可以作为群集资源 也可以在每个单独的节点上安装SSIS服务。但是微软建议不作为群集资源。

    如果是采用两个节点都安装ssis服务,那么ssis的包两个节点是否会共享?
    第二:对日常的备份是否会有影响呢?

    2011年5月17日 7:23

全部回复

  • 没玩过

    SQL Server最基本的就是sql server engine服务,也是Cluster最基本的东东。

    因此,我理解应该是可以单独安装SSIS的,你查到的微软建议不也正说明这点么。另外,SSIS两个节点应该不会共享吧,你都没搞到Cluster,怎会共享呢。对日常的备份应该不会有影响,因为如果您做的是存储镜像备份,那备份是基于LUN的,如果是SQL Server的backup命令,则是基于SQL Server Engine的,和SSIS没什么关系。

    2011年5月17日 11:03
  • 没玩过

    SQL Server最基本的就是sql server engine服务,也是Cluster最基本的东东。

    因此,我理解应该是可以单独安装SSIS的,你查到的微软建议不也正说明这点么。另外,SSIS两个节点应该不会共享吧,你都没搞到Cluster,怎会共享呢。对日常的备份应该不会有影响,因为如果您做的是存储镜像备份,那备份是基于LUN的,如果是SQL Server的backup命令,则是基于SQL Server Engine的,和SSIS没什么关系。

     

    但是如果我采用维护计划进行备份,那么就跟SSIS有关了.


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月17日 13:09
  • 环境:windows 2003 EE+sqlserver 2005 cluster

    一共有2个问题:
    之前安装sqlserver服务的时候忘记选择SSIS服务了,现在是否可以单独安装?
    第二个:
    大家在sqlserver 2005 cluster上是怎么配置SSIS服务的?
    我在网上看了下,可以作为群集资源 也可以在每个单独的节点上安装SSIS服务。但是微软建议不作为群集资源。

    如果是采用两个节点都安装ssis服务,那么ssis的包两个节点是否会共享?
    第二:对日常的备份是否会有影响呢?

    1. Yes, you can add it.

    2. Install ssis on every node in the cluster as local service, then modify c:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml and restart ssis on each node as follow:

    change <ServerName>.</ServerName> to <ServerName>SQL_instance_name</ServerName>

    2011年5月17日 13:27
  • 假如我在一个节点上部署了一个package,定期处理数据,当发生故障转移的时候 是不是也要手动建立到另外一个节点上?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 0:33
  • 环境:windows 2003 EE+sqlserver 2005 cluster

    一共有2个问题:
    之前安装sqlserver服务的时候忘记选择SSIS服务了,现在是否可以单独安装?
    第二个:
    大家在sqlserver 2005 cluster上是怎么配置SSIS服务的?
    我在网上看了下,可以作为群集资源 也可以在每个单独的节点上安装SSIS服务。但是微软建议不作为群集资源。

    如果是采用两个节点都安装ssis服务,那么ssis的包两个节点是否会共享?
    第二:对日常的备份是否会有影响呢?

    1. Yes, you can add it.

    2. Install ssis on every node in the cluster as local service, then modify c:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml and restart ssis on each node as follow:

    change <ServerName>.</ServerName> to <ServerName>SQL_instance_name</ServerName>


    关于第二点,

    你说 

    change <ServerName>.</ServerName> to  <ServerName>ServerName\InstanceName</ServerName>
    后面的SQL_instance_name是不是安装的sqlserver cluster的虚拟实例名称?

    比如:我的windows cluster的名称是AAA,然后SQLServer的实例名称是SQL2005.

    那么这里应该修改成 <ServerName>AAA\SQL2005</ServerName>   ?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 0:37
  • That's correct.
    2011年5月18日 1:22
  • 假如我在一个节点上部署了一个package,定期处理数据,当发生故障转移的时候 是不是也要手动建立到另外一个节点上?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    You can deploy package to sql server, always be there as long as sql is running. 
    2011年5月18日 1:24
  • 假如我在一个节点上部署了一个package,定期处理数据,当发生故障转移的时候 是不是也要手动建立到另外一个节点上?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    You can deploy package to sql server, always be there as long as sql is running. 

     

    我这边是这样部署包的。给你讲一下,你看下是否OK。

    首先使用SQL Server BIDS建立一个package,然后选择‘文件’>'save copy of package. dtsx As ...',然后就可以保存到SSIS 服务下的‘Stored packages’里。

    之后可以在Job中设置运行这个package。

    那么当SQL Engine转移之后,这个是否可以同步过去?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 2:16
  • You can deploy it to shared disk on the cluster.
    2011年5月18日 2:36
  • when i install SSIS service locally, will it stop the sqlserver engine service of the cluster?

     

    For your suggestion,i have the detailed steps:

    1:install SSIS service separately on each node

    2:modify the ssis configuration xml file MsDtsSrvr.ini.xml

    from <ServerName>.</ServerName>  to <ServerName>.CLUSTERNAME\SQL NETWORK NAME</ServerName>

    then i can create ssis package and store it in the cluster physical disk.

    so i can run the package no matter which node is the active one.

     

    Right?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 3:38
  • Should be:

    1:install SSIS service separately on each node, it will not stop sql service.

    2:modify the ssis configuration xml file MsDtsSrvr.ini.xml then restarts ssis service

    from <ServerName>.</ServerName>  to <ServerName>CLUSTERNAME\SQL NETWORK NAME</ServerName>

    Then you can create ssis package and store it in the cluster physical disk in sql resource group.

    2011年5月18日 3:47
  • OK  .

    thanks rmiao, you are so kindly...

     


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 3:54
  • I installed the SSIS service on the  inactive node and it succeed.

    but when i install SSIS service on the active node,it fail......

    and i can connect the ssis service on the inactive node.

    but no ssis service on the active node.

    Does it need to do failover then install ssis service on the original active node?


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    • 已编辑 Wison-Ho 2011年5月18日 4:03
    2011年5月18日 4:02
  • Check log files for reason.
    2011年5月18日 4:03
  • it fail at "SQL Server is scanning my computer configuration"
    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 4:05

  • Microsoft SQL Server 2005 9.00.4035.00
    ==============================
    OS Version      : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)
    Time            : Wed May 18 12:09:04 2011
     
    NEOFISNODE2 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
    NEOFISNODE2 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.


     SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.


    Time            : Wed May 18 12:10:22 2011


    List of log files:
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_Core(Patched).log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_Datastore.xml
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_.NET Framework 2.0.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_Core.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_.NET Framework 2.0 LangPack.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_.NET Framework Upgrade Advisor.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_.NET Framework Upgrade Advisor LangPack.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_.NET Framework Windows Installer.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_.NET Framework Windows Installer LangPack.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_Support.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0011_NEOFISNODE2_SCC.log

     

    This is the log


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 4:30
  • I run the setup.exe with the parameter  SKUUPGRADE=1

    It failed again....

    the log for this time:


    Microsoft SQL Server 2005 9.00.4035.00
    ==============================
    OS Version      : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)
    Time            : Wed May 18 13:24:47 2011
     
    NEOFISNODE2 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.


     SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.


    Time            : Wed May 18 13:25:39 2011


    List of log files:
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_Core(Patched).log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_Datastore.xml
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_.NET Framework 2.0.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_Core.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_.NET Framework 2.0 LangPack.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_.NET Framework Upgrade Advisor.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_.NET Framework Upgrade Advisor LangPack.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_.NET Framework Windows Installer.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_.NET Framework Windows Installer LangPack.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_Support.log
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_NEOFISNODE2_SCC.log


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 5:23
  • after i do the failover,ssis service installed successfully on the current inactive node.

    It shows that we can install ssis service on inactive node.

    if wanna intall it on the active node,we should do failover firstly


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 6:46
  • 但是现在还遇到一个问题。

    我现在在两个节点都安装上了SSIS的服务。并且我连接的时候都是使用的是DB的网络名称或者本地的电脑名称都可以。而且也在两个节点上的SSIS的配置文件中修改

    <ServerName>.</ServerName>  到 <ServerName>.NEOCLUSTERDB\NEOFISDB</ServerName>

    其中NEOCLUSTERDB是cluster的名称,NEOFISDB是数据库的网络名称。
    并且也有重启两个节点的SSIS服务。


    但是发现在cluster中的SQL Cluster网络名称里面,不能创建维护计划。

    报错信息为:

     

    TITLE: Microsoft SQL Server Management Studio
    ------------------------------

    Method not found: 'Void Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'. (Microsoft.SqlServer.MaintenancePlanTasksUI)

    ------------------------------
    BUTTONS:

    OK
    ------------------------------


    另外,我现在显示是可以创建SSIS包,但是无法保存到CLUSTER数据库的SSIS的Saved packages目录下。
    当然可以保存到本地。但是在CLUSTER数据库的中新建Job来调用这个包,也执行不成功。

    请问应该怎么办啊?

     


    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
    2011年5月18日 7:23