If exists (select * From tempdb .. sysobjects where id = object_id ('tempdb .. # temp '))
Drop table # temp
Temporary table
You can create local and global temporary tables. The local temporary table is only visible in the current session; the global temporary table is visible in all sessions.
The name of the local temporary table is preceded by a number character (# table_name), and the name of the global temporary table is preceded by two numbers (# table_name ).
The SQL statement uses the name specified for table_name In the CREATE TABLE statement to reference the temporary table:
Create Table # mytemptable (COLA int primary key)
Insert into # mytemptable values (1)
If a local temporary table is created by a stored procedure or is executed by multiple users at the same time Program SQL Server must be able to differentiate the tables created by different users. Therefore, SQL Server adds a digital suffix to the table name of each local temporary table internally. The full name of a temporary table stored in the sysobjects table of the tempdb database is composed of the table name specified in the create table statement and the digital suffix generated by the system. To allow append suffixes, the table name table_name specified for the local temporary table cannot exceed 116 characters.
Unless the drop TABLE statement is used to explicitly remove a temporary table, the system automatically removes the temporary table when it exits its scope:
When the stored procedure is complete, the local temporary table created in the stored procedure is automatically removed. All nested stored procedures executed by the stored procedure of the created table can reference this table. However, the process that calls the stored procedure to create this table cannot reference this table.
All other local temporary tables are automatically removed at the end of the current session.
The global temporary table is automatically removed when the session for this table is created and other tasks are stopped to reference it. The association between tasks and tables is only maintained during the lifecycle of a single Transact-SQL statement. In other words, when the session for creating a global temporary table ends, the table is automatically removed after the last Transact-SQL statement that references the table is completed.
The local temporary table created in the stored procedure or trigger is different from the temporary table created before the stored procedure or trigger is called. If a query references a temporary table with two temporary tables with the same name at the same time, it does not define which table to resolve the query. A nested stored procedure can also create a temporary table with the same name as the temporary table created by calling its stored procedure. All references to table names in nested stored procedures are interpreted as tables created for this nested procedure. For example:
CopyCode The Code is as follows: Create procedure Test2
As
Create Table # T (x int primary key)
Insert into # T values (2)
Select test2col = X from # T
Go
Create procedure test1
As
Create Table # T (x int primary key)
Insert into # T values (1)
Select test1col = X from # T
Exec Test2
Go
Create Table # T (x int primary key)
Insert into # T values (99)
Go
Exec test1
Go
The following is the result set:
(1 row (s) affected)
test1col
-----------
1
(1 row (s) affected)
test2col
-----------
2
when creating a local or global temporary table, the create table syntax supports all the constraint definitions except the foreign key constraint. If the foreign key constraint is specified in the temporary table, the statement returns a warning message indicating that the constraint has been ignored and the table will still be created, but it does not have the foreign key constraint. Temporary tables cannot be referenced in the foreign key constraint.
Use table variables instead of temporary tables. A temporary table is useful when you need to create an index explicitly on a temporary table or use table values for multiple stored procedures or functions. Generally, table variables provide more effective query processing.
