looks like a 2008 hint not 2005

HI Mike,

Could you confirm that this solved, I noticed that other people are still spending time on this post, when looks like it might be fix?

what is the error you getting?

are you saying that when you run your proc you have no idea what the columns are?

Try this:

DECLARE @table TABLE

(id INT,

Name VARCHAR(10),

Col1 BIT,

Col2 BIT,

Col3 BIT)

INSERT INTO @table

SELECT 1, 'Carlos', 1, 0, 1

--START

DECLARE @sql VARCHAR(MAX)

SELECT [CoLName], [Include]

FROM

(SELECT Col1, Col2, Col3

...

why does it fail?

What is the error?

:hehe:

Sorry I'm an idiot 😀

obviously a varchar need cofffffffeeeeee

are you sure?

My script when run seems to work!

could that be became of the format settings on the server?

If in your table you declare rundate as a datetime and just insert into to from sysjobhsitory run date the conversation should happen automatically.

here is an example of the conversion:

DECLARE...

not sure what you saying but:

this table:

DECLARE @Jobs_failed TABLE

(

[name] nvarchar (128),

[message] nvarchar(1024),

run_date int

)

has Run_date defined as an int, which makes it impossible to start anything that looks like this '2009-03-19'

I...

the reason for this is because there is only one insert statement which is using the values key word.

If you delete 3 rows from the table in one statement the...

that field is defined as an INT, so you can't have it in this format: '2009-03-19' are we missing something here?

Oh and you should be starting dates in a datetime,...

just a note, be care when deleting a large number of indexes from a table. You might notice a drastic change in performance 🙂

just incase you need it.

Here is a solution for if you data is stored in table and you want to do more than one row at a time.

DECLARE @table TABLE

(Input...

cool and if you find the solution could you post it here for others who might be trying the same thing.

Or if you have questions post what you have so...