SSIS on Cluster also 2005 packages and 2008 db connections and jobs?

We have a SQL 2008 Cluster where we do not want to install SSIS. We have a SQL 2005 SSIS instance on another server for packages.

here goes

1. Can we configure jobs on the SQL 2008 custer to point to the 2005 SSIS instance? and do we need SSIS installed on the SQL 2008 cluster to do this?

2. Can we run jobs on a SQL 2005 instance, pointing to a SQL 2005 SSIS instance/packages on a third server that connect to a SQL 2008 DB instance . I know that sounds crazy, but where exactly is the CPU and memory load in that design.. job on one server,
package a seperate server and db on a third server.?

3. As mentioned, I have SQL 2005 SSIS instance. I have local admin on that server and can connect to the ssis instance from my sql 2005 sql client on my desktop. I added a new user to the server and added them to the SSIS and users group. I also
made sure they could write to the folder where they will deploy packages. However, they get some kind of access denied while trying to connect, unless I give them local admin on the server. What more access do they need than to be in the users and SSIS
group and have write access to an SSIS deployment folders?

My home machine has sql 2005ÃÂ and Visual Studio 2005 installed. I uninstalled VS 2005 (RTM)ÃÂ and installed VS 2008 (RTM) in its place. I then found that the SSIS templates were missing. Lesson: don't uninstall VS 2005 if you want to use SSIS 2005!

ÃÂ

1. Is there any "workaround" to this issue?

ÃÂ

2. (If the answer to 1 is "No")ÃÂ I willÃÂ install VS 2008 side-by-side with VS 2005 on the same box.ÃÂ When the SSIS issue is finally resolved, can I uninstall VS 2005 without doing damage to theÃÂ VS 2008 install?

I recently built a SQL Server 2005 cluster on the o/s Windows Server 2008 R2. I have been attempting to connect to the cluster from my Windows 7 dekstop with my SQL Server 2008 Tool set. I have been unable to attach to this cluster since its
creation. The firewall is temp off, remote connections in the surface area configuration is set to pipes and tcp/ip and the Browser surface is up and running.
I ran Wireshark against the cluster and I could see that there was UDP conversations for ms-sql-m (SQL Port) but that was as far as it would get. I am using a named instance so not using 1433, but I do see the cluster offering up high RPC ports but
the client never responds after the initial UDP response.
When I noticed that there was a two way conversation taking place, I went to a seperate machine and fired up SQL Server 2005 Tools and I was easily able to attach to the cluster. So my question is -
Are there any known incompatibilities between SQL Server 2005 cluster services and SQL Server 2008 Tool set? I can use my 2008 tools to attach to a non-clustered SQL Server 2005 w/o issue.
Error when attempting to connect:
A network-related or instance-specific error occured while establishing a connection to sql server. The server was not found or was not accessible. Verify that the instance name is correct and the SQL Server is con

I've read the old posts about having to have the BIDS version match the SSIS package version. My question is with VS2010 is there any change? Can I edit either of the old versions of SSIS packages in VS2010 or do I have to have 3 versions of Visual Studio/BIDS
on my machine?
TIA
J

I am trying to install SqlServer 2005 on windows 2008 cluster with domain controller. Installation fails on the second node while trying to set registry settings for server network libraries. Attached error message and output from error log. Can somebody
suggest any solutions.

Thanks

Ravi

TITLE: Microsoft SQL Server 2005 Setup
------------------------------

Failed to set registry settings for server network libraries. The action is SetDefaults. The error is 11004 (The requested name is valid, but no data of the requested type was found.
)

I am doing an SQL Server 2005 Cluster install. The install appeared to go
okay. On the active node everything installed fine. However, when we looked
at the other node only the configuration tools got installed. SQL Server
Management Studio did not get installed. Would anyone know what caused this
and how to install the SQL Server 2005 on a cluser correctly? I understand
that that the management tools only get installed on the primary node.
Should I run setup on the secondary node to install the tools?

I also went through the summary log for the install and noticed that almost
everything that was installed on the active node was also installed on the
passive node. The products that did not get installed on the passive node
were:

Hi I have a package which was done in SSIS 2005 and I have opened that in SSIS 2008. I want to open this back in 2005 but its throwing an error. How to Open this package back in 2005.

The error message: Error 1 Error loading Package.dtsx: The version number in the package is not valid. The version number cannot be greater than current version number. C:Processing\Operational Packages\Package.dtsx1 1

I need to migrate my SQL Server and Analysis Services cluster from Windows Server 2003 to Windows Server 2008, I have found an article for SQL ID (953200), but I cannot find anything for Analysis Services, does such a guide exist?

Will SSIS packages writen with ssis2005 run used 2008 dtexec.exe? General situation. DB will be upgrade from sql 2005 to sql2008 on a new box. Will the application packages need to be upgraded or will the sql2008 dtexec.exe run them as is?

I just installed SQLServer 2005 STD edition SP3 on an active/passive 2 node cluster, Intended to replace a SQLServer 2005 sp3 EE install (not
clustered) that is in production now using SSIS and SSRS. I would need to migrate the databases, reporting, and Integration Services over to the new server cluster.

1.Does it make sense to run on a SQL Server 2005 on a cluster if SSIS and SSRS are not cluster aware?
This is my 1st time adm