Timeline for Validate data between two large tables
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 9:05 | history | edited | CommunityBot |
Commonmark migration
|
|
| Aug 14, 2018 at 15:13 | comment | added | Sting | Even if replication was the best candidate for this, its never been my favorite. What I'm recommending is a big deal. I'd definitely test it first by spinning up a few temporary VMs for a few months to see what works and what doesn't. RSCI helps a lot when blocking is a concern: social.msdn.microsoft.com/Forums/windows/en-US/…. | |
| Aug 14, 2018 at 15:02 | comment | added | BradC | @JohnG Replication definitely made improvements between SQL 2000 and 2008, but a massive many-to-one merge replication setup on a mission-critical system is far from trivial, I'm not sure that I'd risk this big of a change myself. And if some of the data comes in exported flat files (instead of direct access to the remote servers), I'm not sure this is even a candidate. | |
| Aug 14, 2018 at 14:44 | comment | added | JohnG | my experience with replication, back in the days, weren't pleasant... Everything was locking up... Is it still the case or has there been improvements since SQL2000... Don't forget, this is an OLTP DB, so I can't afford any massive locks (If I'm not mistaken, after 500+ row locks the engine locks the table). | |
| Aug 14, 2018 at 14:42 | history | edited | Andriy M | CC BY-SA 4.0 |
improved formatting; removed noise
|
| Aug 14, 2018 at 14:32 | history | answered | Sting | CC BY-SA 4.0 |