THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |

Search

You searched for the word(s):
Showing page 1 of 2 (13 total posts) < 1 second(s)
  • re: Five things SSIS should drop

    I agree the SCD wizard sucks, but it should be completely rewritten from scratch. &nbsp;Most SSIS folks I know run straight to a high-performance component like TableDifference to manage SCDs or use a staging table strategy with MERGE to avoid the pain of the SCD wizard.
    Posted to Jamie Thomson (Weblog) by Mike C on May 11, 2010
  • re: Debunking Kimball Effective Dates

    No problem. &nbsp;The thing people miss is that even in a denormalized DM, speed is a *secondary* consideration. &nbsp;It's easy to get fast results if you don't care how wrong they are. &nbsp;In every DM (at least the ones I've built) correct results are the *primary* consideration.
    Posted to Jamie Thomson (Weblog) by Mike C on February 21, 2010
  • re: Debunking Kimball Effective Dates

    @JaggedEdge - Don't be skurred. If GROUP BY skurrs you, then try a CTE with a windowing function (ROW_NUMBER) instead. Not sure why you'd find GROUP BY skurry. &nbsp;If something were to keep me up at night it would be the possibility of incorrect results, not set-based SQL syntax.
    Posted to Jamie Thomson (Weblog) by Mike C on February 21, 2010
  • re: Debunking Kimball Effective Dates

    Using Jamie's method of storing just a start date you can *accurately* infer the end dates. &nbsp;As has been pointed out already here, accurately enforcing end dates when you store the start and end dates is a lot tougher. &nbsp;Even if you want to store the start and end dates in the Kimball-style datamart, you would do well to store just the ...
    Posted to Jamie Thomson (Weblog) by Mike C on February 21, 2010
  • re: Decrypting : A question of morals, ethics, or both?

    This is a little OT, but I've been wondering why MS didn't include better encryption for database objects. &nbsp;SQL 2005 and 2008 have much better encryption capabilities than 2000 did. Simple insecure obfuscation seems to be a backwards-compatibility throwback, and a pretty useless one at that. &nbsp;With SQL 2008 and EKM you could theoretically ...
    Posted to Aaron Bertrand (Weblog) by Mike C on January 27, 2010
  • re: Follow Me

    Hallelujah! &nbsp; &quot;L'audace! &nbsp;L'audace! &nbsp;Tujours l'audace!&quot; -- Gen Patton
    Posted to Andy Leonard (Weblog) by Mike C on January 18, 2010
  • re: Windows 7 GodMode

    Here's a list of Canonical names for control panel items in Win 7 from MSDN. &nbsp;Same trick should work with them: http://msdn.microsoft.com/en-us/library/ee330741(VS.85).aspx
    Posted to Greg Low (The Bit Bucket: IDisposable) (Weblog) by Mike C on January 8, 2010
  • re: What is so bad about EAV, anyway?

    Hey Aaron, Prior to 2008 I had to do implement similar functionality to XML columnsets, but on 2005. &nbsp;We basically implemented an XML data type column to store dynamic user-defined attribute info. &nbsp;Very simple to implement, although we spent a lot of time designing and testing indexing strategies which turned out to be our biggest ...
    Posted to Aaron Bertrand (Weblog) by Mike C on November 19, 2009
  • re: Would you like to be able to do minimally logged deletes?

    As you mentioned we already have minimally logged table truncation (TRUNCATE TABLE statement). &nbsp;Taking some limitations into consideration I don't see why we shouldn't be able to get similar minimally logged functionality out of DELETE statements in some circumstances, and personally I don't see how it would cause problems if we did have that ...
    Posted to John Paul Cook (Weblog) by Mike C on July 18, 2009
  • re: Why Do I Keep Seeing This Mistake?

    I really enjoy seeing variable declarations inside the loop, since BEGIN...END doesn't change the scope for variables: BEGIN &nbsp;DECLARE @message VARCHAR(25); &nbsp;SET @message = REPLICATE( '-', 25 ) END SET @message = 'abcdefg'; The declarations don't really affect performance much, but the code is just plain confusing to anyone coming ...
    Posted to Kevin Kline (Weblog) by Mike C on July 10, 2009
1 2 Next >
Privacy Statement