Heenan, Lambert
Lambert.Heenan at aiuholdings.com
Mon Jun 1 08:20:29 CDT 2009
Right-click the C drive and select properties, and then hit the Security tab. Make sure that 'Administrators' is listed and that they have 'Full Control' access. Add any other users you might want at this point too. Next click the 'Advanced' button and I the new dialog box click the 'Owner' tab. Change the owner to the Administrators group and check the box to 'Replace owner on subcontainters and objects'. Click the 'Permissions' tab of the same dialog box. Check the box to 'Replace permission entries on all child objects..." Click OK and sit back and wait. Should sort things out for you. HTH Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Sunday, May 31, 2009 11:07 PM To: Dba-Sqlserver; Access Developers discussion and problem solving Subject: [AccessD] What a mess (otherwise knbown as "who owns things") I rebuilt a server from C:\ format on up. New Windows Server 2003 X64, New SQL Server 2005 etc. Now the current administrator (apparently) does not own the files on the raid arrays which of course survive quite nicely. When I tried to attach a database it gave me an "insufficient rights" kind of error which I Googled and that tells me that I do not own the files. I took ownership which worked (I can now attach), but then I tried to attach and it said it couldn't because the files were read only. Only it DID the attach, and now I have a database in read only mode, which I cannot detach because... it is read only. Sigh. So... this invites MANY questions... 1) How do I take ownership of a disk drive on down and all the files on that disk drive? 2) Why are the files read only? 3) Now that I have one of the databases mounted (read only) how do I detach it so that I can make it read / write and reattach it? Or how do I make it non-readonly? 4)Why did all of this happen? 5) Is there an easy way to prevent all this in the future? I have a second server which I will be rebuilding when new parts get here mid week. New motherboard / processor and 5 new terabyte drives for the server I rebuilt this weekend and 5 new drives for the one to be rebuilt next. Obviously if there is something I can do in advance to prevent this mess I am all for that. In fact the new motherboard is the same motherboard as I have in the current rebuild, and my plan is to clone the boot drive and just use that clone in the new system. I have gone to much trouble to get all the multitude of software installed etc so when I am done I HOPE to end up with two literally identical machines, other than the second machine having some additional storage (and a next generation processor). Any words of wisdom out there? -- John W. Colby www.ColbyConsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com