A few SQL questions

Kurt Schafer ( (no email) )
Mon, 14 Sep 1998 13:07:49 -0400

This is a multi-part message in MIME format.

------=_NextPart_000_0015_01BDDFE0.ACA31840
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm trying to output some sequel queries to text file using SQL-Server =
6.5
=20
I can get the files to output to text file by clicking on the SAVE icon =
from the query manager but I need to be able to schedule these dumps to =
text so that a batch process can work on them later.
=20
Also, when I do save the file it sticks ^M at the end of every row =
result. This is wreaking havoc on the unix machine that I'm trying to =
parse from later. (the SQL server writes directly to the unix host)
=20
If anybody could shed some light on any of the above two problems I =
would appreciate it.
=20
=3D K

------=_NextPart_000_0015_01BDDFE0.ACA31840
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

I'm trying to output some sequel =queries to text=20file using SQL-Server 6.5
 
I can get the files to output to =text file by=20clicking on the SAVE icon from the query manager but I need to be able =to=20schedule these dumps to text so that a batch process can work on them=20later.
 
Also, when I do save the file it =sticks ^M at=20the end of every row result. This is wreaking havoc on the unix machine =that I'm=20trying to parse from later. (the SQL server writes directly to the unix=20host)
 
If anybody could shed some light on any of the above =two=20problems I would appreciate it.
 
=3D K
------=_NextPart_000_0015_01BDDFE0.ACA31840--