HTH.

You're not joining the new table to the rest of the query. I also assume that you have a whole bunch of duplicate data or numbers that are way...

Select * from dbo.YourTable where ISDATE(DateCol) = 0

That'll give you a list of invalid dates.

Otherwise, check out the SET DateFormat command in BOLS.

By duplicating, I assume you mean to copy/reinsert all rows >>

Insert into dbo.crs_schedule (break_time, type, branch_id)

Select break_time, 1 as type, branch_id from dbo.crs_schedule

otherwise you just need a simple update statement.

Not it's not the only solution >>

CREATE TABLE [Test] (

[Pktest] [int] IDENTITY (1, 1) NOT NULL ,

[Name] [varchar] (50) COLLATE Latin1_General_CS_AS NOT NULL ,

CONSTRAINT [PK_Test] PRIMARY KEY CLUSTERED

(

[Pktest]

)...

Yup, that's the power of the numbers table .

Sure, then you can get your server hacked because of dynamic sql.

Read the article, use the split function, or use this for a shortcut.

IF Object_id('fnSplit_Set') > 0

DROP FUNCTION dbo.fnSplit_Set

GO

IF Object_id('Numbers')...

Please learn to use a set based approach. There's just no need for a cursor in that select.

Let's start over.

Post the table DDL, some sample data and the required output. We'll see what we can do.

The insert statement MUST look like this :

Insert into SomeTable (col1, col2...)

Select col1, col2... from YourOuterDataSource

Which will be faster actually...

Have you tested that EACH and EVERY single row as 36 numbers in each column. If not I'd add another check to make sure both...

The closer to the data you do this, the better. If you use dependencies then noone can enter bad data (assuming everything is correctly validated). But even with...

You might wanna do that in batch... unless you have LOADS of ram and a quiet morning on the server. This kind of operation takes a lot of ram/processor...

Please POST IT.

What did you try?