A. v6.5 is still available from Microsoft fulfillment. You need to buy 7.0 and associated licenses and then call the Microsoft Fulfillment office with the serial number(s)/details and they will ship you the 6.5 media.
Applies to SQL Server versions : 7.0
Related FAQ articles : n/a
Related Microsoft Kb articles : n/a
Other related information : n/a
A. The process concerned is accessing an area of memory that SQL Server needs to protect against multiple access - typically on SMP servers. To this end it locks that area of memory (via a spin lock) so that any other access to it gets paused. In concept it is very similar to row/page locking in a database, but is used for internal memory areas within a program. There is plenty of documentation in the Win32 SDK/MSDN about spin locks and their usage.
A. SQL Server is dependent on network functionality - even for the set-up routines. Specifically it needs to use named-pipe/mailslot functionality on NT machines. These usually require a network card to be present. If you don't have a network card then go to control panel/networks, choose add adapter and then add the Microsoft loopback adapter - which is just a dummy driver, no hardware involved. This needs to have working network protocol(s) bound to it. Let whichever protocols you have use default parameters, EXCEPT for tcp-ip.
A. SQL Books Online is a good source, as is Technet with 100's of techie articles/whitepapers on SQL as well as the Knowledgebase. The SQL 7.0 books-online can be downloaded at http://support.microsoft.com/download/support/mslfiles/sqlbol.exe
A. Two things may be happening - either SQL Server is internally gpf'ing/AV'ing (same thing) - you should see messages to this effect in the SQL errorlog. Or there is a net-lib bug with overlapped/fragmented packets.
For either problem you can try applying the latest SP to the server.
For net-lib bugs you will need to apply to the client as well. Also the version of ADO/ODBC can help cause the problem as well, so try upgrading. The latest versions of these drivers can be had via www.microsoft.com/data.
A. There are several ways, but the >>ONLY<< way you can be sure of an engineer looking at it and providing you with a workaround/fix is to report it to Microsoft's PSS (Product Support Services) team. These are people who support all MS's products, write fixes, take the calls, sort out workarounds etc. They work 24x7x365. You can call them by phone (U.S. is 1-800-936-3500)
For details of your nearest PSS support centre and other info try :-
Microsoft provide support for at least the current and previous version of a product (service-packs don't count). So with 6.5 and 7.0 out Microsoft will actively support 6.5 until the next version of SQL comes out - active means fixing the code and issuing servicepacks and hotfixes. The next version - SQL 2000 (Shiloh) - is due by the end of 1H 2000.
I am getting a message 'dbprocess dead' or 'language exec' from SQL Server.
I am seeing an 'Exception Access Violation' message in the SQL errorlog.
I am getting *.DMP files in the <sql>\log directory.
I am getting "symptom dump" messages.