I had to rebuild my SQL development computer, which runs XP Pro, and is
not a domain controller or a member of a domain.

I have SQL 2000 server (SP4) and SQL 2005 server on this development
computer. My problem here is with SQL 2000.

I used to have all of this working on SQL 2000, before the reinstall of
everything, but now I am in a strange catch-22:

Trying to manually start a job listed in SQL 2000 Agent tells me that
the SQL server agent is not running, therefore it can't be notified of
the job, so I can't start the job. (It is running.) I am using local
user accounts that are defined on the same computer to run SQL 2000
server and SQL 2000 agent under, since they need access to a shared
folder (which resides on my "main" computer).

The fix for this error (per KB article 911841) is to replace the ./SQL_
2000_Server username in the registry with <computer_name>/SQL_2000
_Server for the service. SQL 2000 can't correctly interpret the "dot"
for the local computer name.

HOWEVER, then I get the message after reboot that the SQL 2000 server
failed to start because a dependency failed. That dependency is the Net
Logon service. (Although it's not listed as an explicit dependency
under the Dependency tab of the service.)

In a non-domain computer, if you set Net Logon to start automatically,
it starts and stops and says it has nothing to do. Microsoft says that
the Net Logon service should be set to Manual on a non-domain computer.

(Apparently the Net Logon service might have work to do if it wouldn't
just STOP when it sees that it's on a non-domain computer.)

[[Extrainfo: My SQL 2000 development server is a non-domain computer
because it ONLY connects to my "main" computer. My "main" computer has
2 ethernet cards, and the other card connects out to the Internet and to
the rest of our local network.]]

----

SOOOOO, I can't change the period to a computer name per KB911841, since
that would require that Net Logon be running. I can't run Net Logon in
a non-domain computer.

And I can't follow the workaround in KB article 307288, which says to
use Local System for SQL 2000 server and agent, because this SQL 2000
server needs access to a network share, and also because using
LocalSystem for SQL 2000 server or SQL 2000 agent is a bad idea from a
security perpective (see any number of Microsoft articles, such as "10
Stepe to Secure SQL Server 2000").

I *know* that I had this working before the reinstall.

Any getting out of this catch-22, so I can start scheduled jobs
manually, would be greatly appreciated.

David Walker