Comments
Sort by recent activity
I chopped up the script and ran pieces to solve this problem initially, but later used the APIs to code my own program. You might want to go that avenue. Worked pretty well for me. [image] / comments
I chopped up the script and ran pieces to solve this problem initially, but later used the APIs to code my own program. You might want to go that avenue. Worked pretty well for me.
Thanks so much for your help. I'll dig into the code. The solutions you suggested were quite helpful.
-Chris / comments
Thanks so much for your help. I'll dig into the code. The solutions you suggested were quite helpful.
-Chris
Ahhhh. It's possible that the Unicode save option would have been the answer. Is that documented? I didn't see it in the help file, and it wasn't readily obvious to me. Should it have been? [image]
I am still looking at the other issue I mentioned before, though. How is running the SQL through Data Compare different that running it in QA? It's SUPER-FAST relatively speaking when run through Data Compare as opposed to QA. It would be nice to have that option (opening/running a SQL file with Data Compare) if there was indeed a difference.
I am guessing that I could use the APIs to code my own application, but I haven't had the time to get around to that quite yet. [image]
-Chris / comments
Ahhhh. It's possible that the Unicode save option would have been the answer. Is that documented? I didn't see it in the help file, and it wasn't readily obvious to me. Should it have been?
I...
Hi Brian,
I was not aware of a file size limitation either. However, I think I found what may be the problem. I believe that when the script was saved by SQL Data Compare, an EOF marker was somehow saved into the data. There was a box-looking character in the file when I opened it in Notepad. Nothing would display after the character when I tried to open the file in QA.
Let me test a little more and I will post back my findings.
OSQL did not return an error. It just did nothing. [image]
-Chris / comments
Hi Brian,
I was not aware of a file size limitation either. However, I think I found what may be the problem. I believe that when the script was saved by SQL Data Compare, an EOF marker was someh...