Microsoft sql server 2000 windows 10

I have to admit it, that when I first heard about this I was HIGHLY skeptical, but sure enough it actually works.

Картинка с сайта: virtuallyfun.com

Enterprise Manager looking at the infamous PUBS database

Although I have gotten SQL Server 4.21a & 6.5 running on Windows 10 (The core from 6.0 works, but it’s pre-release COM objects for the Enterprise manager don’t like Windows 10) There were two stumbling blocks I never could get around.  The first one turned out to be something trivial, which is SQL 4.21 would never listen on TCPIP.

Fixing SQL 4.21

It turns out that this actually was a simple fix.

17/09/21 19:40:24.00 server server name is ‘JADERABBIT’
17/09/21 19:40:24.00 server Recovering database ‘model’
17/09/21 19:40:24.00 server Recovery dbid 3 ckpt (45,26)
17/09/21 19:40:24.00 server Clearing temp db
17/09/21 19:40:24.03 kernel Using ‘SQLEVENT.DLL’ version ‘4.21.00’.
17/09/21 19:40:24.83 kernel Using ‘OPENDSNT.DLL’ version ‘4.21.09.02’.
17/09/21 19:40:24.83 kernel Using ‘NTWDBLIB.DLL’ version ‘4.21.00’.
17/09/21 19:40:24.83 ods Using ‘SSNMPNTW.DLL’ version ‘4.21.0.0’ to listen on ‘\\.\pipe\sql\query’.
17/09/21 19:40:24.83 ods Using ‘SSMSSOCN.DLL’ version ‘4.21.0.0’ to listen on ‘1433’.
17/09/21 19:40:26.04 server Recovering database ‘pubs’
17/09/21 19:40:26.06 server Recovery dbid 4 ckpt (469,25)
17/09/21 19:40:26.06 server Recovering database ‘ultimate’
17/09/21 19:40:26.06 server Recovery dbid 5 ckpt (524295,12)
17/09/21 19:40:26.06 server Recovery complete.
17/09/21 19:40:26.12 server SQL Server’s default sort order is:
17/09/21 19:40:26.12 server ‘bin_cp850’ (ID = 40)
17/09/21 19:40:26.12 server on top of default character set:
17/09/21 19:40:26.12 server ‘cp850’ (ID = 2)

The DLL for TCP/IP is SSMSSOCN.DLL, and it turns out it really wants to be located in the C:\Windows\SysWOW64 directory (aka the system path for libraries).  Well that’s all great now, isn’t it?

Not really.

ODBC Hell

The ODBC drivers in Windows 10 finally made a magical cut off point that they will not talk to any old and ‘vulnerable’ SQL Servers.  This means that the oldest version you can connect to is SQL Server 2000.  Even SQL 7 didn’t make the cut.  Trying to connect to a SQL 7 server, you just get:

Attempting connection
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context

And then I saw this post, about using FreeTDS to connect to MSSQL.  So I followed their instructions, and got nowhere fast just lots of crashing.  Turns out the bloodshed environment’s included G++ just fails 100% of the time for me, with a nice crash.  So I pointed it to the TDM GCC install, and then had to link the DLL manually and… nothing.  No configuration point.  In a fit of rage, I took the exist msvc project, opened it in Visual Studio 2015, and built it, except for one issue…

odbccp32.lib(dllload.obj) : error LNK2019: unresolved external symbol __vsnwprintf_s referenced in function _StringCchPrintfW

Seriously, it turns out that 2015 can’t just link to ODBC, that the libc thing that gave me SDL grief is deeply entrenched all over the place.  So in this case you need to link against legacy_stdio_definitions.lib. Fantastic.

I get my DLL, and yes, it’s a Windows 32bit ODBC driver!

Картинка с сайта: virtuallyfun.com

FreeTDS Access failure

And yeah, lots of failure.

A red-herring was seeing this in the trace:

net.c:741:Sending packet
0000 01 01 00 2b 00 00 00 00-53 45 4c 45 43 54 20 43 |…+…. SELECT C|
0010 6f 6e 66 69 67 2c 20 6e-56 61 6c 75 65 20 46 52 |onfig, n Value FR|
0020 4f 4d 20 4d 53 79 73 43-6f 6e 66 |OM MSysC onf|

So I was thinking that SQL 4.21 & 6.5 are just too old to have this weird table, and as mentioned over here people would just create it, to get Access to shut up, and get on with their lives.

So, I put in some SQL

CREATE TABLE MSysConf(CREATE TABLE MSysConf(Config   int NOT NULL,chValue  char(255) NULL,nValue   int NULL,Comments char(255) NULL)
GO
INSERT INTO MSysConf(Config,nValue,Comments)VALUES(101,1,’Prevent storage of the logon ID and password in linked tables.’)
GO

And yes, it creates the table, Access get’s it’s result then obviously doesn’t like it and up and dies.  Maybe I can burn more cycles on it later, or break down and ask.

***UPDATE As a follow up, check out Loading the MS SQL 6.5 drivers on Windows 10, for enabling ODBC access on newer versions of Windows.

SQL Server 2000 (Dev) on Windows 10

And then I saw this epic thread, Windows 10 & My SQL Server 2000 Personal.

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

**UPDATE

Newer versions of Windows 10 don’t include the old Visual C++ runtime, and the install will fail.  Just copy the DLL’s into the syswow64 directory.

copy SP4\x86\system\msvc?71.dll \Windows\SysWOW64

This is tested on 17134.112 Version 1803 of Windows 10.

Could that really be it?  For some reason I had a file held in the Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\PendingFileRenameOperations registry key, preventing me from installing, but zapping the key & stub program, and I was able to follow the steps (I’m still not sure if you copy the dlls into the MSSQL\Binn or Tools\BInn directories, so I copied them to both!) and yes, it worked.  I even could run the SP4 update.

And now I can use Access 2016 with this fine ancient database.

Картинка с сайта: virtuallyfun.com

Access 2016 with SQL 2000 via ODBC

And here we are.  As always there is no larger over reaching point to this.  I did have to create a linked SQL login for myself to get ODBC to login properly but it’s somewhat simple, and honestly if that sounds bizarre to you, why are you even thinking about something like this?

For me, I’m interested in the DTS of all things.  Sure the new ones are fancier, and all that jazz, but I paid good money back in the day for old MS dev tools, and being able to use them without any virtualization, aka running on bare iron is all the more appealing.

• Hello,
  Need to install SQL 2000 on Windows 10, and getting the following error on running set up, any advice, Please point to me to a right direction.
  Thanks for your time, Very much appreciated of your help and suggestions. Thanks.
  ========================================================
  Setup initialization error.,sqlsut.dll
  Target: ‘C:\DOCUME~1\AMINI~1\LOCALS~1\Temp\SqlSetup\Bin\sqlsut.dll’
  ========================================================

• e4d4

  SSCertifiable

  Points: 5777

  You can’t. Create virtual machine with supported by MSSQL 2000 OS, it will be Windows 2003 for (MSSQL 2000 SP3) and install there.

• Joe-420121

  Hall of Fame

  Points: 3152

  Thank you e4d4, very much appreciated of your help & support.

• Thom A

  SSC Guru

  Points: 99137

  I have to ask by WHY do you want to install SQL Server 2000? It hasn’t been supported for a very long time. You should really be using more recent technology. Plus, using Windows 2003 server, or a similar dated OS, is just making the problem worse.

  For example, none of these services/OS’s would have been patched against Spectre or Meltdown, and I’m sure there are other similar vulnerabilities that still exist on those old editions as well. Using something like as old as that brings huge security flaws into the mix.

  Thom~

  Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
  Larnu.uk

• Joe-420121

  Hall of Fame

  Points: 3152

  Hello Thom,
  I totally agree to your comments, I am working with customer having still SQL 2000/ 7 as well, Working hard to migrate them. Meanwhile need to support, Thanks for your comments and thoughts.

  Only your fingers NOT able to co-operate faster enough to your speedy brain 🙂 🙂
  Thanks for your time, Very much appreciated.

• Rachel Gomez

  Valued Member

  Points: 68

  To install Microsoft SQL Server 2000 Client Tools, do the following steps:

  • Insert the Microsoft SQL Server 2000 Enterprise Edition CD and click SQL Server 2000 Components.
  • Click Install Database Server.
  • The Microsoft SQL Server 2000 Enterprise Edition setup begins. The InstallShield guides you through the installation. Follow the instructions in the windows. Click Next.
  • From the Welcome window, read the information and click Next.
  • From the Computer Name window, click Local Computer and click Next.
  • From the Installation Selection window, click Create a new instance of SQL Server, or install Client Tools. Click Next.
  • From the User Information window, type your name and company. Click Next.
  • From the Software License Agreement window, read the license information. You must accept the license agreement to continue the installation. Click Yes.
  • From the Installation Definition window, click Client Tools Only. Click Next.
  • From the Setup window, type your CD key information and click OK.
  • Your product ID is displayed in the second setup window.
  • Follow the instructions and click OK to continue.
  • From the Setup Type window, click Next to accept the default values.
  • From the Select Components window, click Next to accept the default values.
  • When the Start Copying Files window opens, click Next to continue with the installation.
  • If you want to change any parameters, click Back. When you click Back, selections reset back to their default values. If you click
  • Back at any time during the installation, make sure you reselect the values you wanted before clicking Next.
  • Click Finish on the Setup Complete window.

  Disabling Selected SQL Server 2000 Query Analyzer Options

  Certain SQL Server Query Analyzer options must be manually disabled in SQL Server 2000 for every Windows(R) account that is used to run the Query Analyzer tool.

  To disable these options, do the following steps:

  1. Start the SQL Server 2000 Query Analyzer. Click Start -> Programs -> Microsoft SQL Server -> Query Analyzer.
  2. In the Connect to SQL Server window, enter the database server name in the SQL Server field. Leave the Start SQL Server if it is stopped check box clear. Type your password. Click OK.
  3. From the Query Analyzer window, click Tools -> Options.
  4. Click the Connection Properties tab.
  5. Make sure the only check box selected is Set arithabort. (Clear the Set concat_null_yields_null check box and the Set ansi_defaults check box. Make sure this clears all seven check boxes underneath it).
  6. Click Apply, then OK to close the window.
  7. Close the Enterprise Manager and SQL Server Query Analyzer applications.

  Regards,

  Rachel Gomez

• Thom A

  SSC Guru

  Points: 99137

  Apart from none of that will work on Windows 10, Rachel; SQL Server 2000 cannot be run on Windows 10. Windows 10 wasn’t even a glint in Microsoft’s eye when SQL Server 2000 came out.

  Thom~

  Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
  Larnu.uk

• September 6, 2022 at 7:02 am

  This was removed by the editor as SPAM

I have a Point of Sale software which has database in SQL Server 2000 SP4. It installed fine under compatibility settings under Windows 8.1. Then the PC was upgraded to Windows 10. But on upgrade to 10, it started throwing out an error «1st Ordinal missing» on booting. So as mentioned on the internet by someone, I uninstalled it using Total Uninstaller because the damn thing wouldn’t even uninstall.

So after cleaning the system off all the SQL Server related stuff, I tried to install it again. But setup was quitting unexpectedly without throwing any message.

Hence I re-installed Windows 10 (Fresh Install this time) but the the setup of SQL Server 2000 SP4 still quits unexpectedly.

How can I install it? Been trying since last 2 days and this being production machine, my work is suffering.

Any help Neowin?