I mean with just normal text.

I could load the following text, "My cat is furry" into two different encoding, and SQL sees them as different.

I FIGURED IT OUT!

The problem wasn't the slashes....the problem was a bulk insert statement requires its path put in quotes.

when I did this (set @var = '\\stuff')....I was providing the...

MSG 102, LEVEL 15, STATE 1, Line 1

Incorrect syntax near '\'.

I should mention I have also tried escape all the slashes with [] and...

dmoldovan (12/4/2009)

---

Don't forget to add the necessary blanks around FROM and WITH:

ET @RUNNER =

'Bulk Insert #Table

FROM ' + @SOURCE +

' WITH (ROWTERMINATOR = '''')'

For the row terminator - see...

Jeff Moden (11/4/2009)

---

With that in mind, there are some "stat" questions we need to ask...

1. How many rows are in the table?

2. How many total rows will be...

Basically we have clients that use the database...and they are very touchy. If any little thing happens our client support team starts getting calls....which is not acceptable to my managers.

So...

Thanks, I've heard a few other recommendations for Itzik so I think I'll take a look.

Michael Valentine Jones (10/30/2009)

---

What did you find when you looked it up in SQL Server...

Thank you for the answers.

Michael, I'm a bit confused on the code below, I'm not familiar with output statements. In particular, I'm not sure what this block of code does:

INSERTED.MyTablePK,

DELETED.FULLNAME,

INSERTED.FULLNAME

Michael...

Jeff Moden (10/28/2009)

---

I'll do all the updates in an extra column that I form while doing a high speed SELECT/INTO. Then, it's a very simple update based...

I tried something new today to see if it would help.

I split my data into two tables, one where the length of the FULLNAME field was less than 450 characters...

jagadeesanpv (10/28/2009)

---

Instaead of using replace function why don't you use where clause

like

Update #temp

set fullname = 'bill'

where fullname = 'billy'

I think if you use this way you can avoid calling...

The problem is your where clause. You are doing an equal statement on two different tables but haven't actually joined them together.

I am guessing the "dbo.tblCUSTOM281009" in your where clause...

Thank you for your help sir!