July 2, 2008 at 1:23 pm
I have two instances of SQL 2000 running on the same server on the same volume. The users of one of the instances continually use up the disk. This effectively crashes both instances of SQL Server. I am trying to prevent that from happening. My idea was configure their instance of SQL Server to run as a specific user and then set a disk/volume quota on that user. Unfortunately, when SQL creates backups, windows assigns Administrators as the owner, instead of the user that SQL is running as. So this is outside of the quota I have set on the user.
Any ideas on forcing the owner of the backups to be the same as the user SQL?
A couple of options considered that are not practical for the situation: rebuilding/repartitioning the machine/drive and setting size limits on the databases individual databases. Are there any other ways on limiting the size of this instance of SQL?
Thanks
Mike G.
July 2, 2008 at 1:45 pm
Make the SQL Service account the owner of the folder? might be inheriting permissions from above for the files.
July 2, 2008 at 2:21 pm
Thanks.
I gave it a try, but it still assigns Administrators as the owner of newly created trn files.
I also tried removing "Take Ownership" from the Administrators group. Still, new trn files are created with Administrators as the owner.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply