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 |
|
joanne
Starting Member
46 Posts |
 Posted - 2005-10-12 : 14:21:55
|
| Hi,I have an application that use a stupid replication with source and target database on the same server.Now I want to test my restore plan and I want to use a dev server.Every time when I want to install replication a red x sign appear on the Replication Monitor.I don’t have this problem on the prod server. Somebody can tell me where the mistake is.The only one difference that I see is that I use win 2000 professional on the dev server and win 2003 on the prod server.Many thanks! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-10-12 : 14:28:18
|
| When a red x appears on the Replication Monitor, you will find a failed job assosciated with it. Check out that failed job to determine what the problem is.Tara |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-10-12 : 22:09:38
|
just to wanted to say that some problems are resolved by this approach, especially if you need to 1. protect databases from each other2. maintain "system" tables easierquote:
Originally posted by joanne
a stupid replication with source and target database on the same server.
 --------------------keeping it simple... |
|
|
|
|
|
|
a red x on the Replication Monitor.