This could also be from lack of instant file initialization. http://mattslocumsql.blogspot.com/2014/02/why-are-my-database-restores-so-slow.html

casinc815,

The links are at the beginning. They are: Article 1[/url] and Article 2[/url].

-Mark

Very well written article with great practical examples of the downstream effect of "lazy" design decisions.

RonKyle: That's a very good point...this technique is perhaps most appropriate for an accumulating snapshot table, where by definition each record is changing with time. The boiled-down example I've...

Coalesce is needed because you don't know in advance if the value will be on the source side, the destination side, or both. If you only refer to one...

GPatterson -- that's a very good point. I've run into that exact problem before. I was going to address that in part 2....but as a preview let...

I'm just using the NEWID() function as a way to create unique random numbers for each row. When you use RAND() in a query like this, it generates the...

ShannonJk,

Thanks for the positive feedback, much appreciated!

I was just reviewing the EXCEPT query syntax at the top as it's the classic way to test for dataset deviations. I needed...

It's not so bad to maintain. You just have to extend the WHERE clause:

WHERE ABS(RandomNumberDiff) > @Tolerance

to the following:

WHERE (

ABS(RandomNumberDiff) > @Tolerance

OR ABS(RandomNumberDiff2) > @Tolerance

OR ABS(RandomNumberDiff3) >...