Installing SSIS on machine running C# application.
1. Does that mean on machine running C# application, Integratin Services
option from SQL Server 2005 installation should be installed? And no need to
install full SQL Server 2005? Do we have such an option?
2. We had installed full SQL Server 2005 on a machine. Automatically
DTEXEC.EXE also got installed. Then we disabled Integration Service. The
package was in file system and not in SQL instance. Then too we were able to
execute the package and save the data on SQL instance running on different
machine.
I am not very clear about over all scene. Does that mean having just
DTEXEC.EXE is enough? What are it's dependencies? Can I port just DTEXEC.EXE
on machine running C# application? Are there any deployment issues?
--
Regards,
MSGuy
[quoted text, click to view] ""WenJun Zhang[msft]"" wrote:
> Hi,
>
> This is mainly a SQL2005 related question.
>
> As I know, the DTEXEC.exe can retrieve packages from remote SQL instance
> but the execution is still at local. So at least you should have SQL Server
> 2005 Integration Services (SSIS) installed on the client machine. The
> details can be found in SQL2005 BOL:
>
> dtexec Utility
>
http://msdn2.microsoft.com/en-us/library/ms162810.aspx >
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
Installing SSIS on machine running C# application.
1. Does that mean on machine running C# application, Integratin Services
option from SQL Server 2005 installation should be installed? And no need to
install full SQL Server 2005? Do we have such an option?
2. We had installed full SQL Server 2005 on a machine. Automatically
DTEXEC.EXE also got installed. Then we disabled Integration Service. The
package was in file system and not in SQL instance. Then too we were able to
execute the package and save the data on SQL instance running on different
machine.
I am not very clear about over all scene. Does that mean having just
DTEXEC.EXE is enough? What are it's dependencies? Can I port just DTEXEC.EXE
on machine running C# application? Are there any deployment issues?
--
Regards,
MSGuy
[quoted text, click to view] ""WenJun Zhang[msft]"" wrote:
> Hi,
>
> This is mainly a SQL2005 related question.
>
> As I know, the DTEXEC.exe can retrieve packages from remote SQL instance
> but the execution is still at local. So at least you should have SQL Server
> 2005 Integration Services (SSIS) installed on the client machine. The
> details can be found in SQL2005 BOL:
>
> dtexec Utility
>
http://msdn2.microsoft.com/en-us/library/ms162810.aspx >
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
Hi,
This is mainly a SQL2005 related question.
As I know, the DTEXEC.exe can retrieve packages from remote SQL instance
but the execution is still at local. So at least you should have SQL Server
2005 Integration Services (SSIS) installed on the client machine. The
details can be found in SQL2005 BOL:
dtexec Utility
http://msdn2.microsoft.com/en-us/library/ms162810.aspx Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi,
Since this is a SQL2005 SSIS issue, our SQL engineer will work with you in
our SQL newsgroup. Please monitor the update of us in your another post in
SQL queue.
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
