Of course, if it is necessary to make the JOIN work correctly.

Two cups of coffee and feeling philosopical...

When I was a boy, and computers were carved from wood and cranked by hand, it was widely understood that hierarchical databases outperformed relational...

INSERT INTO [DestinationDatabase].[dbo].[prempl]

.

.

.

SELECT

-- Employee_Master.Empno,

CONVERT(int,Employee_Master.Empno),

Employee_Master.Surname,

Employee_Master.GivenName,

.

.

.

FROM SQLSERVER.SourceDatabase.dbo.Employee_Master Employee_Master

.

...

You're welcome, Test. Just make that code a user-defined function and the complexity goes away.

Better yet, make it...

"EAV" stands for Entity-Attribute-Value table, also derogatorily referred to as a "MUCK". (Massively Unified Code-Key table) While some people gravitate towards them because of their flexible...

Thanks for the save, Allister. 🙂

At one point that occurred to me, because the usual concatenation routine pads the string on the left and right with separator characters....

To reduce logging and gain speed, you are probably going to wind up setting your db to simple recovery mode and then updating the tables in batches, rather than all...

Thanks for coming back and posting your working code, Damien. It's a nice thing to do.

If you want performance, don't use a MUCK/EAV for one thing. 😉

Seriously, this type of table does not scale well and you will find yourself jumping...

"Easy" is a relative term. The following code is short, and should produce the same results, but I haven't tested for performance. Also, it's not nearly as...

I would have to see both query plans to give a definite answer, but this is my supposition.

By JOINING the tables you are adding the overhead of...

You can JOIN tables based on more than one column. It will work, even in the absence of compound keys or other indexes. Indexes may make...

Sigh... I always over-design things.

This is what you are inserting.

SELECT

Employee_Master.Empno,

You aren't converting the data in your SELECT, just in your JOIN. You need to convert it here for...

That'll work!!! I would have done it with a CROSS-APPLY like this, but for re-use an inline table valued function would be sweet. If...