QOD 10-30

  • The question was incorrect -

    "Using the Dynamic Properties Task, what COULD you set the database name to be equal to?"

    It should have been -

    "Using the Dynamic Properties Task, what could you NOT set the database name to be equal to?"

    since the published answer is..

    The only item of the above that you CANNOT set the database name to be equal to is a registry item....

  • Yep, it was wrong when i tried it too. One person had it correct, guess they didn't read the question right 🙂

  • I'm agree, the question was done incorrectly.

  • yes, this is not a serious mailing, there are a lot of errors in the QOD for a month: no question but ansers, incorrect questions and more...

  • The question is NOT CORRECT !

    BUHHHHHH !!!

  • Thanks for the help!

    I picked the only one it couldn't do and got it right, just goes to show that it's worth checking the forums if the question doesn't make sense

    Keith Henry

    DBA/Developer/BI Manager




    Keith Henry



    According to everyone I know I "do something with computers?" for a living, so there you go.

  • fooled me too !

  • Not even Keith posting did help ?

    "It ain't what you know that kills; it's what you know that ain't so

    that kills!"

    Frank

    http://www.insidesql.de

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • Just last week I found myself in the situation of trying to use DTS Dynamic Properties Task to set Server / Database.

    To me, using a query was not an option as surely you have to set the database before you can query it?

    Also, as far as I am aware there is no environment variable available to set the target database / server for a DTS task (as far as DTS is concerned I could be trying to access any database on any server anywhere on our network)

    I didn't trust INI files as I wouldn't trust anyone not to tinker / lose / deliberately destroy them.

    Global variables seemed a non-starter as far as portability is concerned as they still have to have a value assigned so in the end I decided to pass through the required connection destination as a parameter from the calling application.

    Just my two pen'orth

    Mark

  • You bet. The question was wrong. That'll teach me to do these too late! I went ahead and killed all of your answers if you'd like to retake it with the correction question. 🙂

    Brian Knight

    bknight@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/bknight

  • Suppose I'm thinking about compiling some QOD's right now, it would certainly be helpful to see somewhere what questions have been asked yet (and maybe also the answers).

    Should help avoid double or triple repeats, and should save you, Brian, some work

    What do you and the others who already contributed or want to contribute think about it?

    Frank

    http://www.insidesql.de

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • Sorry !!!!

    A momentary lapse of reason.

    Frank

    http://www.insidesql.de

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • I learned my lesson last week about re-reading the question once the website pops up! Don't forget!

    --
    Adam Machanic
    whoisactive

Viewing 13 posts - 1 through 12 (of 12 total)

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