About The Connect to Server Dialog

In server name column, it apears all the server name that i uesed before, but some of them are not available now, how do I remove them?

There isn't a way to be very surgical about this, but you can use the "big hammer" approach and delete the mru.dat file in C:\Documents and Settings\{you}\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell. This obliterates the most-recently-used list of servers. The connection dialog will create a new mru.dat file the next time you connect to a server.

About Sql Server 2005

Does anyone know when such version will be available in this world?
I mean, no beta, ctp, bla,bla
--
current location: alicante (es)Enric
SQL Server 2005 was finaly released on 7 November 2005, what did you mean?
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:DD3938E7-141D-442A-A90C-42D565495EF2@.microsoft.com...
> Does anyone know when such version will be available in this world?
> I mean, no beta, ctp, bla,bla
> --
> current location: alicante (es)|||jesus christ, am I living where I am living?
--
current location: alicante (es)
"Uri Dimant" wrote:

> Enric
> SQL Server 2005 was finaly released on 7 November 2005, what did you mean?
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:DD3938E7-141D-442A-A90C-42D565495EF2@.microsoft.com...
>
>

About Data algorithms

I just want to know what are the data algorithms available for sql server 2005 and can i use data mining as a web service

A list of algorithms with descriptions can be found at this location: http://msdn2.microsoft.com/en-us/library/ms175595.aspx

SQL Server Data Mining can be used as a web service (by sending XML/A requests inside SOAP payloads). A (live) sample for this can be found here: http://www.sqlserverdatamining.com/XMLAThinMiner/

Our client APIs (OLE DB Provider for Analysis Services, Adomd.Net, AMO) can also be used to conect to an Analysis Services HTTP end point. In this context, the web service communication part is encapsulated in our APIs, so your application does not need to distinguish between locally-accessible servers and HTTP end points (other than providing the appropriate connection string)