Re: sp_fkeys stored procedue is very slow
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 18 May 2006 22:07:17 +0000 (UTC)
(keyvez@xxxxxxxxx) writes:
I am trying to find the tables and columns that depends on 'table1'
sp_fkeys @pktable_name='table1'
and this takes about eight seconds, whereas if I run it for finding all
tables and columns that 'table1' depends on
sp_fkeys @fktable_name='table1'
this only takes a second.
How can I speed up the first stored procedure execution?
Are there many tables in the database?
I'm afraid there is not that much you could do. You could of course
script the database from the master database, and play around with a
copy of the procedure, to see if you can make it go faster. One idea
there would be to replace the temp tables with table variables. Tracing
the procedure in Profile would of course also be necessary to see where
the time is spent.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- sp_fkeys stored procedue is very slow
- From: keyvez
- sp_fkeys stored procedue is very slow
- Prev by Date: Re: Copy a table from one DB to antoher in SQL Server 2005
- Next by Date: Re: SQL Server 2000 running out of space.
- Previous by thread: sp_fkeys stored procedue is very slow
- Next by thread: Copy a table from one DB to antoher in SQL Server 2005
- Index(es):
Relevant Pages
|
