Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SSIS and Import/Export (2008)
 How does DTEXEC find the "local" server

Author  Topic 

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2012-10-24 : 10:40:53
According to the doc
[url]http://msdn.microsoft.com/en-us/library/ms162810(v=sql.105).aspx[/url]
if you omit the /Server parameter when running dtexec, it defaults to the local server. But what is the "local" server and how does dtexec find it?

e.g. I started up SQL Server on my machine. Then I opened a CMD window and ran:
dtexec /SQL foo /SU

To my surprise, dtexec did not run on my machine, it ran on another server that I connect to from time to time. So, I'd like to know what dtexec does to find the local server. What is "local"?

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2012-10-24 : 11:53:33
local server is default instance of server installed on machine where you run dtexec.

in your dtexec you're asking it to fetch package from SQL Server MSDB database so it gets package from specified server and executes it. If you omit /Server it sets server context as local instance on machine where you installed dtexec

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2012-10-24 : 11:57:19
"If you omit /Server it sets server context as local instance on machine where you installed dtexec"

That is precisely what does NOT happen. dtexec runs package on a completely different machine. I can reproduce this at will
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2012-10-24 : 12:50:35
quote:
Originally posted by gbritton

"If you omit /Server it sets server context as local instance on machine where you installed dtexec"

That is precisely what does NOT happen. dtexec runs package on a completely different machine. I can reproduce this at will


hmm...are you sure you omitted server detail?

how did you pass package path between?

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2012-10-24 : 13:21:48
Yes, I'm sure I omitted the /Server parameter. I had run it before WITH the /Server parameter pointing to my local server. Then I saw that I could omit that parameter when the server is local. So, I removed it. Imagine my surprise when I saw the activity happening on a different server! (Both my local server and the other one have the same package installed).
Go to Top of Page
   

- Advertisement -