http://dbbulletin.wordpress.com All matters database tacked up here. Fri, 15 May 2009 13:21:42 +0000 http://wordpress.com/ hourly 1 http://dbbulletin.wordpress.com/2008/11/14/ssis-cheatsheet/#comment-19 dbbulletin Fri, 15 May 2009 13:21:42 +0000 http://dbbulletin.wordpress.com/?p=63#comment-19 Hi Stephen - I'm glad it was of use! Hi Stephen – I’m glad it was of use!

]]> http://dbbulletin.wordpress.com/2008/11/14/ssis-cheatsheet/#comment-18 stephen chatman Thu, 14 May 2009 21:59:58 +0000 http://dbbulletin.wordpress.com/?p=63#comment-18 Thanks! This worked perfect! At the end instead of using Encrypt Sensitive data with key I used encrypt with password. then when I created a sql job in management studio for the first run I was asked to enter the password. Thanks! This worked perfect! At the end instead of using Encrypt Sensitive data with key I used encrypt with password. then when I created a sql job in management studio for the first run I was asked to enter the password.

]]> http://dbbulletin.wordpress.com/2008/06/27/assm-a-shark-in-the-water/#comment-2 Database Management » Blog Archive » ASSM: A shark in the water? Fri, 27 Jun 2008 14:06:27 +0000 http://dbbulletin.wordpress.com/?p=16#comment-2 [...] Technorati Search for: databases wrote an interesting post today onHere’s a quick excerpt My team came across the following earlier this month. There’s a shark in the water, waiting to byte users running 9.2.0.8 through 10.2.0.3. One evening, a table with 10 million rows got several thousand rows updated and inserted via a nightly batch job. But the table grew from 500 MB to over 4 GB! Well, how could that be…The tablespace where the table resides had recently been re-organized so that settings were now locally managed, uniform extent sizes and automatic segment space management [...] [...] Technorati Search for: databases wrote an interesting post today onHere’s a quick excerpt My team came across the following earlier this month. There’s a shark in the water, waiting to byte users running 9.2.0.8 through 10.2.0.3. One evening, a table with 10 million rows got several thousand rows updated and inserted via a nightly batch job. But the table grew from 500 MB to over 4 GB! Well, how could that be…The tablespace where the table resides had recently been re-organized so that settings were now locally managed, uniform extent sizes and automatic segment space management [...]

]]>