Why bother with a best practice if a simple copy-paste is much faster. Migrating SQL server 2000 to a new machine.

"It's so sexy I want to take it to dinner"

iPod mini video review

MS and several others published WS-Discovery, which seems to be Netbios on steroids and a great addition to UDDI for ad-hoc interaction. One of the scenarios I can think of is dicovering computers running a game of hearts and inviting them to join for round.

Omri has a much better explanation of WS-Discovery and a lot more examples.

The big question however remains, will this spec make it into WSE 2.0, when/if the RTW will be released.

Allthough I prefer to use visual studio or the query analyzer for doing  ms sql development, someone may find this usefull: TOAD for MS SQL Server.

I know I'm a little late joining the party, but untill today the webinterface of dasBlog made me feel at home. Well, I finally switched to BlogJet, instead of rolling my own (offline) bloggingtool and I think it rocks. The only negative point I currently have is the inabillity to post to several categories at the same time (e.g. development and whidbey), which may be a limitation in dasBlog or the posting API.

A great product just got better (and a whole lot cheaper). The single user version (previously only $50,-) is now completely free and and multi-user versions start at $200,- but drop fast to $100,- when you reach 25 licenses.

Update: what's new v 2

[SourceGear Vault via Eric.WebLog()]

Russ Cooper posted the following message concerning the leak on the NBugTraq list today:

1. NT source is NT 4.0 SP3, contains 27000+ files (658MB). It is all NT
4.0 Server except IIS, includes IE 4. No references to Mainsoft (see
http://www.eweek.com/article2/0,4149,1526830,00.asp .)

2. W2K is SP1, a very small subset, IE 5, SNMP, PKI, networking and some
SDK stuff. 28000+ files (338MB - although many of these are empty mail
messages and other crap.) Does contain 3 references to MainSoft. Much of
what is there is available elsewhere.

MS confirmed the leak at;

http://www.microsoft.com/presspass/press/2004/Feb04/02-12windowssource.asp

I'd be very surprised if this leak results in any significant new risk.
Given how hard people have pounded away at the binaries in the past,
pouring over 55,000 source file to find something new in old versions
will likely/hopefully be a very unfulfilling task.

Cheers,
Russ - NTBugtraq Editor

This seems to me as one of the better outcomes of this whole situation, which started yesterday with a newsitem on neowin.net and quickly stormed the internet.

Update:

Couple of corrections.

1. There were 27,142 NT 4.0 SP3 files totaling 338MB.

2. There were 28,782 W2K SP1 files totaling 658MB.

3. It does appear that all of both versions are present, minus IIS.

4. 10,425 of the 27k NT files are actually source totaling 193MB uncompressed.

5. 8,367 of the 28k W2K files are actually source totaling 217MB uncompressed.

Sorry for any confusion. I still contend that the risk is relatively low consider the age of the packages. Both are copies from before the MS security push, and both have had 3 service pack releases since.

Obviously only time will tell.

Cheers,

Russ - NTBugtraq Editor

Still doesn't look very bad to me, except for the relationship between Mainsoft and Microsoft.

Frank Arrigo invited me to join orkut, anybody know where the name came from?

I think it's a cool experiment in social computing, so we'll see where this will lead.

If you feel neglected, because I didn't add you as a friend let me know.

 

Chris Sells starts developing Longhorn's most importand application by addressing issues with the current version.

Inspired by this initiative I started porting Minesweeper to .Net (Whidbey), with the next step, a Longhorn version, when I get a capable machine.

Mark Cliggett answers the question whether PDC attendees will recieve Whidbey updates, the answer is yes and he suggests thes updates will continue untill RTM.

I hope the same will hold true for Longhorn.