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\

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...

Who is Participating?
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
what I meant:
>the "lib" is eventually normal.
the "lib" is eventually normal with sql server 2005, as that indeed installs xml 4 objects

the LOGONSERVER is something coming from OS (windows), so you might compare the versions of windows with that box and the one with the "older" sql versions, are they the same?
Guy Hengel [angelIII / a3]Billing EngineerCommented:
the "lib" is eventually normal.
the "LOGONSERVER" should be depending on your OS and domain settings, but not the SQL Server setup
emibadteamAuthor Commented:
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..
oBdAConnect With a Mentor Commented:
That's very normal.
"set L" will display all environment variables starting with L. You can have lots of environment variables defined, it's just that the older version of SQL doesn't set the "lib" variable; this is not affecting the "set" command, it's just another environment variable that is defined like %Temp% or %Path% or whatever.
If you enter
set logonserver
(or even only set li) you will only get the logonserver again. Enter a simple "set", and you will see them all (except for some special variables like %date% or %time%, which are created during runtime).
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.