Viewing 15 posts - 1 through 15 (of 52 total)
No business impact at all - ran this through the middle of the business day with no lock issues. Give it a try and let me know.
August 17, 2015 at 10:42 am
At the time the IT budget was non existent. It happens and DBAs need tools to shrink database in times like that. The tone was meant to be...
August 17, 2015 at 10:40 am
Thanks for the comments.
In this case the data was ancient unread so removing the rows was needed. There was a significant performance improvement by removing the rows. Alas...
August 17, 2015 at 10:35 am
In the process of analyzing the data I focused on inserts/deletes as that is how our system are designed, in the actual migration on the critical high volume DBs I...
September 23, 2013 at 6:39 pm
Hi Andy:
Yes - ours is a high insert OLTP environment, percentage of updates on our systems is low so for this migration it didn't matter. But tracking updates is...
September 23, 2013 at 11:04 am
Thanks for the comment.
I've had inconsistent result with -skiperrors, altering the stored procedures always works. This approach is at the table level so it limits the impact to just...
June 1, 2013 at 12:33 pm
Yes the synch would apply on failed updates and inserts. I'll check out your web site. Thanks,
May 30, 2013 at 12:00 pm
Thanks for the comments. In my shop it's usually 1 article that has issues due to rows being changed on the subscriber, and that's another article, so I use...
May 30, 2013 at 10:33 am
I use the filter in Redgate to limit the number of rows - this runs quick enough on large table:-). Make sure to pick the primary key for best...
May 30, 2013 at 10:26 am
Thanks for all the comments. I add that my shop doesn't ever go offline - we are truly 7*24*365. The article discusses one technique to remove obsolete rows...
March 18, 2013 at 12:07 pm
I see the issue here, yes the left over rows aren't deleted on purpose. My goal is to remove 50 million rows using 2000 row chunks so yes there...
March 7, 2013 at 4:39 pm
Well your view was not defined as discussed in the article, for more fun try these statements and the data is returned in order - always.
CREATE TABLE t1 (x INT...
March 7, 2013 at 12:33 pm
BTW - Ceiling works here because these are integer variables.
Thanks,
March 7, 2013 at 12:24 pm
Try this.
CREATE VIEW dbo.test as (SELECT top (100) * from table ORDER BY primary_key_column). Look at the result they will be ordered.
March 6, 2013 at 6:00 pm
Viewing 15 posts - 1 through 15 (of 52 total)