dbTalk Databases Forums  

SSIS Deployment

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss SSIS Deployment in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Pravin
 
Posts: n/a

Default SSIS Deployment - 12-14-2005 , 11:43 PM






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


Reply With Quote
  #2  
Old   
Darren Green
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 02:36 AM






Pravin wrote:
Quote:
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


Reply With Quote
  #3  
Old   
Pravin
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 03:21 AM



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:

Quote:
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


Reply With Quote
  #4  
Old   
Peter Yang [MSFT]
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 04:40 AM



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.


--------------------
Quote:
Thread-Topic: SSIS Deployment
thread-index: AcYBWN5AsP0G66V0T72zTS/U2XOIDQ==
X-WBNR-Posting-Host: 203.190.152.60
From: =?Utf-8?B?UHJhdmlu?= <Pravin (AT) newsgroups (DOT) nospam
References: <DE5E73C9-BE6B-4081-870F-CF1111F899A0 (AT) microsoft (DOT) com
OmiCfKVAGHA.3936 (AT) TK2MSFTNGP12 (DOT) phx.gbl
Subject: Re: SSIS Deployment
Date: Thu, 15 Dec 2005 01:21:02 -0800
Lines: 33
Message-ID: <E928CE04-8CDB-4E78-B489-EAAA61A48CCB (AT) microsoft (DOT) 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!TK2MSFT NGXA03.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




Reply With Quote
  #5  
Old   
Darren Green
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 05:57 AM



Pravin wrote:
Quote:
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?

Yes. You can install any of the server components on their own, SQL, AS,
RS, SSIS. Not sure about NS, but not an issue here.

Quote:
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
http://www.sqlis.com


Reply With Quote
  #6  
Old   
Ilya Margolin
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 07:32 AM



Pravin,

Have you considered running DTEXEC on the remote PC? It can be done.

Ilya

"Pravin" <Pravin (AT) newsgroups (DOT) nospam> wrote

Quote:
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




Reply With Quote
  #7  
Old   
Pravin
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 07:51 AM



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:

Quote:
Pravin,

Have you considered running DTEXEC on the remote PC? It can be done.

Ilya

"Pravin" <Pravin (AT) newsgroups (DOT) nospam> wrote in message
newsE5E73C9-BE6B-4081-870F-CF1111F899A0 (AT) microsoft (DOT) 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





Reply With Quote
  #8  
Old   
Darren Green
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 08:41 AM



Pravin wrote:
Quote:
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.


Quote:
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


Reply With Quote
  #9  
Old   
Pravin
 
Posts: n/a

Default Re: SSIS Deployment - 12-15-2005 , 08:57 AM




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:

Quote:
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


Reply With Quote
  #10  
Old   
Peter Yang [MSFT]
 
Posts: n/a

Default Re: SSIS Deployment - 12-16-2005 , 02:09 AM



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.


--------------------
Quote:
Thread-Topic: SSIS Deployment
thread-index: AcYBh86MGy++0UymRfKBWFf1eMvE9w==
X-WBNR-Posting-Host: 203.190.152.60
From: =?Utf-8?B?UHJhdmlu?= <Pravin (AT) newsgroups (DOT) nospam
References: <DE5E73C9-BE6B-4081-870F-CF1111F899A0 (AT) microsoft (DOT) com
O0PrxuXAGHA.2392 (AT) TK2MSFTNGP09 (DOT) phx.gbl
<7041BD5B-E4F9-4EAC-A8D9-AE21FA582664 (AT) microsoft (DOT) com>
<OV8otWYAGHA.2812 (AT) TK2MSFTNGP09 (DOT) phx.gbl>
Quote:
Subject: Re: SSIS Deployment
Date: Thu, 15 Dec 2005 06:57:02 -0800
Lines: 40
Message-ID: <A11D5574-F125-42ED-8FF6-EAB44BCB021B (AT) microsoft (DOT) 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!TK2MSFT NGXA03.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




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.