>That's why Microsoft have a knowledge base article (Article Q196824) saying
>"Don't use SMS with SQL 7.0". It's probably in the SQL 7.0 readme as well.
>Always check the knowledge base before upgrading to new products.
Please excuse the ranting, but the SMS 1.2/SQLS7 issue really wound me up.
Yes there is a KB article, buried deep down, which you'll only find after
SMS 1.2 has died and you're desperately trying to reinstall it to no avail.
Q196824 is not even indexed as a SQL Server issue, only an SMS issue. You'll
never find it searching for SQLS issues involving SMS, only the other way
I do try to be careful to check the literature before a major upgrade. Yes,
I actually read the Readme files, and if there had been a mention of the
problem in the SQLS7 readme or install help files, believe me I would have
There is NO mention about this issue anywhere in the SQLS7 readme, install
notes, help files or MSDN. The only fix is to upgrade to SMS 2.0, which was
not even launched when SQL7S was released, so MS knew the all their Back
Office customers upgrading to it must have had SMS 1.2. The simple fact is
it was a marketing*-up. The SMS 2 development was supposed to stay
parallel with SQLS7, because they new from the start SQLS7 would not work
with SMS 1.2. But they wanted to do a big launch of SQLS7 at Comdex Fall,
and SMS 2 wasn't ready, so they launched SQLS7 anyway. Q196824 is pure
And just to add insult to injury, SMS 2.0 was officially "released" a month
ago, but the CDs are still not shipping, although I can buy license packs
'til the cows come home. Oh, and of course if you bought SMS 1.2/Back Office
4.0 before January 1999 say hello to SMS 2.0 upgrade fees, just so you can
have something that works with that SQLS7 upgrade you just bought.
The SQLS7 install could easily have been designed to detect that SMS 1.2 is
installed and warn you of the problem before it is too late, but does not.
There is absolutely no mention on the BackOffice site anywhere that SQLS7
will kill existing Back Office 4.0 components, yet Microsoft continue to
push SQLS7 as the perfect upgrade for all SQL 6.x users.
There has to be a practical limit. Are you seriously suggesting you trawl
through every KB article on every related MS product to a new upgrade before
installing it? The problem with this issue is not that Microsoft's customers
are not checking the setup requirements, but that MS is trying to cover up a
horrible compatibility and development problem by the time-honored technique
of not telling anyone about it and hoping it will disappear under a
tidal-wave of promotional material and offers.
Daniel (Remove x from email to reply directly)