Microsoft KB Archive/67712

PRB: Starting SAF on a Stand-Alone SQL Server ID Number: Q67712

1.10 1.11 4.20 OS/2

Summary:

SYMPTOMS When attempting to start SAF on a stand-alone SQL server with the command “saf sa” (ignoring the “servername” parameter), the following message appears:

The specified SQL Server: sa is not running. OK to start? CAUSE If you are running a stand-alone SQL server, not entering a server name on the command line does not work. The parameters used in the SAF command line are position-dependent (that is, you must specify them in order).

For example, typing the following line on a stand-alone server will attempt to log SAF into a server named “sa”:

saf sa RESOLUTION As noted in the “Using the SAF” section (page 17) of the “Microsoft SQL Server System Administrator’s Guide” for version 1.11, the following examples show all of the correct ways to start SAF:

saf servername username password saf servername username saf servername saf The first three lines are specific to the network version of SQL Server. In these cases, specify the name of the network server that you want to access.

The only way to start SAF from a stand-alone server is to use no parameters. In this situation, SAF displays a dialog box and prompts you to enter the server name, login ID, and password. At this point, you can enter nothing for the server name and enter “sa” for the login ID. Because you have not entered a server name, SAF sends a null value as the server name to SQL Server and the connection is made through local pipes in stand-alone mode.

Additional reference words: 1.10 1.11 4.20