Feeds

It was Microsoft wot done it

What did happen to that Bloor Report?

  • alert
  • submit to reddit

Combat fraud and increase customer satisfaction

Was the report suppressed? Yes. The acid test is looking on Bloor's own site. There you'll find an archive that does, indeed, go back to 1997, but there is no record of any database scalability report.

Screen shot of Bloor website with no mention of the report.

Who was responsible for the suppression? When the report was initially published I was very impressed with the rigour of the testing, so when it suddenly disappeared I approached Bloor to ask where it had gone – whereupon the sorry tale emerged. Microsoft confirmed the basic facts although, as this contemporary column that I wrote in Personal Computer World shows, the stories from the two companies differed in detail.

November 1997

History ain't what it used to be (allegedly)

Those of you who have been worrying about the implications of the Bloor report on Scalability in Databases can stop worrying: the report essentially no longer exists.

The facts described in the report? Oh, they don't appear to have changed. Bloor did find that Microsoft's SQL Server did not scale well, did find the other points of concern, and the company still stands by those findings. What has changed is that the report itself is no longer an available part of the sum total of human knowledge. If you don't have a copy of it, your chances of obtaining all the information therein are slim indeed.

Here are some more facts, so far as I have been able to ascertain them. The report looked at RDBMSs from two companies, IBM and Microsoft. Bloor claims that both companies (Microsoft included) provided software and support people to set up the RDBMSs for testing; Microsoft disputes this and says it did not supply people to help with the test.

The licence for SQL Server says (in broad legalese) that you must have Microsoft's written permission before publishing the results of testing. Bloor did not obtain this written permission, and says that it took Microsoft's assistance in the project as tacit acceptance of the fact that the results would be published.

A couple of months after publication of the report, Bloor received a "cease and desist" letter from Microsoft's lawyers. This letter says Bloor is in breach of contract because it failed to obtain the required written permission. Since Bloor had indeed failed to do so, it felt that it had no option but to cease distribution of the report.

A reasonable person might ask why, if Microsoft felt that the report was inaccurate, it didn't try to stop the report being published on those grounds rather than on what appears to be a technicality.

The greatest loss from all of this may not be the actual information contained in the report, but the methods it used for testing databases. Testing databases for speed is a very complex area, too often treated in a trivial way. This Bloor report was, in my opinion, a genuine contribution to our attempts to derive a sensible methodology of testing databases.

As another piece of opinion, I feel that if Microsoft knew the report was inaccurate, it should have attacked on that basis. To attack it on a technicality rather than technical grounds seems to me the worst of all worlds, making the company look high-handed and arrogant.

Of course, I don't want to get any "cease and desist" letters myself, so I want to stress that I am not making any suggestion that Microsoft has behaved in an unreasonable way in this matter. I have every confidence that you can continue to think of Microsoft as one of the family; like, say, a brother – a big brother.

Have I proved the cause and effect – that Microsoft invoked the clause because the report was damning? No, at this point we run out of evidence so it is up to you to draw your own conclusions. I clearly drew mine 10 years ago.

Perspective

In the hopes of forestalling a "so this proves that Microsoft is a tyrant and that SQL Server is rubbish" response, bear in mind that this is history – it certainly tells us that 10 years ago Microsoft could be heavy handed and that SQL Server 6.5 was a poor product. But companies and products do change.

My belief is that SQL Server is now an excellent product. I would also stick my neck out and guess that Microsoft would probably not act in the same way today. This is not because, as a corporation, it cares particularly about truth and honesty; corporations are not the same as people and have different drivers and objectives. But I do think that Microsoft has learnt that a heavy hand brings bad PR...with, of course, the odd minor hiccough. ®

Combat fraud and increase customer satisfaction

More from The Register

next story
Ubuntu 14.04 LTS: Great changes, but sssh don't mention the...
Why HELLO Amazon! You weren't here last time
OpenBSD founder wants to bin buggy OpenSSL library, launches fork
One Heartbleed vuln was too many for Theo de Raadt
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
Got Windows 8.1 Update yet? Get ready for YET ANOTHER ONE – rumor
Leaker claims big release due this fall as Microsoft herds us into the CLOUD
Next Windows obsolescence panic is 450 days from … NOW!
The clock is ticking louder for Windows Server 2003 R2 users
Patch iOS, OS X now: PDFs, JPEGs, URLs, web pages can pwn your kit
Plus: iThings and desktops at risk of NEW SSL attack flaw
Batten down the hatches, Ubuntu 14.04 LTS due in TWO DAYS
Admins dab straining server brows in advance of Trusty Tahr's long-term support landing
Red Hat to ship RHEL 7 release candidate with a taste of container tech
Grab 'near-final' version of next Enterprise Linux next week
Apple inaugurates free OS X beta program for world+dog
Prerelease software now open to anyone, not just developers – as long as you keep quiet
prev story

Whitepapers

Mobile application security study
Download this report to see the alarming realities regarding the sheer number of applications vulnerable to attack, as well as the most common and easily addressable vulnerability errors.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.