If you mess up your Windows Server 2008, don't go crying to Microsoft. They will not be able to help you. From an article detailing end of support dates: If you are running Windows Server 2000 SP4, you should make plans now to upgrade to Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2 (July 13, 2010 is the cutoff).

Although SQL Server 2000 is not supported at all now and MSFT does not support 2000 on a windows server 2008 or 2008 R2 environment, you can install SQL Server 2000 on one of those servers. I think the issue you were running into was related more to installing a developers edition onto a server that already had a 2005 instance that was either standard or enterprise. You might reverse the installation process and install the MSDE version first and then reinstall the 2005 instance. One thing you may run into though are problems with mail and some ODBC connections, which you will have to work around. Even though it IS possible to install on a 2008 server, it is not optimal and you are asking for anomalies (also known as gremlins) to pop up, especially if your Windows server is also 64bit. I would NOT do this in a production environment. But if you have a test environment to play with then try it out.

You can't post new topics. You can't post topic replies. You can't post new polls. You can't post replies to polls. You can't edit your own topics. You can't delete your own topics. You can't edit other topics.

Animal crossing new leaf download code buy. You can't delete other topics. You can't edit your own posts.

You can't edit other posts. You can't delete your own posts. You can't delete other posts.

You can't post events. You can't edit your own events. You can't edit other events.

You can't delete your own events. You can't delete other events. You can't send private messages. You can't send emails. You can read topics. You can't vote in polls. You can't upload attachments.

You can download attachments. You can't post HTML code. You can't edit HTML code.

You can't post IFCode. You can't post JavaScript. You can post emoticons. You can't post or upload images.

I know of no hacks to get SQL Server 2000 to install on an existing Windows 10 installation. There are probably forces against you from both within the setup program (which looks for certain things on the host system) and within the operating system (which prevents many flavors of older software from getting installed, mostly for security reasons but also compatibility, stability, etc).

I have tried in the past and even with compatibility override options I came across the same failures every time. A couple of ideas: • Use a virtual machine. This really is the simplest and most obvious solution. Most (if not all) editions of Windows 10 now support Hyper-V natively; if not, there is always (not free) and (free).

• Install 2000 then upgrade. Not really practical, especially if you want to use the Windows 10 installation you already have, but if you were doing this from scratch, you could install XP/Vista/Win7, all of which should allow you to install 2000, and then upgrade. Take care, though, because some methods of upgrading to Windows 10 will relegate all of your programs and services to Windows.old, and they won't run any more. In either case, firewall the crap out of that thing, because the most recent security patches for 2000 are hard to find, and the ones that I found wouldn't install anyway. I managed to install following these steps: • Extract SP4 • Copy.SP4 x86 other sqlredis.exe to. Originalinstallpath x86 other (this avoid mdac insall freezing) • Create this folder structure (any place): • Microsoft SQL Server 80 Tools Binn • Microsoft SQL Server MSSQL Binn • Find out sqlunirl.dll on SP4 path and copy to Binn folder above • Copy dll files on.SP4 x86 setup to Microsoft SQL Server MSSQL Binn (folder above) • Copy folder structure (created on step 3) to C: Program Files (x86) • Give full access to user logged to **Microsoft SQL Server** folder • Change install compatiblity.

Originalinstallpath x86 setup setupsql.exe • XP SP2 • Run as administrator All these steps are in this tutorial.