Skip to main content

Installing SQL Server 2000 Server Components in Windows XP Media Center

Check out my previous experience on installing SQL Server Enterprise and Developer Edition in a Windows XP Media Center box.

The error which i was getting all this while is "Microsoft SQL Server 2000 Enterprise Edition Server Component is not supported on this operating system. Only client components will be available for installation." and "Microsoft SQL Server 2000 Developer Edition Server Component is not supported on this operating system. Only client components will be available for installation."

Later I have downloaded SQL Server 2005 Express edition and after some initial struggle I have installed it.

Today I was again thinking why am I not able to install the DEV version as it is supposed to be installed on Windows XP professional itself. So I reinitiated the installation process and the results were surprising to me.

First I wanted to install MSDE and then try SQL 2000 DEV version.

Installing MSDE:

Step 1: I downloaded MSDE 2000 from Microsoft and ran the installation file (MSDE2000A.exe)

Step 2: Went to command prompt (Start >> cmd)

Step 3: Ran the setup file. Though there are various parameter switches which can be used along with this setup file, I used the bare minimum options only.

Setup.exe InstanceName=db2000MSDE SAPWD=velias SecurityModel=SQL

Here, InstanceName == name of the MSDE instance, SAPWD == password of the SA account and SecurityMode == SQL (Mixed mode).

Check out this to know all available parameters. Btw, MSDE doesn’t have any user interface and it is designed to work as a background service.

Step 4: Navigate to Adminstrative tools >> Services and we could now find MSSQL$YourInstanceName there.

Installing SQL Server 2000:

After installing MSDE now I tried installing SQL Server 2000 Enterprise Editio. But it wasn’t successful (Only client tools were getting installed).

Next I tried my luck with SQL Server 2000 Developer edition and to my surprise this time it got installed. I am really surprised because previously I was also trying the same thing but I didn’t have MSDE then. So is MSDE necessary for installing Developer edition of SQL Server 2000 in Windows XP Media Center? Still I don’t think so!!

Just for my better understanding I uninstalled SQL 2000 DEV edition and MSDE from my box. Then without installing MSDE I directly installed SQL Server 2000 Developer Edition and it installed without any issues at all. I am confused :) Have anyone of you guys come across this issue?

Technorati Tags: , ,

Comments

Anonymous said…
am facing a similar problem.
Anonymous said…
Even I have the same issue. When i installed SQL Server 2K edition on xp - it went fine, but now i get an error saying "set up couldnot configure Server on the machines. Set up would abort!"" Kindly suggest!! Pls reply to sharma.amitkumar@yahoo.com

Popular posts from this blog

Registry manipulation from SQL

Registry Manupulation from SQL Server is pretty easy. There are 4 extended stored procedure in SQL Server 2000 for the purpose of manupulating the server registry. They are: 1) xp_regwrite 2) xp_regread 3) xp_regdeletekey 4) xp_regdeletevalue Let us see each one of them in detail! About xp_regwrite This extended stored procedure helps us to create data item in the (server’s) registry and we could also create a new key. Usage: We must specify the root key with the @rootkey parameter and an individual key with the @key parameter. Please note that if the key doesn’t exist (without any warnnig) it would be created in the registry. The @value_name parameter designates the data item and the @type the type of the data item. Valid data item types include REG_SZ and REG_DWORD . The last parameter is the @value parameter, which assigns a value to the data item. Let us now see an example which would add a new key called " TestKey ", and a new data item under it called TestKeyValue :

Screen scraping using XmlHttp and Vbscript ...

I wrote a small program for screen scraping any sites using XmlHttp object and VBScript. I know I haven't done any rocket science :) still I thought of sharing the code with you all. XmlHttp -- E x tensible M arkup L anguage H ypertext T ransfer P rotocol An advantage is that - the XmlHttp object queries the server and retrieve the latest information without reloading the page. Source code: < html > < head > < script language ="vbscript"> Dim objXmlHttp Set objXmlHttp = CreateObject("Msxml2.XMLHttp") Function ScreenScrapping() URL == "UR site URL comes here" objXmlHttp.Open "POST", url, False objXmlHttp.onreadystatechange = getref("HandleStateChange") objXmlHttp.Send End Function Function HandleStateChange() If (ObjXmlHttp.readyState = 4) Then msgbox "Screenscrapping completed .." divShowContent.innerHtml = objXmlHttp.responseText End If End Function </ script > < head > < body > &l

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul