Nice job, Wayne, and I hope you get better soon.

The log shipping from your DR server (now your PRIMARY) is not automatic. The primary is the server that is sending logs to the other server. If you failover, that...

Everyone's welcome. Bring your $30 to the door.

It will be from 8-10pm, Monday November 2, 2009. Room 615-617

You won't see it in Profiler like that. You'd only see

sp_test 1, 4

for a stored procedure call in Profiler.

The issue is that you are calling your current server, the one you failed over to, the secondary. Once you failover, it's the primary. all log shipping starts from that...

Snow day is worse here. The kids are home, need to work around them. I've been trying to edit articles around a game of Life, one of Chess, and I've...

I'd lean towards replication myself.

If you log ship, you need a separate database on your central server for each database in your environment. Then you need another database that you...

I'm not sure about the issue, but for the service account. Use a domain user, normal user. They do not need to be a domain admin, or a local admin....

So it almost appears this is an assignment of some sort. We don't do homework for you. If you have a specific question, or you are wondering if there is...

I think Gail is like me, running from thing to thing, not sure how all the plates are staying in the air.

At least I have kids to balance things out...

I assume you can join the two tables and rows together.

The issue gets into permissions between databases. The user in DB 2 must have rights, or ownership chaining enabled, in...

Try this: http://www.sqlservercentral.com/scripts/Permissions/64309/

If it's a temp proc, it was created on your system. We have no way of knowing what it is.

You could try scripting it to see the code.

You can have both replication partners update data in merge or in bidrectional transactional replication. You need to really think through what to do if there are issues with conflicts...

Egg timer......:-P