Full site membership is required for this article. Already a full member? Login here. You currently have a guest membership. You can upgrade to full site membership here (free trial available). SQLCMD -- Part II   Article Abstract: (Vadivel Mohanakrishnan) This is the second article on the 3 part series of SQLCMD utility. The target audience is Basic to Intermediate level people.   Read this article...

Related Articles - For Members. All Articles By Author The comparison of SQLCMD with OSQL sqlcmd Utility in SQL Server 2005 SQLCMD -- Part I SQLCMD -- Part V SQLCMD -- Part IX (Running set of scripts in multiple environments with ease) SQLCMD -- Part III Diagnosing Poor Data Access Code Using SQL Profiler SQLCMD utility in SQL Server 2005 Using the SQLCMD in SQL 2005 Server

RE: SQLCMD -- Part II
by Steve Shurts (posted: 10/12/2007 8:20:59 AM)
When attempting to run the "sqlcmd -i Message.sql" command, I received the following error:

"HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired."

I was able to get the command to run after adding the name of one of our SQL servers, thusly:

sqlcmd -S -i Message.sql

I am not sure whether this is due to our local configuration or to an error in the article. Just in case other's are trying this.