Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 The minimum record count threshold

Author  Topic 

CanadaDBA

583 Posts

Posted - 2005-10-06 : 10:21:36
I received this email from my production server:
Message from PROD_SERVER - The minimum record count threshold of 14000, for [tblTasks] in the TaskDB database, has been exceeded. The current record count is 13598

Does this mean that the TaskDB has reached its limit and I have to archive some records? Is it a serious problem in my production?

Thanks,

Canada DBA

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2005-10-06 : 12:36:54
I'm not familiar with this message. I believe it is a custom alert. Did someone setup this alert? Do you know where it is setup?

Tara
Go to Top of Page

CanadaDBA

583 Posts

Posted - 2005-10-06 : 12:45:53
Yes, this is from an alert. I think the previous DBA had set it up.

Is there any beneficial to have this setting? Do I need to take an action? What should I do?
quote:
Originally posted by tduggan

I'm not familiar with this message. I believe it is a custom alert. Did someone setup this alert? Do you know where it is setup?

Tara



Canada DBA
Go to Top of Page

SQLServerDBA_Dan
Aged Yak Warrior

752 Posts

Posted - 2005-10-06 : 12:53:10
quote:
Originally posted by farhadr

Yes, this is from an alert. I think the previous DBA had set it up.

Is there any beneficial to have this setting? Do I need to take an action? What should I do?
quote:
Originally posted by tduggan

I'm not familiar with this message. I believe it is a custom alert. Did someone setup this alert? Do you know where it is setup?

Tara



Canada DBA



This has nothing to do with the SQL Server itself... it's a part of your internal processes in your environment that seems to have gone wrong. I'd check and see exactly what tbltasks is and how your business uses that table. Maybe if you import data from some other entity then today you imported less than expected or something along those lines.

Daniel
SQL Server DBA
www.dallasteam.com
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2005-10-06 : 12:58:14
You'd have to talk to the previous DBA to know what it was intended for. There's no way for us to know it's intention as the alert is application specific and not a general SQL Server alert. For some reason, the previous DBA thought that table should never be below 14000 rows. Perhaps your users or the developer would know why if you can't get in contact with the previous DBA.

Tara
Go to Top of Page
   

- Advertisement -