QOD 6/13

  • Am I being a dork here but SQL7 EM does not have 'Error Logs' option let alone configure it?

    Far away is close at hand in the images of elsewhere.
    Anon.

  • Neither does SQL 2003. IT is called "sql server Logs". The options that were given are missleading as the 3rd option is also correct as I have tried this and also checked this with the technet site. I think that the people who answered the 3rd option should have ther answer corrected to "correct".

    Finaly the question sound like a Microsft exam trick question. Please rectify this If only to save face. Thanks. Dom.

  • hmm...seems to be once again kind of misleading.

    If you click on configure, a window pops up with the title 'Configure SQL Server Error Logs'

    Cheers,

    Frank

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

  • Inside Microsoft SQL Server 2000 by the folk at redmond explicitly states answer 3 as being the way to do it. => It should be marked as correct for those that got it.

    boy is my head hurting this morning

  • If you check out this link

    http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B196909

    it states thet the configure option is on 2000 EM.

    For SQL7 you have to create the following key

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\NumErrorLogs

    Since the question did not specify a version of SQL and I am on SQL7, technically none of the answers are correct (unless answer 4 is a typo?)

    Far away is close at hand in the images of elsewhere.
    Anon.

  • Hi David,

    quote:


    If you check out this link

    http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B196909

    it states thet the configure option is on 2000 EM.


    you mean this passage?

    NOTE: In SQL Server 2000 Enterprise Manager, the number of error logs that are created before they are recycled is configurable through the context-sensitive popup menu for SQL Server Logs. For more information, see the "Configure SQL Server Error Logs" topic in SQL Server 2000 Books Online.

    Cheers,

    Frank

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

  • Yep Frank, thats it. It is the only MS page I could find that specifies this. Other web sites mention the use of registry change as stated in the article.

    I am not miffed that I got the answer wrong (I chose 4 but did not look at key closely) but I am miffed that it is assumed that everyone is a lucky bugger and are on SQL 2000

    Far away is close at hand in the images of elsewhere.
    Anon.

  • quote:


    I am not miffed that I got the answer wrong (I chose 4 but did not look at key closely) but I am miffed that it is assumed that everyone is a lucky bugger and are on SQL 2000


    I use both!

    Hey, domwoolgar is on SQL2003. How about that?

    Cheers,

    Frank

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

  • Nice to know someone is! My boss is reviewing our SQL strategy and looking to move to SQL2000. Don't know when. Can't see us moving 2003 for a while.

    Far away is close at hand in the images of elsewhere.
    Anon.

  • Just catching up with the forum here.

    May I suggest that you do a search on the following quote "increase the number of SQL Server error logs " from the question.

    I used the yahoo search engine. As the question did not specify a version this made the question unclear because in SQL 2000 there is a registry setting that does change the values but, as stated by others there is the configure option., but the question states that you "Right-click on Error Logs in Enterprise" which is answer one. I think they meant "Right-click on SQL Server Logs in Enterprise Manager".

    Secondly my appologies to impress those who thought I was refering to "yukon". I was using SQL 2000.

    Anyhow It is only worth one point but the question should be void (based on the above) and that is my final though on this issue.

    Bye all...

  • I think that the people that answered with the 3rd option should have their answers made correct. This was a trick question. There are multiple ways to do this. Here are some I found with a Google Search.

    INCREASE THE NUMBER OF ERRORLOGS THAT SQL SERVER MAINTAINS

    There are two methods for adding the number of errorlogs that SQL Server

    will maintain: using SQL Enterprise Manager (SEM) or the extended stored

    procedure, xp_regwrite. Exercise caution when using the xp_regwrite

    extended procedure, however, as it will modify the registry. Before

    attempting to use this procedure, you should first back up the server's

    registry

    and thoroughly test the procedure.

    Option 2:

    1. Open Query Analyzer.

    2. Run the following command to retrieve the current number of

    errorlogs that SQL Server will maintain:

    exec master..xp_regread N'HKEY_LOCAL_MACHINE',

    N'SOFTWARE\Microsoft\MSSQLServer\MSSQLServer',

    N'NumErrorlogs'

    3. Run the following command to update the number of errorlogs that SQL

    Server will maintain where x is the number of logs desired:

    exec master..xp_regwrite N'HKEY_LOCAL_MACHINE',

    N'SOFTWARE\Microsoft\MSSQLServer\MSSQLServer',

    N'NumErrorlogs',

    'REG_DWORD', x

    4. Run the following command to verify that the number of errorlogs has

    been changed to the value used in the previous command:

    exec master..xp_regread N'HKEY_LOCAL_MACHINE',

    N'SOFTWARE\Microsoft\MSSQLServer\MSSQLServer',

    N'NumErrorlogs'

    5. Run the following command multiple times to add errorlogs (but not so

    many times that you cycle out the errorlogs containing important

    information):

    exec master..sp_cycle_errorlog

    1429 » How do I increase the number of SQL Server error logs?

    To increase the number of error logs, use Regedt32 to navigate to:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer

    On the Edit menu, Add Value name NumErrorLogs, as a type REG_DWORD. In the DWORD Editor, click the Decimal Radix and enter a number greater than 7.

    Wendy Johnson


    Wendy Schuman

  • Just thought I'd throw my hat in the ring...

    Looks like there are multiple correct answers.

    #1 is certainly correct and is the easiest to perform.

    Kalen Delaney's "Inside Microsoft SQL Server 2000" (p 164) details #4 as the longhand procedure for extending the number of error logs that are retained for a default SQL Server instance. Slightly different key for a named instance.

    And you're finding refs exhorting #3 as the answer, too? Wow...

    It must be Friday. Enjoy!

    Stuart

    Stuart

    "Chance is always powerful. Let your hook be always cast. In the pool where you least expect it, will be a fish" - Ovid

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

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