emibadteam
asked on
SQL 2005 affects DOS commands??
I have built a new system wand installed SQL 2005. I have noticed that this affect the SET command in DOS. example: set l
lib=C:\Program Files\SQLXML 4.0\bin\
LOGONSERVER=\\MYDC
does anyone know if this is because SQL was setup wrong? ...or is this something that's "normal"??
this does not happen on my older SQL boxes...
Thanks
lib=C:\Program Files\SQLXML 4.0\bin\
LOGONSERVER=\\MYDC
does anyone know if this is because SQL was setup wrong? ...or is this something that's "normal"??
this does not happen on my older SQL boxes...
Thanks
ASKER
yepper,, I understand that what I'm showing you above is what is returned when I type "set l"..
hence my question... cause I don't get that if I'm on a server with an older version of SQL..
hence my question... cause I don't get that if I'm on a server with an older version of SQL..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the "LOGONSERVER" should be depending on your OS and domain settings, but not the SQL Server setup