|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
DTS in code or spI am not sure one is "better" than the other, as DTS (at least in SQL 2000)
is like shooting fish in the dark. With .NET, you have more options, at least to an extent. An easy method is fire a process object and use dtsrun.exe. The main question is what are you using DTS from and what triggers it. If it is an application event or GUI button push, for example, firing from the .NET app makes sense, unless you can also fire it automated at some point in time, then SQL Server may make more sense. Also, how you fire it in SQL Server makes a difference. If you set up a job and fire the job, it is a bit more sane, as less things are open. If you use sqlcmd, you are opening a potential hole and might be better served in .NET. -- Show quoteGregory A. Beamer MVP; MCP: +I, SE, SD, DBA *************************** Think Outside the Box! *************************** "Mike" wrote: > Is it better to execute a DTS package in .NET or in a stored procedure? > > |
|||||||||||||||||||||||