I assume that either the source or destination of your data flow is a SQL Server table? If it is, then you can create an Execute SQL task to...

Frank

If the procedure is being called 1000 times but does not use the most appropriate execution plan every time, could this be because you are supplying different parameters each time?...

Would this work?

COALESCE(MyCol + CHAR(13),'') + COALESCE(MyNextCol + CHAR(13,'') + ....

John

Have you considered using SSIS? It has built-in file manipulation tasks, so it should be just what you need.

John

I'm afraid I don't know of any such stored procedure and I've never written a query myself to get this information. I don't think it's possible to take account...

Does this need to work for absolutely any schedule, or are you going to use it only on certain types of schedule, for example transaction log backups that occur every...

If it's a static table then NOLOCK won't help since there won't be any locks...

If all your stored procedures are in the same schema, just grant execute on the schema.

John

Mmmm.... surely by adding the line [font="Courier New"]WHERE r.type = 'L'[/font] at the end?

John

Roland

Try this.

John

DECLARE @BookLoans table

(

BookID int,

StudentID int,

LoanDate datetime,

ReturnDate datetime

)

INSERT INTO @BookLoans

...

OK, that's a good start. When I run that on one of my servers, it returns the name of a job whose next run date is in the past...

Colin

Could your login and the SQL Agent login be interpreting the data 08/11/2009 differently? If you express it in the form 20091108 then there will be no ambiguity.

John

Jim

You need to use the REPLACE function.

John

Gail, that's fair enough. I suppose what it means is that, since the WHERE clause is being supplied as a parameter to the stored procedure, we could end up...