Help!! Prob with starting merge replication...

Hi there. I want to try set up merge replication from one machine to another, but I dont want to bulk copy the tables as the data already exists in the other database. Ive been testing the scenario out on a basic DB. It has one table and has a uniqueidentifier and another char col. The other database I am replicating to has exactly the same data. The create tasble statement is here:
CREATE TABLE [dbo].[testTable] (
      [rowGUID]  uniqueidentifier ROWGUIDCOL  NOT NULL ,
      [val] [char] (10) COLLATE Latin1_General_CI_AS NOT NULL
) ON [PRIMARY]

When I try to start synchronising I get the following error:
Invalid column name 'rowguidcol'.

Any ideas on this?? On the real database all my tables use Uniqueidentifiers as the primary key just like the table above...
LVL 11
SlimshaneeyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dishan FernandoSoftware Engineer / DBACommented:
is there any col like this >> rowguidcol
SlimshaneeyAuthor Commented:
No, just 2 cols in the table. you can see them both if you look at the create table statement used for both databases

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dishan FernandoSoftware Engineer / DBACommented:
I am under the impression you selected "No, the subscriber already has
the schema and data." If the subscribing articles do have rowguid
columns, you will get this error message.  A solution would be to
initialize the schema and data at the subscriber or generate the
publisher's database script (if you previously had replication
configured) and apply it to the subscriber and then
select "No, the subscriber already has the schema and data. Hope that
helps.
>

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.