Performance wise (view or Temp Table )Which one is better

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 Performance Tuning » Performance wise (view or Temp Table )Which...

Performance wise (view or Temp Table )Which one is better

Rate Topic

Display Mode

Topic Options

Author

Message

Raghu.K

Posted Tuesday, December 18, 2012 3:43 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, December 31, 2012 3:01 AM
Points: 18, Visits: 35

Hi ,

Table A is having 1 million Records, Table B is having 100 million Records.
I need to show data (for report pupose) from both the tables using join basing conditions.

Which one is better : View or Temp Table (Performance wise)
Please help me in that

Post #1397663

anthony.green

Posted Tuesday, December 18, 2012 3:51 AM

SSCertifiable

Group: General Forum Members
Last Login: Friday, April 12, 2013 3:51 AM
Points: 5,075, Visits: 4,831

Depends what you are trying to do.

Please follow the link in my signature on posting code and data for the best help.

But with a temp table you would have to load and then read, where as a view would be a read so less going on via a view.

That being said why not a procedure?

What is the structure of the tables?
What is the index definitions on the tables?
What is the joining criteria?
Is there referential integrity between the tables?

Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1397665

opc.three

Posted Friday, December 21, 2012 5:58 AM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 2:41 PM
Points: 6,696, Visits: 11,714

Regular views offer nothing from a performance standpoint. Views are simply replaced by their definition in the query submitted for execution and then optimized as if the query submittor had supplied the entirety of the view-query themselves.

For example, if I have a view named dbo.SomeData defined as:

CREATE VIEW dbo.SomeData
AS
SELECT ColumnName FROM dbo.SomeTable;
GO

and I say

SELECT * FROM dbo.SomeData;

this (in general terms) is what the query engine will eventually optimize after view-replacement is done:

SELECT * FROM (SELECT ColumnName FROM dbo.SomeTable);

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato

Believe you can and you're halfway there. --Theodore Roosevelt

Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein

The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein

1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy

Post #1399359

« Prev Topic | Next Topic »

Permissions