您要查找的是不是：
- The DELETE statement is used to delete rows in a table. delete 声明常用来删除表中的数据。
- The DELETE statement succeeds, even though the CHECK constraint specifies that table CheckTbl must have at least 1 row. 即使CHECK约束指定表CheckTbl必须至少包含1行,DELETE语句也会成功。
- After a CTE is defined, it can be referenced like a table or view can in a SELECT, INSERT, UPDATE, or DELETE statement. 定义CTE后,可以在SELECT、INSERT、UPDATE或DELETE语句中对其进行引用,就像引用表或视图一样。
- At most, one INSTEAD OF trigger per INSERT, UPDATE, or DELETE statement can be defined on a table or view. 对于表或视图,每个INSERT、UPDATE或DELETE语句最多可定义一个INSTEAD OF触发器。
- Variable, within its scope, also can be used as a table source in a DELETE statement. 在其作用域内还可用作DELETE语句中的表源的。
- A FOREIGN KEY constraint on the table prevents the DELETE statement from succeeding and a constraint violation error is generated. 此表的FOREIGN KEY约束将阻止成功完成DELETE语句,并生成一个违反约束错误。
- To replace data in a table, the DELETE statement must be used to clear existing data before loading new data with INSERT. 若要替换表中的数据,在使用INSERT加载新数据之前,必须使用DELETE语句清除现有的数据。
- The stored procedure usp_GenerateError executes a DELETE statement inside a TRY block that generates a constraint violation error. 存储过程usp_GenerateError在TRY块内执行DELETE语句,该语句生成违反约束错误。
- Specifies the temporary named result set, also known as common table expression, defined within the scope of the DELETE statement. 指定在DELETE语句作用域内定义的临时命名结果集,也称为公用表表达式。
- UPDATE, INSERT, and DELETE statements factored into analysis? 分析中将UPDATE、INSERT和DELETE语句作为考虑因素吗?
- CHECK constraints are not validated during DELETE statements. 执行DELETE语句时不验证CHECK约束。
- Transact-SQL scripts, stored procedures, and triggers can use the WHERE CURRENT OF clause on a DELETE statement to delete the cursor row on which they currently are positioned. Transact-SQL脚本、存储过程和触发器可以使用DELETE语句中的WHERE CURRENT OF子句来删除它们当前所在的游标行。
- The SQL Server query optimizer ignores the READUNCOMMITTED and NOLOCK hints in the FROM clause that apply to the target table of an UPDATE or DELETE statement. SQL Server查询优化器忽略FROM子句中应用于UPDATE或DELETE语句的目标表的READUNCOMMITTED和NOLOCK提示。
- For example, if a data page is deallocated by the CHECKDB process, the Log Reader Agent does not translate this to a DELETE statement; therefore, the change is not replicated. 例如,如果数据页由CHECKDB进程释放,则日志读取器代理不会将它翻译为DELETE语句;因此,更改将不会复制。
- TRUNCATE TABLE is functionally the same as the DELETE statement with no WHERE clause; however, TRUNCATE TABLE is faster and uses fewer system and transaction log resources. TRUNCATE TABLE在功能上与没有WHERE子句的DELETE语句相同;但是,TRUNCATE TABLE速度更快,使用的系统资源和事务日志资源更少。
- Table variable. The DELETE statement may fail if it violates a trigger or tries to remove a row referenced by data in another table with a FOREIGN KEY constraint. 如果DELETE语句违反了触发器,或试图删除另一个有FOREIGN KEY约束的表内的数据被引用行,则可能会失败。
- For example, if user Mary executes a DELETE statement that causes DML trigger DML_trigMary to run, the code inside DML_trigMary executes in the context of the user privileges for Mary. 例如,如果用户Mary执行可以使DML触发器DML_trigMary运行的DELETE语句,则DML_trigMary中的代码将在Mary的用户特权上下文中执行。
- A searched DELETE statement deletes multiple rows if the search condition does not uniquely identify a single row. 如果搜索条件不唯一标识单行,则搜索DELETE语句删除多行。
- The DELETE statement removes rows one at a time and records an entry in the transaction log for each deleted row. DELETE语句每次删除一行,并在事务日志中为所删除的每行记录一个项。
- Any modifications, including UPDATE, INSERT, and DELETE statements, must reference columns from only one base table. 任何修改(包括UPDATE、INSERT和DELETE语句)都只能引用一个基表的列。
