ISQL ERROR..
-
I am getting an insufficient resources when trying to execute a sql through isql, the same runs fine through query analyzer. Below is the error. Its when running a st.proc which does 200 rows of insert to a table. error is as below.
Ø Error: Insufficient memory to continue.
How can you resolve this? i read cases of getting this error when virtual memory goes down. how is it possible to check that or is there any other soln? please advise.
TIA
-
It's because ISQL is just a subset of what the server can actually do. Do NOT use ISQL. Use OSQL instead.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Is this on your workstation or the server? Are you able to bounce the box? I typically don't advocate bouncing prod boxes, but memory problems are difficult to fix a lot of times. You can see what's consuming the memory on that box and kill it if you can and see if that works.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
-
Use SQLCMD with SS2K5
-
Also i have a st.rpoc which i am calling thru isql. Thsi is takingw aytoo long than expected. I have put debug msgs in thsi proc to cehck which part of sql is taking too long. does these debug msgs gets written only once the procedure finishes. or isql writes to output when every sql within the st.proc is run..any help on this will be appreciated. TIA
-
Didn't you read any of the above? Don't use ISQL... use OSQL or SQLCMD depending on which version of SQL you have.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply