The application I support uses SQL Server 2005 as the publisher and SQL Server 2000 at the subscriber. One of our clients went nuts trying to prune his database and deleted a year and a half of sales data. Unfortunately I did not have a backup, but I did have an old copy of the db. I manually imported the data at the subscriber end (which I've done before with no issue) as his database was pushing 20 gigs and publisher server space at the time was a premium. Long story short when it replicated it locked up all that data in 40k worth of conflicts with the subscriber as the loser. To avoid a costly and time consuming data import at the publisher, I want to use one of the customer resolvers, namely the SQL Server Subscriber always wins. I only need to do it on 2 articles. Can someone give my brief instructions as well as any pitfalls before I take the plunge? My concerns are will I have to reinitialize the subscriber or redo my publication (reinit would be painful and due to the number of locations in the clients WAN, recreating the publisher is not an option).
Software/Hardware used: SalonTouch, Windows XP, SQL Server 2000 (sp4) and 2005 (sp3), 64 bit Server 2003 R2 SP2
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!