That shouldn't be a problem, but I'm not sure if your format file is correct.

Here's one example that I use, it might help you out.

<?xml version="1.0"?>

<BCPFORMAT

xmlns="http://schemas.microsoft.com/sqlserver/2004/bulkload/format"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<RECORD>

...

Instead of fighting with this, why don't you do things correctly? You should store each value in its own column.

I'm sure the bug is logged under code PEBKAC. There's an easy fix for that but it might not correct it the first time you apply it.

tjskidmore (12/19/2014)

---

This is of course a limitation with the ISNULL() function. The datatype and in this case str1 is varchar(5) meaning that the replacing statement will be confined to 5...

Yes, it's intended to look simpler as the conditions are reduced by half. Note that I changed the collation, basically because I have a case insensitive collation and because binary...

ichv (12/17/2014)

---

Hi,

I have exactly the same issue, and the found that solution perfect but it still getting error.

My question is: how could I find the row producing error? I...

Noobie in deed 😛

DECLARE @CountResult int, @ID_Wells int = 1

Set @CountResult =(SELECT COUNT(*)

FROM (VALUES(1, 'SomethingH'),

(1,...

Two side notes:

1. A table with one row will return the message that has more than 1 row. :w00t:

2. If you don't care about the number of rows in the...

Your variable is declared as integer and you're assigning a string value. Read about sp_executesql to understand how to use parametrized dynamic queries. Using parametrized queries, you can use an...

The problem is that you aren't assigning length to your strings. There's no need to use varchar since you're always going to have the same length. Here's an example:

DECLARE @RPT_DTA...

It's good to know that you found a solution to your problem.

Remember that there's not a "one-code-to-rule-them-all" and you need to test possible approaches to find out which one is...

Lance,

You continue to mention that this is a bug while it's actually a feature that allows us to write correlated subqueries. It's a feature that can cause bugs, but...

It seems that you edited your reply. I wonder if it was due to security/privacy concerns.

I'm not sure what the issue was as it seems that it should work as...

I hope that this is some kind of weird reporting requirement as it shouldn't be used to store data unrelated in the same row of a table.

WITH SampleData(Main) AS(

...

How do you define that PR-10-01004-2 relates with CC-09-00032-D and not with CC-09-00113-A? Or is that irrelevant? Do you need some kind of order whatsoever?