sql server connect: Hi:

I have noticed that if there is no network connection, the TCP Server on
port 1433 doesn't start.

Is this a normal behaviour?, Is there any way to change this behaviour, so I
can work offline with SQL Server?.

I'm running SQL Server 2000 Enterprise Edition (8.00.878) SP3 over Windows
Server 2003 (Microsof Windows NT 5.2 - 3790).

You should be able to connect to 127.0.0.1. This should ALWAYS start,
whether your network card is down or not.

To test this,
disconnect your machine,
stop SQL with the SQL Manager,
go here (C:\Program Files\Microsoft SQL Server\MSSQL\Binn) with the
command prompt
type in sqlservr -f -m (to start SQL in minimal configuration,
single-user mode).

You should see something like this:

C:\Program Files\Microsoft SQL Server\MSSQL\Binn>sqlservr.exe -f -m
2004-11-01 13:19:20.77 server Microsoft SQL Server 2000 - 8.00.760
(Intel X8
6)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2004-11-01 13:19:20.81 server Copyright (C) 1988-2002 Microsoft
Corporation.

2004-11-01 13:19:20.81 server All rights reserved.
2004-11-01 13:19:20.82 server Server Process ID is 3908.
2004-11-01 13:19:20.82 server Logging SQL Server messages in file
'd:\MSSQL\l
og\ERRORLOG'.
2004-11-01 13:19:20.84 server Warning: -f command line flag
used...minimal se
rver configured.
2004-11-01 13:19:20.85 server SQL Server is starting at priority class
'norma
l'(1 CPU detected).
2004-11-01 13:19:21.59 server SQL Server configured for thread mode
processin
g.
2004-11-01 13:19:21.60 server Using dynamic lock allocation. [500] Lock
Block
s, [1000] Lock Owner Blocks.
2004-11-01 13:19:21.60 server MS DTC initialization skipped because of
start
up option.
2004-11-01 13:19:21.61 spid3 Warning ******************
2004-11-01 13:19:21.61 spid3 SQL Server started in single user mode.
Updates
allowed to system catalogs.
2004-11-01 13:19:21.63 spid3 Starting up database 'master'.
2004-11-01 13:19:22.14 spid3 Server started with '-f'. Auditing will not
be
started.
2004-11-01 13:19:22.22 server Using 'SSNETLIB.DLL' version '8.0.760'.
2004-11-01 13:19:22.23 spid5 Starting up database 'model'.
2004-11-01 13:19:22.32 spid3 Server name is 'GUAVA'.
2004-11-01 13:19:23.08 server SQL server listening on 192.168.1.82: 1433.
2004-11-01 13:19:23.09 server SQL server listening on 192.168.87.1: 1433.
2004-11-01 13:19:23.09 server SQL server listening on 192.168.31.1: 1433.
2004-11-01 13:19:23.09 server SQL server listening on 127.0.0.1: 1433.
2004-11-01 13:19:23.28 spid5 Clearing tempdb database.
2004-11-01 13:19:24.97 server SQL server listening on TCP, Named Pipes,
Rpc.

2004-11-01 13:19:24.97 server SQL Server is ready for client connections
2004-11-01 13:19:25.73 spid5 Starting up database 'tempdb'.
2004-11-01 13:19:26.07 spid3 Recovery complete.
2004-11-01 13:19:26.07 spid3 SQL global counter collection task is
created.
2004-11-01 13:19:26.11 spid3 Warning: override, autoexec procedures
skipped.

You can press CTRL-C, then Y to terminate. You can then restart SQL as
normal, if you have confirmed that interfaces it is running on.

This means, that you can therefore ALWAYS connect to SQL by specifying
(local) or 127.0.0.1 in your connection string.

Cheers

O

"Amando Resendez" <AmandoResendez@discussions.microsoft.com> wrote in
message news:810A4275-81AF-45FE-9B6C-EBE28C0AFB94@microsoft.com...
[quoted text, click to view]