yami_rider
asked on
sqlcmd - Variations between Windows Server 2003 and Windows Server 2008
Is there a difference between Windows 2003 and Windows 2008 with respect to SQL 2008's sqlcmd utility?
In Windows 2003 if I install SQL 2008 Express w/Adv Services and run the command:
sqlcmd /A -Q "select * from sys.syslogins;"
the command succeeds and performs the query.
However under Windows Server 2008, if I install SQL 2008 Express w/Adv Services and run the same command:
sqlcmd /A -Q "select * from sys.syslogins;"
it fails to connect.
Is there a difference with respect to which operating system it is running on? Is there a difference between types as well (i.e. x64 vs x86)?
Trying to script a process and based on my results looks like I will need to check the OS distribution, but does not make since because both OS's are running SQL 2008 Express.
Any help would be greatly appreciated.
In Windows 2003 if I install SQL 2008 Express w/Adv Services and run the command:
sqlcmd /A -Q "select * from sys.syslogins;"
the command succeeds and performs the query.
However under Windows Server 2008, if I install SQL 2008 Express w/Adv Services and run the same command:
sqlcmd /A -Q "select * from sys.syslogins;"
it fails to connect.
Is there a difference with respect to which operating system it is running on? Is there a difference between types as well (i.e. x64 vs x86)?
Trying to script a process and based on my results looks like I will need to check the OS distribution, but does not make since because both OS's are running SQL 2008 Express.
Any help would be greatly appreciated.
Try specifying the instance name "-S server_name" in you command. Your 2008 instance may not be the default instance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Does your Windows 2008 server have multiple IP addresses assigned to it or multiple NIC's that are connected to the network?
Windows 2008/Vista can have issues in these cases with all SQL versions.
Troubleshooting: Timeout Expired - Unusual Errors - Multiple Server IP Addresses
http://msdn.microsoft.com/en-us/library/ms190181.aspx