http://www.sqlmag.com/authors/author/author/5059106/rsscomment/5059106en-USFri, 25 May 2012 10:38:08 GMTFri, 25 May 2012 10:38:08 GMThttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorWed, 28 Jul 2010 01:22:36 GMT
Hi Royce,

At the time I wrote this article, or even up until now, I have not explored too much into SQL Server Powershell. To be frank with you, I am too busy at work with new enhancements that we need to constantly provide to our business customers.

However we use Informatica as workflow to process our customer every week. I have instructed the system engineering team to call this proc few places in the middle of the workflow also at the end of workflow after making enormours amout of changes to our customer database. This proc does a fine job of updating statistics only on those tables that have been modified every time it is invoked, thus saves us enormous amount of time.

I am sure someone out there who is a talented in Powershell could incorporate what my proc does in his/her work.

Thanks,
Saravanan Radhakrishnan
]]>RADHAKRISHNANWed, 28 Jul 2010 01:22:36 GMThttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorhttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorThu, 10 Jun 2010 18:40:40 GMT
I really like what this does. is there a powershell script that does all this?]]>RoyceThu, 10 Jun 2010 18:40:40 GMThttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorhttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorMon, 07 Jun 2010 16:26:49 GMT
To Brendan
In this case sp_ is fine ’couse proc’s in master database

John]]>GVOZDEVMon, 07 Jun 2010 16:26:49 GMThttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorhttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorThu, 01 Apr 2010 01:49:39 GMT
Why are you using sp_ as a naming convention for stored proc’s when it is best practice not to. And Grant Fitchly( aka Scary DBA ) in his book ’SQL 2008 Performance tuning distilled’ shows the negative impact it does have. The funny thing is its not only you, I have noticed this amoungst other authors...

Thanks
Brendan]]>CallaghanThu, 01 Apr 2010 01:49:39 GMThttp://www.sqlmag.com/article/store-procedures/update-the-statistics-on-recently-modified-tables-only#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-statement-tracks-transaction-less-dates#commentsAnchorWed, 09 Dec 2009 06:03:40 GMT
I think the real shortcoming here is that the solution given should have been written better. Either as this: Select distinct m1.Store_ID, m2.TransactionDate from MySalesTable m1 cross join MySalesTable m2 where m2.TransactionDate not in (Select m3.TransactionDate from MySalesTable m3 where m3.Store_ID=m1.Store_ID) or even more optimally as this: Select distinct m1.Store_ID, m2.TransactionDate from MySalesTable m1 cross join MySalesTable m2 where not exists (Select 1 from MySalesTable m3 where m3.Store_ID=m1.Store_ID and m3.TransactionDate=m2.TransactionDate)]]>BarryWed, 09 Dec 2009 06:03:40 GMThttp://www.sqlmag.com/article/tsql3/t-sql-statement-tracks-transaction-less-dates#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-statement-tracks-transaction-less-dates#commentsAnchorMon, 09 Nov 2009 13:23:56 GMT
If we use the new function "EXCEPT" provided by SQL Server 2005, the script will be much simple and efficient. I post the new script. select distinct I1.Store_ID , I2.TransactionDate from MySalesTable i1 left outer join MySalesTable i2 on I1.TransactionDate <> I2.TransactionDate except (Select Store_ID,TransactionDate from MySalesTable) Eric Jiang ericjiang.yang@gmail.com]]>EricMon, 09 Nov 2009 13:23:56 GMThttp://www.sqlmag.com/article/tsql3/t-sql-statement-tracks-transaction-less-dates#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-statement-tracks-transaction-less-dates#commentsAnchorThu, 05 Nov 2009 10:45:01 GMT
So Saravanan, did you get fired after a "senior-senior production DBA" reviewed your code?!? I hate to see what a NON-senior production DBA would have done!]]>RICKThu, 05 Nov 2009 10:45:01 GMThttp://www.sqlmag.com/article/tsql3/t-sql-statement-tracks-transaction-less-dates#commentsAnchor