Are the posted questions getting worse?

  • Trey Staker (3/25/2010)


    I've got a 3rd party companies support that uses sql server as their DB for their database that is insisting I add this command to my full backups, sql server 2005. compat 90 on all the databses.

    DUMP TRANSACTION <DATBASENAME> WITH TRUNCATE_ONLY

    They are driving me nuts! Anyone have some links handy to help me with the battle I'm about to fight with their engineers and dba once I get past level one support?

    I have to do it or I loose support from them on their applications.

    I added this disclaimer in the job's description:

    ** Disclaimer from the DBA -- This does nothing to a database in FULL

    or BULKLOGGED in SQL Server 2005 or greater. This is also in the

    process of being depricated by Microsoft because it is a known bad

    practice and has been fully depricated in SQL Server 2008.

    :crying:

    I feel bad for you. I wish I had some links, but I'd start by providing links to the MS documentation you are quoting in your disclaimer and then give them links to BOL on recovery models and why you'd use the various recovery models. Really they want SIMPLE recovery model.

  • Jack Corbett (3/25/2010)


    Trey Staker (3/25/2010)


    I've got a 3rd party companies support that uses sql server as their DB for their database that is insisting I add this command to my full backups, sql server 2005. compat 90 on all the databses.

    DUMP TRANSACTION <DATBASENAME> WITH TRUNCATE_ONLY

    They are driving me nuts! Anyone have some links handy to help me with the battle I'm about to fight with their engineers and dba once I get past level one support?

    I have to do it or I loose support from them on their applications.

    I added this disclaimer in the job's description:

    ** Disclaimer from the DBA -- This does nothing to a database in FULL

    or BULKLOGGED in SQL Server 2005 or greater. This is also in the

    process of being depricated by Microsoft because it is a known bad

    practice and has been fully depricated in SQL Server 2008.

    :crying:

    I feel bad for you. I wish I had some links, but I'd start by providing links to the MS documentation you are quoting in your disclaimer and then give them links to BOL on recovery models and why you'd use the various recovery models. Really they want SIMPLE recovery model.

    If they want you to do this, really are you losing any value in their support?

    I would do as Jack recommends. Provide them the links to the deprecation statements.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Jack Corbett (3/25/2010)


    Trey Staker (3/25/2010)


    I've got a 3rd party companies support that uses sql server as their DB for their database that is insisting I add this command to my full backups, sql server 2005. compat 90 on all the databses.

    DUMP TRANSACTION <DATBASENAME> WITH TRUNCATE_ONLY

    They are driving me nuts! Anyone have some links handy to help me with the battle I'm about to fight with their engineers and dba once I get past level one support?

    I have to do it or I loose support from them on their applications.

    I added this disclaimer in the job's description:

    ** Disclaimer from the DBA -- This does nothing to a database in FULL

    or BULKLOGGED in SQL Server 2005 or greater. This is also in the

    process of being depricated by Microsoft because it is a known bad

    practice and has been fully depricated in SQL Server 2008.

    :crying:

    I feel bad for you. I wish I had some links, but I'd start by providing links to the MS documentation you are quoting in your disclaimer and then give them links to BOL on recovery models and why you'd use the various recovery models. Really they want SIMPLE recovery model.

    This is one of those things where they've been doing that way since sql server 6.5 and have their own predjudices.

    They want SIMPLE but they send their databases out the door in FULL or BULK LOGGED. My company assumed, before I came aboard, that they could do point in time recoveries. I set up hourly log backups. Before that the log files were filling up because that does nothing in 2005+.

    ---------------------------------------------------------------------
    Use Full Links:
    KB Article from Microsoft on how to ask a question on a Forum

  • Trey Staker (3/25/2010)


    Jack Corbett (3/25/2010)


    Trey Staker (3/25/2010)


    I've got a 3rd party companies support that uses sql server as their DB for their database that is insisting I add this command to my full backups, sql server 2005. compat 90 on all the databses.

    DUMP TRANSACTION <DATBASENAME> WITH TRUNCATE_ONLY

    They are driving me nuts! Anyone have some links handy to help me with the battle I'm about to fight with their engineers and dba once I get past level one support?

    I have to do it or I loose support from them on their applications.

    I added this disclaimer in the job's description:

    ** Disclaimer from the DBA -- This does nothing to a database in FULL

    or BULKLOGGED in SQL Server 2005 or greater. This is also in the

    process of being depricated by Microsoft because it is a known bad

    practice and has been fully depricated in SQL Server 2008.

    :crying:

    I feel bad for you. I wish I had some links, but I'd start by providing links to the MS documentation you are quoting in your disclaimer and then give them links to BOL on recovery models and why you'd use the various recovery models. Really they want SIMPLE recovery model.

    This is one of those things where they've been doing that way since sql server 6.5 and have their own predjudices.

    They want SIMPLE but they send their databases out the door in FULL or BULK LOGGED. My company assumed, before I came aboard, that they could do point in time recoveries. I set up hourly log backups. Before that the log files were filling up because that does nothing in 2005+.

    EDIT: I did pose this as a question outside the "Thread" after I posted it here because this probably isn't the proper place. I appologize for the double posting, That's one of my pet peeves and here I go breaking it.

    ---------------------------------------------------------------------
    Use Full Links:
    KB Article from Microsoft on how to ask a question on a Forum

  • Trey Staker (3/25/2010)


    EDIT: I did pose this as a question outside the "Thread" after I posted it here because this probably isn't the proper place. I appologize for the double posting, That's one of my pet peeves and here I go breaking it.

    Well, in your favor, you tried to remove it but Jack quoted you too quickly.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Trey Staker (3/25/2010)


    EDIT:

    I removed it and I'm going to post it outside this thread...

    This is a fun thread...

    Where's the link?

  • Anyone have anything light or funny to move this thread back into the right direction?:-D

    ---------------------------------------------------------------------
    Use Full Links:
    KB Article from Microsoft on how to ask a question on a Forum

  • Jack Corbett (3/25/2010)


    Trey Staker (3/25/2010)


    EDIT:

    I removed it and I'm going to post it outside this thread...

    This is a fun thread...

    Where's the link?

    ---------------------------------------------------------------------
    Use Full Links:
    KB Article from Microsoft on how to ask a question on a Forum

  • Trey Staker (3/25/2010)


    They want SIMPLE but they send their databases out the door in FULL or BULK LOGGED. My company assumed, before I came aboard, that they could do point in time recoveries. I set up hourly log backups. Before that the log files were filling up because that does nothing in 2005+.

    Someone must have taken a full backup at some stage, otherwise the databases would still be in log-auto-truncate mode...?

  • Trey Staker (3/25/2010)


    Anyone have anything light or funny to move this thread back into the right direction?:-D

    What is your favorite color?

    Blue. No yel-- auuuuuuuugh!

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Trey, it's possible they are relying on DBCC TIMEWARP to provide point-in-time recovery.

    What is your ARID??

    __________________________________________________

    Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
    Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills

  • The Dixie Flatline (3/25/2010)


    Trey, it's possible they are relying on DBCC TIMEWARP to provide point-in-time recovery.

    What is your ARID??

    umm... Extra Dry?

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • ARID = Alternate Reality ID.

    I believe it's parameter 117, but I'd have to confirm that with Gail.

    __________________________________________________

    Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
    Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills

  • The Dixie Flatline (3/25/2010)


    ARID = Alternate Reality ID.

    I believe it's parameter 117, but I'd have to confirm that with Gail.

    And that's a GUID right?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • The Dixie Flatline (3/25/2010)


    ARID = Alternate Reality ID.

    I believe it's parameter 117, but I'd have to confirm that with Gail.

    From what I recall, it's 117 if in a closed universe, 118 if in an open universe, and both if the universe is in a steady-state.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 15 posts - 13,306 through 13,320 (of 66,712 total)

You must be logged in to reply to this topic. Login to reply