osql question

Re:
osql -i test.sql -e -b -r 1 > temp.log
I intend to use osql to submit a bunch of SQL scripts from
a batch file.
If the SQL script has an error, the message is logged with
a line number. But the echoed input does not have line
numbers. Instead, the SQL text is preceded by a line that
looks like:
1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17>
18> 19> 20> 21> 22> 23>
The above looks to me like the line numbers without the
text. The text is successfully echoed after that, but
with out line numbers.
Is there any way to get the text echoed to the log file
with line numbers?
Hi
I don't think you can do exactly what you want. -n will turn of the N>
prompts and -m can set the error level to display.
John
"Randy" <anonymous@.discussions.microsoft.com> wrote in message
news:1c7c801c4524c$36dbc0a0$a001280a@.phx.gbl...
> Re:
> osql -i test.sql -e -b -r 1 > temp.log
> I intend to use osql to submit a bunch of SQL scripts from
> a batch file.
> If the SQL script has an error, the message is logged with
> a line number. But the echoed input does not have line
> numbers. Instead, the SQL text is preceded by a line that
> looks like:
> 1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17>
> 18> 19> 20> 21> 22> 23>
> The above looks to me like the line numbers without the
> text. The text is successfully echoed after that, but
> with out line numbers.
> Is there any way to get the text echoed to the log file
> with line numbers?
>
>

OS and SQL Server installed on seperate drives.

We have a server with one IDE drive which is where the OS
in located. We have recently purchased a SCSI drive and
intend on installing SQL Server 2000 on it. Is anyone
aware of any problems that could arise from having the OS
and SQL server on seperate drives? Thanks a lot!No issues that I know of. In fact, having more drives to spread out the I/O
is strongly encouraged.
--
--Brian
(Please reply to the newsgroups only.)
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:398b01c4014b$1477d870$a601280a@.phx.gbl...
> We have a server with one IDE drive which is where the OS
> in located. We have recently purchased a SCSI drive and
> intend on installing SQL Server 2000 on it. Is anyone
> aware of any problems that could arise from having the OS
> and SQL server on seperate drives? Thanks a lot!|||Hi Mark.
There's no problem with separating the drives that the o/s & SQL Server are
on, but you should be aware that by far the most important components to
separate onto different physical disks are SQL Server's .mdf & .ldf files.
There are significant performance and recoverability issues that stem from
this separation and it's the thing that most inexperienced people get wrong.
Regards,
Greg Linwood
SQL Server MVP
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:398b01c4014b$1477d870$a601280a@.phx.gbl...
> We have a server with one IDE drive which is where the OS
> in located. We have recently purchased a SCSI drive and
> intend on installing SQL Server 2000 on it. Is anyone
> aware of any problems that could arise from having the OS
> and SQL server on seperate drives? Thanks a lot!