Empty tables | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Empty tables

Hello, friends. Can anybody expain to me the purpose of empty tables in db. Can they be the temperaly tables used at some kind of transaction and at the end of transaction data should be automatically deleted from them? I am in the dark here. Please, explain to me the logic behind such design.
Thanks for help.

You need to look at the whole package of database and client application(s) to know what role a table has. It may be that there are some tables in the database that were created in the development stages of the system, and that are not actually used. Or the system does provide the possibility to store data in that table, but that part of the system is not used. But as you say a table could be empty because it is used to upload 3rd party data to the server, then call a stored procedure to merge the data into the database, and at the end the 3rd party data is deleted. I know we’re using this set-up in a system that uses an MS Access front-end.
If you want to find out, put a trigger on the tables to monitor activity. If nothing has been done after…oh, say a year <img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /> then drop the table. You could also use Profiler.<br /><br />MeanOldDBA<br />[email protected]<br /><br />When life gives you a lemon, fire the DBA.