Oops...sorry

Looking at the GUI angle....

Create another package .....call it Main

In the main package:

call package1 --> call package2 --> on success call store proc (sql task).

what do you mean by depends on indexes? can u give example?

Trying my luck....

declare @date datetime

select @date = getdate()

select convert(varchar(22),@date,100)

whic one is better?

personally, I still like Remi's query. It's easier to understand.

Igor, my apology the query below should work. It was my bad I didn't drill deep enough.

insert into #tmp (name) exec('select top 9 name from [SAVVIS-Reporter].master.dbo.sysobjects')

Just one question, why  don't you want...

Most of the times I go direct to books online.

one way to get around it...

select taskid,taskname,entrydt from task 

where task.entrydt >= @x and task.entrydt < dateadd(dd,1,@x)

declare @x datetime

set @x= '29/06/2004' --datetime doesn't like this format. How about '29-Jun-2004' ??

OR

'29/Jun/2004' ?

Ray is right. Table can be dropped. The view that referenced this table still exists but unviewable.

I've never tried insert and exec() in one statement before. But I think the problem is you're missing a 'select' statement.

insert into #tmp (name) exec('select top 9 name from [SAVVIS-Reporter].master.dbo.sysobjects')...

Just wondering is there anything that you write as a function but cannot re-written in SP ???

There are so many rules bound to views for update/insert/delete!!!!

one rule states UPDATE statement cannot affect more than one of the base tables referenced in the FROM clause of the...

Remi, do you mean something like this?

Select *

from dbo.SysObjects

option (maxdop 1)

Remi, not sure which query you'r ereferring to?

If you're talking about the query below it only reads everything from sysobjects.

Select * from dbo.SysObjects maxdop1