I have noticed that if SQL7 is installed in a directory with a space in it,
eg c:\program files\mssql7, some batched jobs will not work. Does anyone
know if this is an error in SQL or in NT? I use SQLAgent to call batch
SQL errors, NT errors and setup/installer errors. Even after all this time,
MS hasn't resolved some basic stuff like "long" file names and disks/partitions
greater than 2GB in size...
Your best bet is to install to a short name dir - like C:\MSSQL7
> I have noticed that if SQL7 is installed in a directory with a space in it,
Neil Pike MVP/MCSE. Protech Computing LtdQuote:> eg c:\program files\mssql7, some batched jobs will not work. Does anyone
> know if this is an error in SQL or in NT? I use SQLAgent to call batch
on nt 4 sp6ado you need to stop EVERY service before running the sp3?
theres' like 20 or so, and to manually do that seems ridiculous.
if not every one, which ones?
the readme says stop applications, then further down, says restart services.
guess they don't know either.
any other caveats, besides backing up the system db's?
also, since my sql7 is on D: and I only have 500k left on C:, can I
unpack the sp3.exe onto D: and run it from there, and will it deploy