Results 1 to 5 of 5
  1. #1
    Join Date
    May 2003
    Location
    California Coast
    Posts
    72

    Unanswered: profiler cannot connect to db to log to table

    when ever a profiler trace is run it times out and presents an alert box that states failed to start a new trace. I have tried to run index wizard from within profile as well and recieved a cannot connect to db message. All this magic is done as sa account.

    Mike

  2. #2
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    True, only members of the sysadmin fixed server can execute those tools. Refer to BOL for more information.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  3. #3
    Join Date
    May 2003
    Location
    California Coast
    Posts
    72
    Originally posted by Satya
    True, only members of the sysadmin fixed server can execute those tools. Refer to BOL for more information.
    thanks for the post. I will look into that info.

    BTW, this is all done on the same server - there is no network connection. So I was expecting sa to be part of the sysadmin fixed server. This process works on 1 of 3 machines and I don't see the difference (yet) in the setup.

    Thanks again,
    Mike

  4. #4
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    True, SA have all the powers on SQL Server.
    Still sometimes if you get error stating trace cannot be started, then try to restart after a while and refer to SQL Error log for any information.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  5. #5
    Join Date
    May 2003
    Location
    California Coast
    Posts
    72
    this has been the condition for the past 3 days. I am reviewing BOL now and will post my findings.

    mike

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •