Viewing 15 posts - 31 through 45 (of 135 total)
The only things that I set differently than default are the RPC & RPC out server options. By default these are set to False. We do quite a bit of...
October 17, 2006 at 4:40 am
Do you have the named pipes protocol enabled? We ran into a similar problem with one of our users.
John
September 28, 2006 at 8:30 am
Gary,
Are you generating a log file? What does the log file say? There will probably more detail in there that will someone to help. The message you gave is too...
September 21, 2006 at 4:46 am
Yonah,
I believe you have to have Visual Studio 2005 Professional Edition to create a SQL Server project. You can't create it with the VS that comes with SQL. I don't...
September 19, 2006 at 5:16 am
Wanderer,
Not if you are in a 64 bit environment. DTExec will defer to the 64 bit version. Hence why you have to call out the full path name.
John
August 24, 2006 at 10:30 am
Curtis,
Here is how you reference it within a SQL Agent Job:
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" /dts \MSDB\PackageName /SERVER ServerName
Here is how you reference it from a SP:
EXEC
...
August 24, 2006 at 9:53 am
Jv,
We recently upgraded our data warehouse server to 64 bit & ran into a few issues with the dtexec but it mostly was related to what was compatible with 64...
August 24, 2006 at 4:13 am
We had a similar problem & it ended up being the fact that the named pipes protocol was not enabled on the server being accessed. I enabled it & the...
August 22, 2006 at 8:49 am
Claude,
Thanks for the help. I rewrote my update statement using the not exists & it worked perfectly. Still not sure why it didn't work before but it works!
Thanks!
John
August 7, 2006 at 3:47 am
Grant,
We ran into this same issue. Within a SSIS package, there is a SQL 2000 DTS package step. You can go in & do your ODBC "stuff" within the DTS...
July 21, 2006 at 6:34 am
The account running this will have to be a member of sysadmin. Other than that, it should be fine.
John
July 21, 2006 at 6:26 am
It is safe as long as you have everything locked down. Far as extended sp's & other high powered functions. By default, public has access to several of these sp's...
July 20, 2006 at 6:59 am
Ryan,
It depends on what you need to do in your SQL Agent jobs. If you are accessing network shares or other secured areas, then you would need it to run...
July 20, 2006 at 6:24 am
Lee,
In addition to what Zubeyir said, they won't have any more power than what they currently have with Enterprise manager on their machines. MS just combines the two tools.
The DBAs...
July 20, 2006 at 5:27 am
Marcus,
Thanks for the reply but I may not be explaining myself correctly. I am doing a load into a SQL table. I turned on logging for the entire SSIS package. ...
July 19, 2006 at 12:15 pm
Viewing 15 posts - 31 through 45 (of 135 total)