Process Locking Database

[faust13]

Does anyone know what process locks the ASPNETDB file in the production environment (i.e. IIS).

I am trying to make changes to the database after it's been live using SQL Management Studio. The DB was created using VWD 2005.

Any Suggestions?


Thanks,

faust13
Because Han Shoots First

http://www.hanshootsfirst.org

 

[jbenson001]

what do you mean locks?

 

[faust13]

I'm using SQL Management Studio on the production box to attach the DB. However when I try to attach, it says that a process has the file locked and won't let me attach.

I shut down all the services taht would likely be the culprits, but the file is still showing as locked.

If there's a better way of making changes to ASPNETDBs on the production box, please let me know.


Thanks,

faust13
Because Han Shoots First

http://www.hanshootsfirst.org

 

[jbenson001]

I'm using SQL Management Studio on the production box to attach the DB

Are you saying you are connecting to a database that is not on your db server?

 

[jbenson001]

or did you do a detach then are trying to do an attach?

 

[faust13]

The web app and the db are on the same server. I'm using SQL Management Studio (on the server) to attach to the ASPNETDB, so I can manually make my updates on the production box.

I cannot remotely access (with VWD or SQLMS) the production box becuase of security.


Thanks,

faust13
Because Han Shoots First

http://www.hanshootsfirst.org

 

[jbenson001]

I am not sure what you mean by attach. Attach has a specific meaning in SQL Server. Do you mean "Connect"?

You connect to that DB as you would any other db. If you are getting an error, then you should really post in the SQL Server forum: forum183

 

[faust13]

In SQLMS, you attach databases. Normally it's not a problem, but for some reason with the ASPNETDB it is. I suspect there's some background ASP.Net process that's locking it.

Thant's why I haven't posted it on the the SQL forums, as they're more SQL Server centric, most of the guys over there don't use the default ASPNETDBs. Everytime I post regarding that, I get told to convert it to a traditional SQL Server DB, which isn't an option because of my security constraints. This seems to be a no man's land, SQL Server DBAs don't know anything about them (ASPNETDB), and .Net guys don't have the security constraints that prohibit them connecting via VS or VWD.


Thanks,

faust13
Because Han Shoots First

http://www.hanshootsfirst.org

 

[faust13]

If I stop the site and wait long enough, I can attach, but I can't wait 30 minutes to make a 30 second change. There must be a single process holding the DB open, and I'm just trying to figure what it is. It must be a .Net process, by process of elimination.


Thanks,

faust13
Because Han Shoots First

http://www.hanshootsfirst.org

 

[Rhys666]

Have you ensured all utilised connections are closed and disposed after use?

Rhys
The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offense Edsgar Dijkstra

Church of the Flying Spaghetti Monster

 

[faust13]

Rhys666,

That may be it. I'm confident I didn't programatically close all my connections.

I just want to be sure what you're saying. If I don't programatically close all connnections in my .Net code, it will leave an open process that is connected to my db, which prevents SQLMS from attaching?


Thanks,

faust13
Because Han Shoots First

http://www.hanshootsfirst.org

 

[ca8msm]

Yes, have a look at the SQL Profiler and you will see any open connections.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.