Hi, It would have been nice if you had included the community. While the exclusion of that feature may seem non-critical at first sight, it represents a highly valuable functionality for fairly common usecases.
The PERMLIMIT functionality enables the deployment of multiple databases (schemas) dedicated to independent projects or customers using a single SAP DB instance. While it is possible to implement a similar scenario without it, such a system would be vulnerable to excessive storage allocations which could in turn cause a denial of service. Without the PERMLIMIT, a schema-based storage allocation quota in respect to the data devspace, this potential weakness cannot be solved. Operating System quota mechanisms cannot be applied because these could only affect a specific operating system user / group - an SAP DB instance as a whole. For us, the PERMLIMIT provided by 7.3 was a key feature for a planned project of ours because it would have allows us to setup strict per database / schema / customer quotas in order to protect the complete instance - one schema may not cause a different schema or the complete service to go down / deny service. SAP DB is (was) the only open source RDBMS supporting schema quotas as far as we know, one (certainly not the only) reason for us to take a closer look at SAP DB. Oracle for example provides a very similar functionality, resource limits, they've implemented resource limits because security / availability becomes increasingly important. Oracle's opinion, quoting the Oracle documentation: <quote> (...) This resource limit feature is very useful in large, multiuser systems, where system resources are very expensive. Excessive consumption of these resources by one or more users can detrimentally affect the other users of the database. In single-user or small-scale multiuser database systems, the system resource feature is not as important, because users' consumption of system resources is less likely to have detrimental impact. (...) </quote> http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920 /a96524/c23acces.htm#6381 Please reconsider your decision, while PERMLIMIT may not be strictly required for SAP R/3 installations, it's a highly valuable and even essential functionality for other usecases (see above). My suggestion is to call for comments within the community, please let others participate in your decision making. cheers, Horst G Reiterer Chief Executive Officer netarray, Austria -- [EMAIL PROTECTED] "Strahl, Torsten" <[EMAIL PROTECTED]> wrote in message 37DE83A2B945D3118B180008C75D3E8D0A8291E3@dewdfx25">news:37DE83A2B945D3118B180008C75D3E8D0A8291E3@dewdfx25... > Hi Wolfgang, > sorry but SAP DB 7.4 will not support PERLIMTS anymore. > Caused by the re-implementation of the converter component, > we decided not to re-implement the PERLIMIT feature, because > we are of the opinion that PERLIMITs are not up-to-date. > > Regards, > Torsten > > SAP DB, SAP Labs Berlin. _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
