Tag: sql server

Community

SQL Server 2000 may experience errors and stop responding, and error messages may be logged in the SQL Server 2000 error log, when you try to perform a write operation that is not logged

In Microsoft SQL Server 2000, you may experience the following symptoms when you try to perform a write operation that is not logged: 1. The write operation fails, and the following error message is logged in the SQL Server error log: SQL Server Assertion: File: , line=3723 Failed Asse

Community

Making Stored Procedures Readable

(Andrew Novick) Stored procedures can grow to be quite lengthy. I’ve created procedures that are 500 to 1000 lines or more. There are a couple of reasons for this, including the limited coding structure provided by T-SQL. In particular, the limited error handling in SQL Server 2000 forces constan

Community

Writing Database Objects in CLR

(Sahil Malik) My previous article covered the basics of CLR integration in SQL Server 2005. It compared CLR inside SQL Server 2005 with TSQL and extended stored procedures, and discussed the judicious use of CLR in lieu of other available choices. This article takes the discussion further, discussin

Community

The Ntbackup.exe operation may break the differential backup chain of a SQL Server database and may invalidate the differential backups when you perform a snapshot backup of the database

The Ntbackup.exe utility uses the Virtual Device Interface (VDI) to perform a snapshot backup of a Microsoft SQL Server 2000 database. When you use this utility, the operation may break the differential backup chain of the SQL Server database and invalidate the differential backups.

Community

FIX: You may receive a ‘Server: Msg 7358, Level 16, State 1, Line 1’ error message after you run a linked server query in SQL Server 2000 Service Pack 4

When you run a linked server query to Microsoft SQL Server 2000 Analysis Services, and the query uses the OLAP provider, you may receive the following error message: Server: Msg 7358, Level 16, State 1, Line 1 Could not execute query. The OLE DB provider ‘MSOLAP’ did not provide an appropriate