Alert by Database/ Table

• 
  Hi,
  
  Thanks for your post.
  
  To obtain alert for a particular database, expand the SQL Instance name on the left hand navigation. Then select the database. This will show all the alerts for the selected database. SQL Monitor doesn't have any table specific alerts hence filtering by table is not supported.
  
  What is the version of SQL Server for which Top 10 queries are empty? Top 10 query feature is not supported for SQL Server 2000. There are certain criteria which a query has to satisfy in order to qualify for this. This includes 'Execution Count > 50', 'Total Physical Reads > 50' etc. So if the queries running in your environment are not expensive enough to be collected by SQL Monitor then you wont see it in UI.
  
  Hope this helps. Let us know if you have more questions.
  
  Thanks,
  Priya

  priyasinha June 03, 2011 04:45

  - 0 +
• 
  I've expanded the SQL Instance name on the left hand navigation and select the Database under the Instance, a message "No alerts match your current filter settings" shown at the right hand side.
  
  I'm using SQL 2000 Enterprise x86

  xexex June 03, 2011 05:51

  - 0 +
• 
  Hi,
  
  Thanks for your reply.
  
  Regarding database alerts ... that message indicates that no database specific alerts have been raised (for the chosen database) and hence nothing is being shown when you select that particular database.
  
  As mentioned in my previous post, "Top 10 queries" is not supported for SQL Server 2000.
  
  Thanks,
  Priya

  priyasinha June 03, 2011 06:57

  - 0 +
• 
  
  
  Uploaded with ImageShack.us

  xexex June 06, 2011 23:17

  - 0 +
• 
  Hi,
  
  Thanks for the image. I understand it better now.
  
  It all depends on how alerts are grouped in SQL Monitor. "Long running query" alert is grouped per instance hence when you select database it doesn't get filtered against it. Some of the alerts which are grouped per database are "Log backup overdue", "Backup overdue" etc.
  
  I have raised an enhancement request for grouping "Long running query" by database instead of instance. For your reference, the issue number is SRP-4347.
  
  Thanks,
  Priya

  priyasinha June 07, 2011 05:25

  - 0 +
• 
  Which alert will be grouped by database?

  xexex June 07, 2011 05:29

  - 0 +
• 
  Hi,
  
  The following alerts are grouped per database:
  
  1. Backup overdue
  2. Database unavailable
  3. Fragmented indexes
  4. Integrity check overdue
  5. Log backup overdue
  6. Page verification
  
  Thanks,
  Priya

  priyasinha June 07, 2011 07:37

  - 0 +
• 
  Thanks, I can see fragmented index recommendation in SQL response but I can't find it on SQL monitor.
  
  
  
  

  xexex June 08, 2011 03:11

  - 0 +
• 
  Hi,
  
  Fragmented Index check only runs at 1 AM every Sunday. How long you had SQL Monitor installed for after you changed the Configuration?
  
  Thanks,
  Priya

  priyasinha June 08, 2011 04:36

  - 0 +
• 
  IC, I've install SQL monitor last week and change the config today.
  
  Thanks

  xexex June 08, 2011 04:44

  - 0 +
• 
  Okay. In that case, I would wait till the next week.
  
  Regards,
  Priya

  priyasinha June 08, 2011 06:02

  - 0 +
• 
  Tried but no luck
  

  xexex June 09, 2011 21:30

  - 0 +
• 
  Apologies, but just to clarify. I assume that you are looking for "Fragmented Index" alert. Not sure what time zone you are in? But if you changed the config on 8th June then the next scheduled fragmentation index check on SQL Monitor will happen only at 1 AM on 12th June (local time on Base Monitor machine).
  
  I would look for this alert only after this time. Please let me know if you have any more questions or in case I have misunderstood your questions?
  
  Regards,
  Priya

  priyasinha June 10, 2011 04:23

  - 0 +
• 
  Oh, my bad, I've overlook the date (Sunday), I will check the result on next Monday.
  Thanks.

  xexex June 10, 2011 04:33

  - 0 +

Add comment

Please sign in to leave a comment.