| Groups | Blog | Home |
sql server dts : SSIS Deployment
located on the same machine where C# application runs. Hence, DTEXEC.EXE file doesn't reside on machine where C# application runs. My question Can we install DTEXEC.EXE (and NOT whole SQL Server 2005) on machine that runs C# application. -- Regards, MSGuy
Installing SSIS on machine running C# application.
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? And if yes to above, will it be counted as one liecnse is used? -- Regards, MSGuy [quoted text, click to view] "Darren Green" wrote:
> Pravin wrote: > > We have a C# application which calls DTEXEC.EXE. SQL Server (2005) is not > > located on the same machine where C# application runs. Hence, DTEXEC.EXE file > > doesn't reside on machine where C# application runs. > > > > My question Can we install DTEXEC.EXE (and NOT whole SQL Server 2005) on > > machine that runs C# application. > > > > You will need to install SSIS on the machine. Note, SSIS is no > redistributable as DTS was, so this machine will require a full server > license. > > -- > Darren > http://www.sqldts.com > http://www.sqlis.com
Ilya,
Wow that would be really useful. So my SQL Server will be loaded on a SERVER machine (remote machine)...and C# application will run on client machine...which will call DTEXEC.EXE residing on server machine. Cool! How to do this? Is it just include the path of DTEXEC.EXE (residing on remote machine) in system variable "path" of client machine? Do we need to do anything else? Thanks. -- Regards, MDGuy [quoted text, click to view] "Ilya Margolin" wrote:
> Pravin, > > Have you considered running DTEXEC on the remote PC? It can be done. > > Ilya > > "Pravin" <Pravin@newsgroups.nospam> wrote in message > news:DE5E73C9-BE6B-4081-870F-CF1111F899A0@microsoft.com... > > We have a C# application which calls DTEXEC.EXE. SQL Server (2005) is not > > located on the same machine where C# application runs. Hence, DTEXEC.EXE > file > > doesn't reside on machine where C# application runs. > > > > My question Can we install DTEXEC.EXE (and NOT whole SQL Server 2005) on > > machine that runs C# application. > > > > -- > > Regards, > > MSGuy > > > >
I didn't get --> rather than just load an exe over the network and run it locally. Do you mean copy it from network or what else? How about ot's dependencies? Thanks. -- Regards, MSGuy [quoted text, click to view] "Darren Green" wrote:
> Pravin wrote: > > Ilya, > > > > Wow that would be really useful. So my SQL Server will be loaded on a SERVER > > machine (remote machine)...and C# application will run on client > > machine...which will call DTEXEC.EXE residing on server machine. Cool! > > > Just like DTS, SSIS packages are executed on the machine which calls > them, the host process, so the package executes upon the machine which > DTEXEC is running. If you can invoke a process on a remote machine, then > this will work, rather than just load an exe over the network and run it > locally. > > > > How to do this? Is it just include the path of DTEXEC.EXE (residing on > > remote machine) in system variable "path" of client machine? > > > > Do we need to do anything else? Thanks. > > > > > -- > Darren > http://www.sqldts.com > http://www.sqlis.com
Pravin,
Have you considered running DTEXEC on the remote PC? It can be done. Ilya [quoted text, click to view] "Pravin" <Pravin@newsgroups.nospam> wrote in message news:DE5E73C9-BE6B-4081-870F-CF1111F899A0@microsoft.com... > We have a C# application which calls DTEXEC.EXE. SQL Server (2005) is not > located on the same machine where C# application runs. Hence, DTEXEC.EXE file > doesn't reside on machine where C# application runs. > > My question Can we install DTEXEC.EXE (and NOT whole SQL Server 2005) on > machine that runs C# application. > > -- > Regards, > MSGuy >
[quoted text, click to view]
Pravin wrote: > We have a C# application which calls DTEXEC.EXE. SQL Server (2005) is not > located on the same machine where C# application runs. Hence, DTEXEC.EXE file > doesn't reside on machine where C# application runs. > > My question Can we install DTEXEC.EXE (and NOT whole SQL Server 2005) on > machine that runs C# application. > You will need to install SSIS on the machine. Note, SSIS is no redistributable as DTS was, so this machine will require a full server license. -- Darren http://www.sqldts.com
Hello Pravin,
You could install SSIS without install other components on a machine. For licensing questions, you can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00 A.M. to 6:00 P.M. (PST) to speak directly to a Microsoft licensing specialist. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites http://www.microsoft.com/licensing/index/worldwide.asp to find contact information in their locations. Best Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- [quoted text, click to view] >Thread-Topic: SSIS Deployment
>thread-index: AcYBWN5AsP0G66V0T72zTS/U2XOIDQ== >X-WBNR-Posting-Host: 203.190.152.60 >From: =?Utf-8?B?UHJhdmlu?= <Pravin@newsgroups.nospam> >References: <DE5E73C9-BE6B-4081-870F-CF1111F899A0@microsoft.com> <OmiCfKVAGHA.3936@TK2MSFTNGP12.phx.gbl> >Subject: Re: SSIS Deployment >Date: Thu, 15 Dec 2005 01:21:02 -0800 >Lines: 33 >Message-ID: <E928CE04-8CDB-4E78-B489-EAAA61A48CCB@microsoft.com> >MIME-Version: 1.0 >Content-Type: text/plain; > charset="Utf-8" >Content-Transfer-Encoding: 7bit >X-Newsreader: Microsoft CDO for Windows 2000 >Content-Class: urn:content-classes:message >Importance: normal >Priority: normal >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 >Newsgroups: microsoft.public.sqlserver.dts >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.dts:62580 >X-Tomcat-NG: microsoft.public.sqlserver.dts > >Installing SSIS on machine running C# application. > >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? > >And if yes to above, will it be counted as one liecnse is used? > >-- >Regards, >MSGuy > > >"Darren Green" wrote: > >> Pravin wrote: >> > We have a C# application which calls DTEXEC.EXE. SQL Server (2005) is not >> > located on the same machine where C# application runs. Hence, DTEXEC.EXE file >> > doesn't reside on machine where C# application runs. >> > >> > My question Can we install DTEXEC.EXE (and NOT whole SQL Server 2005) on >> > machine that runs C# application. >> > >> >> You will need to install SSIS on the machine. Note, SSIS is no >> redistributable as DTS was, so this machine will require a full server >> license. >> >> -- >> Darren >> http://www.sqldts.com >> http://www.sqlis.com >> >
[quoted text, click to view]
Pravin wrote: Yes. You can install any of the server components on their own, SQL, AS, > Installing SSIS on machine running C# application. > > 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? > RS, SSIS. Not sure about NS, but not an issue here. [quoted text, click to view] > And if yes to above, will it be counted as one liecnse is used? Yes, for every machine that runs a server component, which SSIS now is, you need to license that machine for a full server. So you can run a SQL+SSIS+AS as is most common, or you can split across three machines, but you need more licenses. To be absolutely clear on licensing, check with MS as Peter suggests. -- Darren http://www.sqldts.com
[quoted text, click to view]
Pravin wrote: Just like DTS, SSIS packages are executed on the machine which calls > Ilya, > > Wow that would be really useful. So my SQL Server will be loaded on a SERVER > machine (remote machine)...and C# application will run on client > machine...which will call DTEXEC.EXE residing on server machine. Cool! > them, the host process, so the package executes upon the machine which DTEXEC is running. If you can invoke a process on a remote machine, then this will work, rather than just load an exe over the network and run it locally. [quoted text, click to view] > How to do this? Is it just include the path of DTEXEC.EXE (residing on > remote machine) in system variable "path" of client machine? > > Do we need to do anything else? Thanks. > -- Darren http://www.sqldts.com
Hello,
Based on my test, if SSIS is not installed on client machine, and I tried to run dtsexec from remote server with SQL 2005 installed, \\servername\d$\Program Files\Microsoft SQL Server\90\DTS\Binn\ I received the error message the error message "the system cannot execute the specified program". It seems we are not able to execute the program from client via this method. We need to install SSIS on clients. Best Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- [quoted text, click to view] >Thread-Topic: SSIS Deployment <O0PrxuXAGHA.2392@TK2MSFTNGP09.phx.gbl> >thread-index: AcYBh86MGy++0UymRfKBWFf1eMvE9w== >X-WBNR-Posting-Host: 203.190.152.60 >From: =?Utf-8?B?UHJhdmlu?= <Pravin@newsgroups.nospam> >References: <DE5E73C9-BE6B-4081-870F-CF1111F899A0@microsoft.com> <7041BD5B-E4F9-4EAC-A8D9-AE21FA582664@microsoft.com> <OV8otWYAGHA.2812@TK2MSFTNGP09.phx.gbl> [quoted text, click to view] >Subject: Re: SSIS Deployment
>Date: Thu, 15 Dec 2005 06:57:02 -0800 >Lines: 40 >Message-ID: <A11D5574-F125-42ED-8FF6-EAB44BCB021B@microsoft.com> >MIME-Version: 1.0 >Content-Type: text/plain; > charset="Utf-8" >Content-Transfer-Encoding: 7bit >X-Newsreader: Microsoft CDO for Windows 2000 >Content-Class: urn:content-classes:message >Importance: normal >Priority: normal >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 >Newsgroups: microsoft.public.sqlserver.dts >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.dts:62591 >X-Tomcat-NG: microsoft.public.sqlserver.dts > > >I didn't get >--> rather than just load an exe over the network and run it locally. > >Do you mean copy it from network or what else? How about ot's dependencies? >Thanks. > >-- >Regards, >MSGuy > > >"Darren Green" wrote: > >> Pravin wrote: >> > Ilya, >> > >> > Wow that would be really useful. So my SQL Server will be loaded on a SERVER >> > machine (remote machine)...and C# application will run on client >> > machine...which will call DTEXEC.EXE residing on server machine. Cool! >> > >> Just like DTS, SSIS packages are executed on the machine which calls >> them, the host process, so the package executes upon the machine which >> DTEXEC is running. If you can invoke a process on a remote machine, then >> this will work, rather than just load an exe over the network and run it >> locally. >> >> >> > How to do this? Is it just include the path of DTEXEC.EXE (residing on >> > remote machine) in system variable "path" of client machine? >> > >> > Do we need to do anything else? Thanks. >> > >> >> >> -- >> Darren >> http://www.sqldts.com >> http://www.sqlis.com >> >
Pravin,
To run a process on a remote machine you can use RSH or REXEC commands. Look them up in the Windows help. The approach requires some setup, but it works. Another approach can be setting up either Windows or SQL job on the remote machine which would look for a token file to start your process. Yet another approach would be using Message Queue task at the beginning of you package and sending the MQ message from you C# program to start the process. I am sure there are other approaches. Ilya [quoted text, click to view] "Pravin" <Pravin@newsgroups.nospam> wrote in message news:7041BD5B-E4F9-4EAC-A8D9-AE21FA582664@microsoft.com... > Ilya, > > Wow that would be really useful. So my SQL Server will be loaded on a SERVER > machine (remote machine)...and C# application will run on client > machine...which will call DTEXEC.EXE residing on server machine. Cool! > > How to do this? Is it just include the path of DTEXEC.EXE (residing on > remote machine) in system variable "path" of client machine? > > Do we need to do anything else? Thanks. > > -- > Regards, > MDGuy > > > > "Ilya Margolin" wrote: > > > Pravin, > > > > Have you considered running DTEXEC on the remote PC? It can be done. > > > > Ilya > > > > "Pravin" <Pravin@newsgroups.nospam> wrote in message > > news:DE5E73C9-BE6B-4081-870F-CF1111F899A0@microsoft.com... > > > We have a C# application which calls DTEXEC.EXE. SQL Server (2005) is not > > > located on the same machine where C# application runs. Hence, DTEXEC.EXE > > file > > > doesn't reside on machine where C# application runs. > > > > > > My question Can we install DTEXEC.EXE (and NOT whole SQL Server 2005) on > > > machine that runs C# application. > > > > > > -- > > > Regards, > > > MSGuy > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |