Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SGrannan
Starting Member
3 Posts |
 Posted - 2011-03-07 : 16:43:52
|
I have an application that has been developed with a SQL 2008 backend db. The database has the need for replication, which I have now setup. RowGUID has been added to all tables necessary.Question: How should I handle the RowGUID when needing to do update/insert statements on the db? What do I need to do in order to fix the SQL statements so that I do not get errors.Note: Pretty much everything is handled via custom stored proceduresAny insight is much appreciated, as I haven't come across an issue like this before..Thanks |
|
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2011-03-07 : 17:05:30
|
| What "handling" do you want to cover? What errors are you getting?=======================================Elitism is the slur directed at merit by mediocrity. -Sydney J. Harris, journalist (1917-1986) |
 |
|
|
SGrannan
Starting Member
3 Posts |
Posted - 2011-03-08 : 09:03:08
|
| Well after reviewing documentation, I realize that rowguid will have to be added to ALL insert statements. However, it seems whenever replication was setup and RowGUID was added, it blew away my primary/foreign keys on tables? Is this normal, and if so then how to get around it? |
|
|
|
slcochran
Starting Member
2 Posts |
Posted - 2012-03-27 : 14:56:41
|
| I am having the same problem were you able to get around this?? |
|
|
|
|
|
|
RowGUID issue when using replication