FYI> "Invalid command option D." >Resolved

Just thought I would pass this along in hopes that it can help someone.
When I had changed the startup parameters for SQL so that the databases and
log files would be in different locations. I used CAPITAL LETTERS to
designate the default location. Like -DD:\data and -LL\:logs... that
caused the server to fail to start, no matter what I did, and when I tried
to start from a dos prompt I would get the "Invalid command option D."
error. The solution was to change the registry setting under
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Parameter
s]
and remove any capitol letters. Once I changed -DD:\data to -dD:\data,
and -lL:\logs, SQL starts up fine..Thanks for following up your own post. It prevents others from wasting their
time trying to help you after you have solved the problem, and it helps
others when you share your solution.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:%23mMqhwiwGHA.4280@.TK2MSFTNGP04.phx.gbl...
> Just thought I would pass this along in hopes that it can help someone.
> When I had changed the startup parameters for SQL so that the databases
> and log files would be in different locations. I used CAPITAL LETTERS to
> designate the default location. Like -DD:\data and -LL\:logs... that
> caused the server to fail to start, no matter what I did, and when I tried
> to start from a dos prompt I would get the "Invalid command option D."
> error. The solution was to change the registry setting under
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Paramet
ers]
> and remove any capitol letters. Once I changed -DD:\data to -dD:\data,
> and -lL:\logs, SQL starts up fine..
>