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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-08-07 : 07:50:27
|
| Janet writes "I am using SQL Server 2000, sp. 2. I have a query that was written against a database using a curser, with an output to a text file. In order to capture all the results, I am using an "Execute Process Task", accessing iSQL (under Win32 process), then under parameters, having that file read a SQL file then putting the results as a text file.All is working well, EXCEPT, the formatting of the file. For long rows, the file is wrapping at around the 90 to 100th caracter. It always keeps the words in tact (never splits a word from the field). These rows have greater than 255 characters.If I run the query through Query Analyzer and get the result in a text file, it's perfect.Any help or insights is greatly appreciated.Thanks!" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-08 : 12:47:21
|
| First of all, use osql instead of isql. Second, why don't you just use bcp instead with a view?Tara |
 |
|
|
scottpt
Posting Yak Master
186 Posts |
Posted - 2003-08-14 : 12:20:08
|
| try setting the -w{width} in your command line |
|
|
|
|
|
|
Using iSQL w/ DTS