|
|
Posted by Greg D. Moore \(Strider\) on 02/19/07 23:15
"Gert-Jan Strik" <sorry@toomuchspamalready.nl> wrote in message
news:45DA261B.75D850BB@toomuchspamalready.nl...
> teddysnips@hotmail.com wrote:
>>
>> In a system I'm maintaining there is a Stored Procedure called
>> dbo.MyStoredProcedure. I didn't create this - it was created by a
>> developer who has now left. I don't know how the object came by its
>> "dbo." prefix, but I think he created it in QA.
>>
>> Anyway, there were some performance issues (it was taking between 4
>> and 10 seconds to complete) so I copied the SQL into a QA window and
>> it consistently ran in under 1 second. So I created a new SPROC with
>> SQL exactly identical to the old one, but without the "dbo." prefix,
>> and that too runs in <1 second.
>>
>> Any thoughts?
>>
>> Edward
>
> Maybe all the stored procedure needed was a recompilation. Maybe it had
> nothing to do with the dbo prefix.
>
> Please post back if the behavior is consistent (IOW, if performance
> degrades if you change it back to the dbo prefix).
>
Duh, didn't even think of recompilation.
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
> Gert-Jan
Navigation:
[Reply to this message]
|