DB read only after reattached

I am running into a problem that I need help with. The problem is
preventing me from successfully installing our software at a new
customer site. The system configuration is Windows Server 2000 SP 4
with SQL 2005 SP 1.
The problem is that when our install tries to attach the mdf and ldf
files, the process fails because the database is read-only and this
prevents the files from being upgraded from SQL 2005 (they are from a
SQL 2000 system). I have seen this problem in the past and it has
always been due to a permissions issue. If the service that SQL
Server is running under does not have write permission to the folder
that the files are located in, then this problem will show up.
However, this does not seem to be the case at present. In trouble-
shooting this problem, I have discovered that I can create a new
database with no problem at all (showing that I do have write
permission), but if I detach that database and then reattach the
associated mdf file, it will be reattached as a read-only database. I
can change the read-only option setting of this database to False and
that will then allow me to write to the db once again, but why did SQL
Server make it read-only when I reattached it?
Try to dig something in this
http://www.dbtalk.net/microsoft-public-sqlserver-setup/attach-database-became-readonly-301452.html
Manu
"Brandon Wilhite" wrote:

> I am running into a problem that I need help with. The problem is
> preventing me from successfully installing our software at a new
> customer site. The system configuration is Windows Server 2000 SP 4
> with SQL 2005 SP 1.
> The problem is that when our install tries to attach the mdf and ldf
> files, the process fails because the database is read-only and this
> prevents the files from being upgraded from SQL 2005 (they are from a
> SQL 2000 system). I have seen this problem in the past and it has
> always been due to a permissions issue. If the service that SQL
> Server is running under does not have write permission to the folder
> that the files are located in, then this problem will show up.
> However, this does not seem to be the case at present. In trouble-
> shooting this problem, I have discovered that I can create a new
> database with no problem at all (showing that I do have write
> permission), but if I detach that database and then reattach the
> associated mdf file, it will be reattached as a read-only database. I
> can change the read-only option setting of this database to False and
> that will then allow me to write to the db once again, but why did SQL
> Server make it read-only when I reattached it?
>
|||Hooray!!! The problem has been resolved!
The problem with attaching databases always being set to a Read-Only
status was corrected by upgrading the server from Windows Server 2000
to Windows Server 2003. My bet is that the real cause of this issue
was due to the fact that the customer had set this server up as a
backup domain controller, and I think that because it was a Windows
2000 system, it was not communicating properly with the primary domain
controller (which is their Windows 2003 SBS server). This was
probably causing some ambiguity in determining permissions.
On Dec 12, 8:51 am, manu <m...@.discussions.microsoft.com> wrote:
> Try to dig something in thishttp://www.dbtalk.net/microsoft-public-sqlserver-setup/attach-databas...
> Manu
>
> "Brandon Wilhite" wrote:
>
> - Show quoted text -