FIX: Slow Query Performance When Non-SA Executes Query That Causes Trigger to Access the INSERTED or DELETED Tables

This article was previously published under Q278671
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 58473 (SQLBUG_70)
Query performance may be slow when all of the following conditions apply:
  • Either Service Pack 1 or Service Pack 2 is installed on the SQL Server.
  • You are not logged in as a System Administrator.
  • You execute a query that causes a trigger to be fired.
  • The trigger directly accesses the INSERTED or DELETED trigger tables.
Inaccurate row estimates for the INSERTED and DELETED tables are used prior to Service Pack 3, which results in suboptimal table scans instead of index seeking when the user is not a System Administrator.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Article ID: 278671 - Last Review: 11/02/2013 00:43:00 - Revision: 3.0

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB278671
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)