July 20, 2005 at 8:31 pm
July 21, 2005 at 7:57 am
I once had this problem before. I had two script files, each about 7 MB. One is to create a blank database, one is to upgrade an exsiting database. The first one always succeded. The second one has lots of transactions and need to take more than 10 hours. Sometimes it succeeded sometimes never finished. The setup developer said that it's windows problem. The command prompt hangs there and windows cannot close it. After that we do not use osql anymore to run the upgrade script. I cannot confirm what the developer said.
So it seems not only the size of the script, it has something to do with the running time.
We were using windows 2000 then.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply