Indexing otherwise 'temporary' tables - what's fastest?
Thanks for looking,
I am trying to optimize a rather lengthy process (a set of Stored
procedures) that initially combines a number of tables into temporary
tables, then uses these these as reference/input for a dozen or more other
procedures. These tables need to exist only for the process, and can go
away once the process is completed.
My question is:
Is it more effective, effecient, faster, etc., and does it make sense to
tables (with indexes) and populate them for use as these reference tables,
or just to create them completely on the fly as temporary (#<table name>)
tables for the subsequent processes?
I guess I'll try it both ways & see, but if anyone can shed some light on
the technical aspects of which might be better... Any help is appreciated.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL