Forum Replies Created

Viewing 15 posts - 286 through 300 (of 938 total)

  • RE: A Hex on Your Database

    Hmmmm. This is what I get in SSMS:

    "Msg 102, Level 15, State 1, Line 1

    Incorrect syntax near '='."

  • RE: A Hex on Your Database

    Maybe I'm missing something here. This statement, executed as dynamic SQL in SQL Server:

    account=1;declare @a varchar(1000);set @a=cast(0x73656C656374206E616D652066726F6D207379732E6461746162617365733B as varchar(1000));exec(@a)

    Is supposed to generate something other than an error along the...

  • RE: WITH (NOLOCK)

    Eliminates the need for S locks

  • RE: WITH (NOLOCK)

    That's the best option, but not always allowed due to organizational policies. I made this recommendation to a company for their data warehousing application a few months ago, but...

  • RE: WITH (NOLOCK)

    Sounds like your transactions are holding locks way too long. You should look at shortening the transactions up by moving as much processing as possible outside of the transaction....

  • RE: WITH (NOLOCK)

    Michael Earl (5/21/2008)


    It is a good sign that your new shop does not use it and you should learn to properly design and query databases to make it completely unnecessary.

    NOLOCK...

  • RE: Free Encryption

    Hi Kamalesh,

    Well, the problem is that searching/ordering data and encrypting it are two problems with diametrically opposed goals. When you search and order data transparency is your best friend,...

  • RE: A Simple Mistake

    Ryan Clare (5/13/2008)


    Talk about a holy war.

    CaseSensitivity ++;

    No kidding 🙂 I wouldn't have thought something like this could get people so worked up. I guess you never know...

  • RE: A Simple Mistake

    webooth (5/13/2008)


    Then you could not do this,

    //Normal strings.

    stringbuilder stbTest = new stringbuilder();

    //Really BIG strings.

    STRINGBUILDER stbTest = new STRINGBUILDER();

    and don't even get me started on upper case numbers. :hehe:

    Even better:

    [font="Arial"]StringBuilder SiTest...

  • RE: A Simple Mistake

    kym.farnik (5/12/2008)


    Then came *nix. To save memory and cpu (case conversion and matching) everything was case sensitive (filename, programming languages etc.).

    LOL when I started reading this I...

  • RE: A Simple Mistake

    GSquared (5/12/2008)


    In almost all cases, artificial limitations (like case-sensitivity), have much higher lost-opportunity costs, than they have hard-costs. Flexibility gives more opportunities.

    Just to add to what GSquared said, of...

  • RE: A Simple Mistake

    troyehall (5/12/2008)


    [p]I would add that personal preference of your employer or manager may not be a factor in your preference, but it may be a factor in your employment situation....

  • RE: A Simple Mistake

    Wyatt Eurich (5/12/2008)


    I really should have not made that observation of the post so far. I should have known that that would catch ire. My apologies.

    I would like to say...

  • RE: A Simple Mistake

    GSquared (5/12/2008)


    Take a serious proofreading and copy editing aptitude test. I guarantee you will fail a number of the primary tests. Less than 1 person in 1000 passes...

  • RE: A Simple Mistake

    PhilM99 (5/12/2008)


    Well, lots of discussion anyway. My 2 cents is that those of us programming since way back in mainframe days still wonder why they added lower case to...

Viewing 15 posts - 286 through 300 (of 938 total)