Forum Replies Created

Viewing 15 posts - 5,671 through 5,685 (of 6,031 total)

  • RE: NoSQL is Not the Answer

    CirquedeSQLeil (3/17/2011)


    I think a huge it depends is in order for NoSQL v RDBMS. One thing to consider is if the data consistency or data recoverability in your application...

  • RE: Implicit and Explicit Conversions

    Ron Porter (3/17/2011)


    Mike B in AK (3/17/2011)


    Interestingly, I inherited a process where the previous person stored integer values in a varchar(3) field and did poor quality checks on the data...

  • RE: Implicit and Explicit Conversions

    richardd (3/17/2011)


    Nakul Vachhrajani (3/16/2011)


    I have seen people using VARCHAR for storing everything (dates, money, floats)! Their excuse? Globalization/Internationalization.

    How can anyone claim that storing a date as the string "09/01/2001" is...

  • RE: Implicit and Explicit Conversions

    The representation of dates as character strings in a database (what I'll call a "VarDate") is one of the leading causes of business intelligence disasters.

    The day will come when another...

  • RE: How to Connect to a SQL 2005 Server When You Are Completely Locked Out

    There are many different scenarios, but if what you need is access to the database itself, then you can always attach a copy of the mdf file(s) to a SQL...

  • RE: NoSQL is Not the Answer

    Just because a database platform is good enough for Facebook or Google, that doesn't mean it's good enough for online banking or e-commerce. I believe that financial and operational data,...

  • RE: Avoiding Logging

    So after the staging server has finsihed updating it's copy of the database, you do what with the synonymns on the production server? Point your queries to a different database?

  • RE: Avoiding Logging

    Generally speaking, transaction logging is trivial during the normal day to day operations of a OLTP database, especially if the log files are on separate storage from data files.

    If...

  • RE: Avoiding Logging

    [Jim].[dba].[Murphy] (3/10/2011)


    mmmm. Not sure about that. A log truncation could have bad side effects if any part of that database is used by others; rows being modified in...

  • RE: Avoiding Logging

    Carl B. (3/9/2011)


    It could be helpfull to avoid logging in scenario where you want to "UPGRADE" the data in a BD with numerous conversions script:

    1- You take a full backup...

  • RE: Quality Over Timing

    Steve Jones - SSC Editor (3/9/2011)


    Mark W Johnson (3/9/2011)


    I don't see my job as writing code so much as solving the user's problem through code; my job is to help...

  • RE: Quality Over Timing

    This piece is a few years old, and it talks about how quality has become more important at many large software vendors. Looking back across the five years since the...

  • RE: Avoiding Logging

    Those of us who were developing applications in FoxPro, MS Access, or some other ISAM platform back in the 80's and early 90's know the perils of a transactionally inconsistent...

  • RE: Avoiding Logging

    Transaction logging usually isn't an issue unless you're inserting 100,000+ records one.. at.. a.. time.. in a loop, or the DBA allows the transaction log to grow until it fills...

  • RE: Slow Fixes

    Of course wether or not a security flaw or bug makes public headlines determines how it is triaged, however it doesn't mean that Microsoft is just sitting on it.

Viewing 15 posts - 5,671 through 5,685 (of 6,031 total)