Yes, SSIS or BCP can both work with semi-structured data.

From the information you've given, you must have more than one row that meets the criteria defined. It's the only way you would get the problem.

The question intrigued me, so I played with until I got the right answer. I've no doubt (at all) that there are more efficient ways to work this, but this...

Take a look at the Books Online for the topic OUTPUT clause. That's exactly what you need. It can work with a single row insert, or with batches, and captures...

A "self Join" is when a single table is joined back to itself. You have two tables.

Can you better define what it is you're trying to do?

You can only run it once for a particular set of values, yeah.

Here, an example:

CREATE TABLE dbo.x

(ColNo1 INT NOT NULL,

ColNo2 INT NOT NULL,

Val VARCHAR(50) NULL)

ALTER TABLE dbo.x ADD CONSTRAINT...

It's not the each one is a primary key. You're looking at the GUI and seeing a key next to each column. That means they're part of a compound primary...

Lynn Pettis (11/24/2008)

---

The issue would be support by the vendor, going to SQL Server 2008 before they say their app will work properly with that version, you could lose support....

Absolutely not a cursor.

If you're getting the error that you're violating the primary key, it's simply because you are, in fact, violating the primary key.

The purpose of the primary key...

Another vote for the Inside series of books. Fantastic stuff in there. Other than that, no other books come to mind as absolute must reads. You start to get into,...

Sure sounds like a possible case for transactional replication.

Yes.

If you want records that only meet the criteria defined AND records that don't, it seems a bit odd. What you're saying then is return everything.

The two limiting factors, the...

Actually, it looks like you've changed the structure of the query unnecessarily.

...from (Premium_Access

inner join Premium

on Premium_Access.rollup =...

Please don't cross-post. There are now two different discussions going on about the same topic. Please continue discussion at the other location:

http://www.sqlservercentral.com/Forums/Topic607252-1291-1.aspx?Update=1

This is a cross-post with this http://www.sqlservercentral.com/Forums/Topic607251-149-1.aspx

I'd suggest keeping discussion here.