Identity columns and replication are a dangerous combination.

You should consider add location to the PK

OR

Use sequence tables to handle your Id needs.

Hard to tell with just that. You will need to be able to reproduce the problem.

I have many large installations and even with the largest of the snapshots the...

Although peer-to-peer can potentially work you should avoid multiple writers because conflict resolution can become a problem.

Merge was designed for that but it is very intrusive with the schema. If...

ptaylor (3/24/2009)

---

Thanks...

At this point the updates will be infrequent, but thanks, I will keep that in mind if it scales out.

Might there be a better way to do it than...

glad you got it working.

Quit :hehe::-D

george sibbald (3/24/2009)

---

noeld (3/24/2009)

---

IF and only IF there is only one database you can drop all SQL logins on the destination Server and copy the logins from the Primary using...

IF and only IF there is only one database you can drop all SQL logins on the destination Server and copy the logins from the Primary using sp_help_revlogin. Then there...

No sp_help_revlogin is useful for Transferring logins NOT to remap them! Which is what the PO...

You can make qty NOT NULL and you will have consistent behavior.

ptaylor (3/23/2009)

---

Thanks guys, I found another way around it.

I wanted the replication job to run everytime there was an update or insert on a table in the parent sql...

Create a local SQL Server alias. SQL Server replication tools are ***very*** picky about Server Names.

-Noel

sp_change_users_login

Ahh the PIPE Dreams of English Query ... that's probably why MS throw the towel!

Steve Jones - Editor (3/23/2009)

---

The multiple monitors definitely helps me work faster. I have 3 on the desk, struggle slightly when I'm on the laptop.

itouch controlling a presentation? Post a...