View Complete Post
Hi, multipart questions.
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.
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?
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
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've created a SSIS package in SQL 2008. I tried running the package in SQL 2005 but was prompted with the error below.
"The version number in the package is not valid. The version number cannot be greater than current version number."
"Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number."
Is there any method that I could use to enable the package to be executed in SQL 2005?
I'm finding some articles or white papers about the limits or incompatibilities of SSIS 2005-2008 web service task.
Any suggests to me, please? Many thanks
I have a process which reads from 2 tables (using two connection managers) and "merge join" them to a third table by using left outer join.
This process is implemented on SSIS 2005 and SSIS 2008 identically, however, for some reason I get
less records at the third table at the 2008 process.