vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, I am investigating setting up a shared sql server. I wish to enforce database size quotas, and hopefully still allow customers to manage the creation of their own databases. Any thoughts or suggestions would be appreciated. Kind Regards Simon Hall |
| ||||
| "Simon Hall" <itguy@xtrahost.co.uk> wrote in message news:84f037fd.0404290756.77945c9@posting.google.co m... > Hello, > > I am investigating setting up a shared sql server. I wish to enforce > database size quotas, and hopefully still allow customers to manage > the creation of their own databases. > > Any thoughts or suggestions would be appreciated. > > Kind Regards > Simon Hall CREATE DATABASE is usually restricted only to administrators, to prevent someone grabbing all the disk space. One solution might be a custom database creation/resizing request tool, which could be a web form or whatever. That would allow you to check a request against other information (eg. billing status) before processing it, either manually via a DBA or in some automated way (perhaps using SQLDMO). Alternatively, when you set up a new client, just create a database with the largest size you want to allow them, although since different clients may have different requirements in terms of transaction log use and recovery models, it may not be that simple. There may well be other solutions using genuine disk quotas (ie. in the OS, in SAN software, a commercial app etc.), but since the MSSQL service runs as one user account, I'm not sure how a quota could be linked to a specific login/client. Unless you could do something where a single client's files are all in one folder, then manage that folder. But you'd still probably need some sort of custom tool in that case to handle new requests and assign more space if needed. Simon |
| Thread Tools | |
| Display Modes | |
|
|