![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am getting the error message "Not enough storage available to complete operation" when trying to use the lookup feature in a DTS package. Article 889170 indicates that this should be fixed in SQL Server 2000 SP4. So, I installed SP4, but i'm still getting this error. I really need to use this feature. I used to be able to do lookups, and then at some point it stopped working (a windows automatic update???) The nature of my data loads requires that i be able to use this feature to get the appropriate internal unique keys assigned to data received from outside sources. I hope i'm making sense. My question is... Is anyone else experiencing this problem? What have you done, if anything, to resolve it? thanks, Kay -- "Out of clutter find simplicity, from discord find harmony, in the middle of difficulty lies opportunity" --Albert Einstein |
#3
| |||
| |||
|
|
Kay, We had the same issue where we could not use lookups in w2k3 environment. After spending time with MS support we realized we had two options. One going back to w2k environment were lookups worked and the other getting rid of lookups altogether. We chose the latter because lookups and data pumps in general are performance hindrance for one and unstable in all environments for the other. So we loaded all the data into a bunch of global temp tables with bcp and used Execute SQL tasks with insert/select statements to replace data pump tasks. The statements had left outer joins representing lookups. The performance improved. Ilya "Kay" <Kay (AT) discussions (DOT) microsoft.com> wrote in message news:ED9F0177-2819-4A7E-BBFB-7A21B69A2021 (AT) microsoft (DOT) com... I am getting the error message "Not enough storage available to complete operation" when trying to use the lookup feature in a DTS package. Article 889170 indicates that this should be fixed in SQL Server 2000 SP4. So, I installed SP4, but i'm still getting this error. I really need to use this feature. I used to be able to do lookups, and then at some point it stopped working (a windows automatic update???) The nature of my data loads requires that i be able to use this feature to get the appropriate internal unique keys assigned to data received from outside sources. I hope i'm making sense. My question is... Is anyone else experiencing this problem? What have you done, if anything, to resolve it? thanks, Kay -- "Out of clutter find simplicity, from discord find harmony, in the middle of difficulty lies opportunity" --Albert Einstein |
![]() |
| Thread Tools | |
| Display Modes | |
| |