We have a procedure that is ran evry 2 minutes in a windows service. The procedure uses a table variable. It appears tha after a couple hours of execution the server that this service is running on starts to take a performance hit. We have also seen a tremendous increase in timeouts since the implementation of this stored procedure. Is ti possible that the table variable is not being released from memeory?

I have a table with columns
distributor_id ,
brand_id,
year,
month,
total_sales

distributor_id ,
brand_id,
year,
month are my primary keys.

I have records for last 3 years od data.

I have distinct records till last year,
Some are till last month (Current month – 1)
some are till feb 2007…….
some are till jan 2007..

Now i want to insert records to all distinct
distributor_id ,
brand_id,
year,
month
Zero for sales

where i have to take max month + 1 and hardcode as zero till current month + 10 months.

i appreciate if you get me a insert script without cursors.

I think it is efficient to use staging physical tables if result set is very large. because of sp recompilation, locks on tempdb and better use of parallelism

If you read what you have found and it is clearly stated what I have said and it confirms it. They still perform I/O on tempdb.

“A table variable is created in memory, and so performs slightly better than #temp tables (also because there is even less locking and logging in a table variable). A table variable might still perform I/O to tempdb (which is where the performance issues of #temp tables make themselves apparent), though the documentation is not very explicit about this. “