The postings on this site are my own and do not represent my Employer's positions, advice or strategies.

LifeAsBob

  Monday, May 29, 2017

lifeasbob.com




Home
Blog
bob tech
Calendar
Contact Bob
Pictures
VW Buses
HomeBrew
Cook Book

 

Family_Picture_September_2007_23.JPG

  bob Links
Welcome to Nate
No children without sex--no drunkenness without beer. - Ancient Sumerian Proverb
Wider View Insert

Cluster
DOS
IBM - AS400
MOM
Performance Counters
Service Broker
SQL Server
     Temporary Database
     Views
     Backup
     SQL Mail
     DTS - Data Transformation Services
     Memory
     Security
     Excel
     Jobs SQL Agent
     MSDE
     Install
     DBCC
     User Management
     System Databases
     BCV
     Deadlocks
     Temp Tables
     Find the physical se...
     Enable xp_cmdshell
     Intermittent Connect...
     Connection String Pr...
     Login Error ( State)...
     Turn Default Tracing...
     Re-index fails when ...
     SMO AND DMO
     Tracing of Errors
     Extra carriage Retur...
     Query to find Object...
     Named Instance Port ...
     Adding Domain Login ...
     Rename Logical File ...
     Error 3624 Delete st...
     SQL DMO Error 21776
     NetworkConnections
     SQL Server Service m...
     Trace Flags for Dead...
     Change Server Name
     Alternate to Count(*...
Windows OS

Insert Category

Will be added as a sub-category of, SQL Server
Error 3624 Delete statemen SQL Server Internal Error
KB Article http://support.microsoft.com/default.aspx?scid=kb;en-us;885442 When you compile a delete query that contains sub-queries that use multiple "NOT IN" clauses, you may receive an error message that is similar to the following: Server: Msg 8624, Level 16, State 1, Line 3 Internal SQL Server error Prerequisites This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3). For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base: Restart information You do not have to restart your computer after you apply this hotfix. You must restart SQL Server after you apply this hotfix. To enable this hotfix, trace flag 9057 must be turned on. Trace flag 9057 is a dynamic flag. To turn on trace flag 9057, use either of the following methods: • Run the following statement: DBCC TRACEON(9057, -1) • Add -T9057 to the SQL Server startup parameters. If the hotfix does not solve the problem, you may have to add a OPTION (MAXDOP 1) query hint to the query that is experiencing the 8624 error.