If you create temporary tables in your stored procedure - there will be no problems. Temporary tables are actually created with unique (dependent upon current session) names.
The temporary tables are the tables which will be created in the tempdb of the database. If u have so many temporary tables in the procedure then it will fill the tempdb's allocated space. If the tempdb is full then u may have to restart your system. Moreever if ur using the temporary table and access it paralelly then the tempdb will get locked until the completion of the request of a particular user. So I may cause the performance problem even though it was created with unique id's. It is always suggested to use the table variable like declare @temp table . it will be faster than the tempporary table. This is what i have experienced.
The temporary tables are the tables which will be created in the tempdb of the database. If u have so many temporary tables in the procedure then it will fill the tempdb's allocated space. If the tempdb is full then u may have to restart your system. Moreever if ur using the temporary table and access it paralelly then the tempdb will get locked until the completion of the request of a particular user. So I may cause the performance problem even though it was created with unique id's. It is always suggested to use the table variable like declare @temp table . it will be faster than the tempporary table. This is what i have experienced.
Comment