|
|
Posted by Erland Sommarskog on 08/22/06 21:57
Ted (r.ted.byers@rogers.com) writes:
> There are two, probably related, differences between my notebook
> computer and my colleagues' notebooks. 1) They are using SQL Server
> Express 2005 and I am using the developer's edition of SQL Server 2005.
> 2) I can connect to my server using SQLCMD without specifying any
> command line arguments while they must specify the server machine and
> instance (i.e. SQLCMD -S my_machine\an_instance).
By default Developer Edition installs a default instance. And by default
Express Edition installs as a named instance, SQLEXPRESS.
When you say SQLCMD only, this implies a default instance on the local
server. Thus, if you have a named instance, you need to specify this.
".\SQLEXPRESS" should be sufficient.
> Probably related to this, if I edit my perl script to provide the
> additional parameters they have to submit, connection fails while the
> very same commandline submitted on the commandline instead of through
> Perl works. i.e. Submitting SQLCMD -S my_machine\an_instance on the
> commandline works but connection fails if it is submitted from within a
> perl script.
It's not entirely clear, but it sounds as if you specify the instance
name of the laptpos, when to connect the Perl scripts to your local instance
on your workstation. That will not fly, since you have a default instance.
Anyway, without error message and the Perl code, it's a bit difficult
to do more than to guess.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|