The more indexes you add, the more it costs to maintain them. But if that costs is less than the cost of a slow query then it can be...

Sure :

GO

CREATE PROCEDURE dbo.Test @Dividor as int

AS

SET NOCOUNT ON

Declare @Er as int

begin tran

Select 10 / @Dividor

Set @Er = @@Error

if @Er 0

begin

print 'There''s an error'

rollback tran

end

else

begin

print 'No problem --...

How the heck did he do that without noticing he was screwing something up??

Good idea, it's true some forums are very specialized...

You'd never do that, would you??

No, I don't know that trick... I usually just copy/paste the whole thing directly and it works.

1=2 returns only the metadata, no select is actually done.

Care to outline the logic of this thing???????????????????????

I can so picture myself doing that .

Maybe we should redo that disaster contest. Looks like we'd have a few new inputs

I see you have way more experience in that area than me. Thanx for sharing.

While I don't know anything about reporting services either, I can suggest that you have a single query (stored proc) with DateFrom parameter that you can set on the client....

I knew you could help him . I must be able to see the future or something

Sorry, didn't mean to rant on you .

You have nothing to fear on that matter.

The only slight ill effect is that when you drop/recreate a proc, the dependencies to other objects are lost because they are deleted...

Seems to me like the problem comes from the reporting side of the process. Can you go into debug mode to see why it's being called so often?