[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 326
  • Last Modified:

MS ACCESS, MS SQL and Merge replication.

Hi There,

we are using MS Access database. I am in testing phase of migrating access data to sql server and replicating using merge replication with client installing MSDE and using access, adp file for the front end.

When i migrated table from ms access to ms sql four new coloums has been created and when i published database for replication on additional coloum has been created (which is rowguid, which is necessary), but i donot understand all the four coloum that has been created is really important (wheather always work like this when migrating ) or we can delete it.

Like i have a table called account with two field
- assetCategoryID
-assetCategoryDescription

When i migrate to sql server table become like this

- assetCategoryID
-assetCategoryDescription
-s_colLinege , type image
-s_Generation , type int
-s_guid , uniqueidentifier
-s_lineage,type image
- rowguid, uniqueidentifier
and tstamp row was also created

we were also using replication in MS Access database.

I am looking for information about these four extra coloum created. wheather its always like this when we migrate or there is some thing wronge with my migration. Can i delete those coloum or not.

If you can give me some information that will be grate.

Thanks.

Indra.
0
Indra77
Asked:
Indra77
  • 2
1 Solution
 
arbertCommented:
Those are the replication columns that were on the access database but hidden--they also got moved to SQL Server when you upsized.....
0
 
Indra77Author Commented:
As after upsizing I am going to use sql database for replication as well, so can i delete those column or i have to keep them in our database.

Thanks.
0
 
arbertCommented:
You can delete them since they were the previous Access replication columns....

Brett
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now