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 |
|
wardsan
Starting Member
48 Posts |
 Posted - 2004-05-19 : 04:31:46
|
| Folks,we have been using a linked server to insert rows into an oracle database and keep hitting the 2GB virtual memory limit with the sqlservr.exe process. We have decided at this stage, to only select on the linked server and use DTS to do the actual inserts. Should we be aware of any issues we may encounter, we really don't want to get it wrong again. We had so many issues using OLEDB, both microsoft and oracle providers, we really don't want to take a route that's going to give more headaches.... ThanksSandra |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-05-19 : 04:44:41
|
| Why not stay with the linked server and batch the inserts?If you have that much data I would consider creating a file from sql server then importing to oracle - it'll probably be faster and safer.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
wardsan
Starting Member
48 Posts |
Posted - 2004-05-19 : 05:16:01
|
| Basically what we're doing is that we validating data on the sql server tables from oracle so selecting from the oracle database across the link. What the data is validated, inserts are done using the link into the oracle database. When the insert operation begins, the virtual memory on the sql server machine runs up to 2GB and crashes. We are stumped about why the memory is rising so dramatically when the inserts are being done. Microsoft haven't been able to help. We do know there is a problem inserting the rows into tables with large amounts of data. Can anybody shed any light or had similar experiences? I don't think batching the inserts is going to help.... |
|
|
|
|
|
|
DTS enquiry