Very Computer

I'm using Query Analyzer for SQL Server 7.0 on a table that contains 153,676
rows and a DBCC CHECKTABLE shows that 13,102 pages are allocated.  There are
no text or image columns in this table and no indexes.  When a SELECT * INTO
Table2 FROM Table1 it takes 30 seconds.  When I run a simple SELECT * FROM
Table1 , I stop it at 3 minutes and only 26,000 records have been returned.

I guess I don't understand why the SELECT * INTO is so much faster than a
SELECT * from the same table.  Is this a problem with Query Analyzer and
large result sets?

SELECT INTO does not generate a result set that need to be displayed on the
client, SELECT FROM does. Depending on your target in SQL QA Text Windows or
Grid you will also see different performance, Text Window will draw line by
line, where the grid build the result set in memory on the client and draws
from there. That is why in grid mode you only see results when the query is
completed and all results are fetched from the server.

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
? 2001 SQLDev.Net All rights reserved.

Quote:> I'm using Query Analyzer for SQL Server 7.0 on a table that contains
153,676
> rows and a DBCC CHECKTABLE shows that 13,102 pages are allocated.  There
are
> no text or image columns in this table and no indexes.  When a SELECT *
INTO
> Table2 FROM Table1 it takes 30 seconds.  When I run a simple SELECT * FROM
> Table1 , I stop it at 3 minutes and only 26,000 records have been
returned.

> I guess I don't understand why the SELECT * INTO is so much faster than a
> SELECT * from the same table.  Is this a problem with Query Analyzer and
> large result sets?