You may have set up the linked server properly but did you set it up with a login using sp_addlinkedsrvlogin ?

That's required unless you allow anonymous logins and that should...

>Jeff, can you give an example where 'a-f' are considered by ISNUMERIC to be convertable to a number?

Sure Frank,

There's others but these will do... only one out of a-f that...

>Why can not select cast ( '123'+char(160) as int) work ?

Probably for the same reason that select cast ( '123'+char(12) as int) won't work.  The extra special characters just aren't convertable to...

Outstanding, Ziga!  Thank you for the feedback!

Shrikant,

This will do it provided your tables correctly have a primary key (composite 2 column PK in this case)... first, the usual disclaimer because this is a data altering script...

Shrikant,

Yes, but I need a little more info...

1. Do the tables have a Primary Key?

2. How many rows does the biggest table have?

3. Are you allowed to use temporary tables?

Ziga,

To do a nearly perfect distribution of random numbers across 3 sets, use the following to overcome the up-rounding that is inherenent in an INT column (you could use TinyInt...

Easy enough...

First, let's take care of adding the ID column, filling it with numbers from 1 to n, and making it the Primary Key... we're going to do it without...

Ziga,

The reason for the error is you have not FETCHed anything. 

Shifting gears... I know you think you need a cursor for this, but you do not.  I will admit...

Ok, just for fun, the following code will report ranges of both present and missing ID's.  Why do it this way?  Because if you have a huge number of missing...

Interesting...  THAT allows you to use sp_ExecuteSQL with more than 4k bytes?  I gotta try that.

No need to be sorry... most of us have made the same mistake early in our SQL careers.  Those that say they didn't... are lying.

Sure, one complete explanation coming right up...  but I'm a bit surprised you didn't figure it out yourself... remember, you asked the question...

First, I modified your code so we could...

Don't use sp_Execute.  Just use EXEC...

EXEC (@SQL1+@SQL2+@SQL3....+@SQLn)

... and each of the variables can be VARCHAR(8000).

dba321,

The Inserts that Phil provided are just test code to simulate your much larger table (or result set, whatever)!  You don't need any of those Inserts and you certainly don't...