April 19, 2007 09:19 PM

Sqlcmd

Rating: (0)
SQL Server Magazine
InstantDoc ID #95387
In SQL Server 2005, Microsoft replaced the familiar command-line tool Osql with Sqlcmd. Both tools perform similar functions, with subtle differences. For example, each tool can connect to a SQL Server instance for direct queries or batch job initiation. And, for my project, they can both perform the invaluable service of listing all listening SQL Server machines on the network. One of Sqlcmd’s subtle differences is that you can use the command-line option /Lc rather than just /L to derive the server list:

sqlcmd /Lc
The...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Add a Comment

"sqlcmd /Lc" works well for me.

RODNEY1/14/2010 3:54:17 PM


the syntax given above is incorrect. Use SQLCMD -Lc and press

Craig1/4/2010 6:46:21 PM


I am not sure unless maybe you have a combination of security settings that are preventing browsing to the servers...Firewall ports blocked, SQL Browsing disabled, listening on ports other than default, hidden servers?

RODNEY5/6/2008 2:24:21 PM


i used sqlcmd /Lc or /L and returned null, but i do have sql installed..??

CHANG4/23/2008 2:06:23 PM


You must log on before posting a comment.

Are you a new visitor? Register Here

Related Resources

A Jump Start to SQL Server BI
A EBooks by Microsoft
The Essential Guide to SQL Server 2005 BI
A Essential Guides by Dell
More
GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS