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.
| Author |
Topic |
|
heze
Posting Yak Master
192 Posts |
 Posted - 2006-10-09 : 20:14:15
|
| Hi,Im using the DTS but using the designer, there are certain elements that when produced and configured, once I try to open them again the designer sends a message thaat there is anerror and if I wish to report it, any option i choose, the DTS designer closes the window, I wonder if this is a bug of the designer, a problem with my hard disk(because there isnother message stating that certain hexadecimal address could not be written), or what?In your experience, is the DTS stable enough to rely on it to perform a considerably large workflow, or I better program everything in visual basic/vbscript? I was planning to use it to automate a considerably large worflow but with this problem now I wonder...thank youthank you |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2006-10-09 : 22:39:22
|
| Have you tried reinstalling the SQL client components (including Enterprise Manager and the DTS components)? I've often seen EM throw strange errors that go away with a reinstall.As far as workflow is concerned, I have seen some absolutely SICK DTS jobs that run. Someone posted a screenshot on SQL Team a while back, basically you couldn't see the white background because of all the data flow tasks. You can always break up large workflows into smaller packages and execute each of them through a master package/workflow. This is probably better because testing a huge workflow all at once will probably take much longer than each piece separately. |
 |
|
|
heze
Posting Yak Master
192 Posts |
Posted - 2006-10-11 : 00:10:31
|
| Thanks Rob, I reinstalled the client components in my PC but the problem persisted, finally after some ime lost I apparently found out the problem, the problematic element was the transform data task whose source was an Access connection and the target was a SQL Server connection. When the source Access table was opened by somebody else, and I tried to open the task by double clicking, it triggered the mentioned message and shut the window down, so the way I "fixed" the issue was by creating one centralized Access db and created all the necessary linked tables, now, even though the concrete tables that are pointed by my linked tables are opened by another user, DTS is not complaining any more, I imagine must be some kind of networking problem (bug?), but anyway this patch let me continue with my work |
|
|
|
X002548
Not Just a Number
15586 Posts |
|
|
|
|
|
|
|
DTS designer shutting up