I would add a placeholder in the recipe table for the "cloned" ID while you're doing this (if you do this a lot - I'd actually leave it in.)

Once you...

Then either your column # 2 or column # 3 is returning something that can't be cast as a float. Meaning - it's not a number.

So take the CAST...

There's a basic flaw in your joining characteristics. You can't limit by zipcode, then JOIN by zipcode, and expect to get zipcodes other than the ones you join on....

You uncommented the "beginning" of the NULLIF, but not the end:

SELECT raw_payload,

LEFT(raw_payload+'+++', CHARINDEX('+', raw_payload+'+++', 1)-1),

...

Michael Earl (4/29/2008)

---

You should look at the feature lists for the editions of SQL to make sure you do not need standard edition features.

Per-processor licensing seems a lot for you....

If you want to just delete those rows - then

DELETE

FROM raw_data[raw_payload]

Where raw_payload not like '%+%+%'

Following your lead - comments inline

Matt Miller (4/28/2008)

---

Well -...

n1pcman (4/25/2008)

---

Yes that is the problem I do have some bad data, 1 or 2 lines per every 600 is stepped on data its un unavoidable buffering issue with the...

Warren Peace (4/28/2008)

---

I tried as you suggested...

DECLARE @DBNAME varchar(50)

DECLARE @MyCommand varchar(1000)

SET @DBNAME = '_RESTORERECOVER'

PRINT @DBNAME

SET @MyCommand = 'USE [' + @DBNAME + ']'

EXECUTE(@MyCommand)

But the DB never switched to the _RESTORERECOVER...

Well - the quick answer to your question is - it's 31GB now because at some point in the past, it needed to be that size. From possibly...

If you want to post the XML - run...

GSquared (4/28/2008)

---

Matt Miller (4/28/2008)

---

GSquared (4/28/2008)

---

Having StatusID and Active in your Where clause is getting rid of any rows that would have 0 in them. You need to move those...

GSquared (4/28/2008)

---

Having StatusID and Active in your Where clause is getting rid of any rows that would have 0 in them. You need to move those to the Join...

That's the end of the replace statement. You seemed to be trying to "increment" the year in your previous attempts. If...

Hmm...I must be missing something, cause CASE should handle that... That being said - assuming you're starting out with an 8-character string, then:

select replace(left([col032],4)+'-'+substring([col032],5,2)+'-'+substring([col032],7,2)+' 00:00:00.00.000','2006','2007')

would create a CHARACTER...