April 12, 2010 at 10:29 am
One of our SQL Servers has started experiencing error 17207 file in use by another process on one of its database files.
The AUTO_CLOSE option is true so looking at the SQL logs there are a series of Starting up up database blah....
Then eventually error 17207 appears.
We suspect it might be caused by an auto-growth op, so does anyone know if a database autogrow operation would take an exclusive lock on the .mdf and .ldf files?
April 12, 2010 at 11:39 am
I believe that autogrow does require a lock on the files, but it should be part of SQL Server. I'm not sure what you mean by file in use here with autogrow. If the database was not open and in use, I do not think that autogrow is in effect.
More likely you have some other process, backup, copy, etc. that is holding a lock on the file. You can use FileMon (http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx) from sysinternals to find which process has the handle.
Why do you have auto-close set?
April 12, 2010 at 11:43 am
Maybe somethng in http://support.microsoft.com/kb/2015754 will help.
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
April 13, 2010 at 2:00 am
Its SQL 2005 Express so AUTO_CLOSE is default on
April 13, 2010 at 2:44 am
Thanks for the link. One of the replies mentions if you move databases to a different folder than the default root sql install folder. Ensure permissions for the service account are carried to the 'different' folder.
For space reasones we moved the mdf and ldf to another disk so do you know what permissions the SQL Account needs to this different folder?
April 13, 2010 at 7:13 am
Did you detach/attach the files? If so, then SQL Server should have rights.
You can check the rights on the original folders and then set the new ones. I believe that it needs read/write to the files.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply