 |
 |
NTP Software News & Events |
 |
| |
 |
|
 |
| |
NTP Software will be attending the EMC Forum in Rosemont, IL on February 18, 2010.
NTP Software and BlueArc Partner to Create Intelligent Storage Solutions.
Read the Press Release here.
NTP Software and Siemens AG Partner to Enhance Storage Services for Siemens Business Services Customers.
Read the Press Release here.
|
|
 |
|
 |
|
|
 |
 |
 |
|
|
| |
Industry News |
|
| |
| |
|
|
| |
Analysts are predicting an improving data storage market in 2010.
To view the article click here.
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
Tech Tidbits |
|
| |
| |
|
|
| |
Go Green with your Storage!
Click here to read about some green data storage tips.
|
|
| |
|
|
|
|
| |
|
|
|
|
|
|
 |
Patrick Hynds
Sr. Storage Architect, NTP Software |
A common question we get from customers is how to use NTP Software quota policies to manage the growth of large files such as Access databases. Managing the size of these databases can be somewhat trickier than managing quotas for other file types, in particular because these files are often accessed by many different users. The actions of any of these users might cause the database to grow beyond defined thresholds, raising the questions of how to manage file size and whom to notify when file size quotas are exceeded.
Among the numerous self In most organizations, the issue of multiple users writing to a database turns out to be a fairly straightforward problem to resolve. The first step is to determine the quota, the thresholds for notification, and the appropriate people to be notified when a threshold is reached or exceeded- in other words, the same items that need to be determined when setting a quota policy for any other type of file.
The key difference in this scenario is that it may be a delicate situation to prevent writes to a database, whether in Access or another format. Because of this, hard quotas for database size are typically undesirable. Rather, soft quotas may be the best management tool for this type of data, allowing writes but warning the appropriate person that the database has exceeded an established quota or threshold.
Once the details of the soft quota have been set, the primary remaining issue is that the user who is writing to the Access database is typically not the person who should be notified that the threshold has been exceeded. Instead, the owner of the database should receive the notification. Since the Access .mdb files are created ahead of time, the ownership of the database can be assigned in advance to the user who should be notified when the file size exceeds a defined threshold. As long as the owner of the database is determined in advance, the “threshold exceeded” notification will always be routed to the proper person.
To learn more
click here.
Suggest a topic for future editions of this newsletter. Email us at newsletter@ntpsoftware.com and let us know.
|
|