Let me make you a picture of the system tables :

SysObjects : keeps all tables, views, functions, constraints, defaults and so on.

SysColumns : keeps all the columns and parameter...

Glad we could help .

Maybe a simplistic approach, but just to add another option to the logging method... Maybe you could add a step that logs each execution in an history table... untill...

It wasn't too long ago that I read here that there was a way to make the functions work pretty fast (even if it's row by row). It had...

Here's basically how that article concludes :

IF Object_id('ListTableColumns') > 0

DROP FUNCTION ListTableColumns

GO

CREATE FUNCTION dbo.ListTableColumns (@TableID as int)

RETURNS varchar(8000)

AS

BEGIN

Declare @Items as varchar(8000)

SET @Items = ''

SELECT

@Items = @Items + C.Name +...

For my query to work you need to change this '42ADD00B-46AB-4EF5-AD59-DE476FA638D2' to your package id.

I see now, looks like his site is having problems at the moment...

I'm surprised that he didn't post this link as he usually does.. but this will tell you what you're missing :

http://sqljunkies.com/WebLog/amachanic/archive/2004/11/10/5065.aspx?Pending=true

There's never only 1 way to do something in sql server. However there's often a best way. And here's my version of it :

IF Object_id('Split') > 0

DROP...

I said I didn't want dynamic sql in my solution.

Besides if you were to have Millions of lines in either table (especially the Proposals), this would run slower than a...

BTW I've never actually run that on defaults or constraints but I wouldn't expect much problems to come out of this.

Takes even less time to run this... or the fix login sp :

Select 'EXEC sp_changeobjectowner ''' + O.Name + ''', ''WSREGISTER ''' from dbo.SysObjects O where O.Status >= 0...

This should help you :

Select * from msdb.dbo.SysJobHistory where job_id = '42ADD00B-46AB-4EF5-AD59-DE476FA638D2' order by run_date desc, run_time desc

Yes... but AJ already posted the solution. Just open the books online and you'll be able to find the solution.

Nice thinking... but what happens if the list of keywords is dynamic and you still want to use static sql?