Dunbest question ever.... 1

[simian336]

I have wondered this for sometime but could never find the answer on my own.... What do the numbers and > signify when running a query from command line?

Thanks

Simi

Example

C:\>osql -U sa -P 1234 -i D:\all.sql
1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 1> 2> 3> 4> 5> 6> 7> 8> 1> 2> 3> 4> 5> (8
5165 rows affected)
1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> (85165 rows affected)
1> 2> 3> 4> 5> (60802 rows affected)
1> 2> 3> 4> 5> (60802 rows affected)
1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 2
3> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40> 41> 42> (
0 rows affected)

 

[SgtJarrow]

See this page for osql syntax

http://www.di-mgt.com.au/osqlUtility.htm

Notice the -i syntax which allows you to specify an input file full of commands to exectue.

See this page for the #> explanation

http://msdn.microsoft.com/en-us/library/aa213092(v=SQL.80).aspx

The osql is being run in interactive mode, so the #> is an indicator it is waiting for a command from the user...but in this case the input was coming from the input file.

=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)

Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
C#.NET Programmer

 

[simian336]

Make since...

Thanks

Simi