Microsoft's Knowledge Base is a great source for SQL Server how-to information, recent bug fix information, and problem workarounds. Microsoft Product Support Services (PSS) constantly updates the Knowledge Base, so check it out periodically. (You can search the Knowledge Base at http://search.support.microsoft.com/kb/c.asp.) Here are seven recent and helpful Knowledge Base Information articles.
If you haven't applied Service Pack 2 (SP2) yet, check out "SQL Server 7.0 Service Pack 2 Fixlist," which lists all of SP2's SQL Server 7.0 and Microsoft Data Engine (MSDE) fixes. The article also has links to the SP1 fixlist and to an article that explains how to obtain SP2.
Database Consistency Checker (DBCC) uses the tempdb database as temporary storage. "How to Determine Tempdb Size Required by DBCC CHECKDB" explains how to estimate the amount of temporary storage that DBCC will need before you run it against large databases.
Installing SQL Server 7.0 on Microsoft Cluster Server can be troublesome. "Troubleshooting SQL Cluster Wizard Failures" explains how to use the SQL Server Cluster Wizard. The article also describes specific problem scenarios and offers step-by-step solutions.
English Query is powerful, but it generates queries that only SQL Server 7.0 can use. "Allow an English Query to Interact with Non-SQL7 Data" explains how to set up a heterogeneous query that lets English Query access other databases, such as Microsoft Access, SQL Server 6.5, and Oracle.
If you've ever wanted to try to save storage by compressing the hard disk volume that contains SQL Server data, you need to read "SQL Server Databases Not Supported on Compressed Volumes" and think again. This article explains why using compressed volumes for SQL Server data is a bad idea.
Getting information from a standard stored procedure output parameter is simple, but getting return-code information isn't. "Output Parameters, Return Codes and the ODBC Driver" describes how to use the SQLMoreResults() function to access stored-procedure return-code information from an ODBC application.
SQL Server's built-in backup can back up the transaction log only if both the primary data file and the log data file are accessible. This requirement can be a problem if the primary data file and master database are on damaged media but the log file is intact. "How to Backup the Last Transaction Log When the Master and the Database Files are Damaged" explains how to recover the log by using a temporary database and the Backup Log command