Drop database fails because of aspnet_wp.exe

Hey everyone.

I'm having some problems dropping a database because the aspnet_wp.exe process is accessing it. Whenever I try to drop it, I get an error stating that the database is being used. If I access the task manager and end the aspnet_wp.exe process manually and then retry the database drop it works... :\

Any help? Thaks in advance,

Sérgio

You can't drop the database because it is using by some .NET application. aspnet_wp.exe is a worker process in which .NET runs code, you can take a look at this article:

http://www.xefteri.com/articles/show.cfm?id=14

|||A connection is being kept open by an asp.net application. Either it forgot to close the connection after it was rendering a page, or (more likely), the connection was kept open in the connection pool.

drop and re-create table

What kind of problems may I see if a process drop and re-create a set of
tables every night?A Biggy: You will lose all access permissions that have been set for the
tables -unless you add steps to recreate the permissions on the tables.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:801C90E1-5D1B-4171-8B49-CCAFF38563FC@.microsoft.com...
> What kind of problems may I see if a process drop and re-create a set of
> tables every night?
>|||JIM.H. wrote:
> What kind of problems may I see if a process drop and re-create a set of
> tables every night?
>
Why not just TRUNCATE them?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

drop and re-create table

What kind of problems may I see if a process drop and re-create a set of
tables every night?A Biggy: You will lose all access permissions that have been set for the
tables -unless you add steps to recreate the permissions on the tables.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:801C90E1-5D1B-4171-8B49-CCAFF38563FC@.microsoft.com...
> What kind of problems may I see if a process drop and re-create a set of
> tables every night?
>|||JIM.H. wrote:
> What kind of problems may I see if a process drop and re-create a set of
> tables every night?
>
Why not just TRUNCATE them?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

drop and re-create table

What kind of problems may I see if a process drop and re-create a set of tables every night?

It will be helpful to explain why you need to drop tables on a daily basis.

drop and re-cerate table

What kind of problems may I see if a process drop and re-create a set of tables every night?

foreign key constraint.

you won't be able to support replication at least without dropping it also

database fragmentation

|||It depends on your schema and database. You can have foreign keys, indexed views, schema bound objects referencing tables and there are also the soft dependencies (code that accesses the table). It would help if you explain what you are doing or trying to do? Why do you have to drop and recreate set of tables every day? Are they staging tables?

Drop all indexs with a stored procedure

I want to call a script/sproc at the beginning of a nightly ETL process that
will drop all indexes in a user-defined database.
At the end of the ETL process I will call a stored procedure (I already
have) to recreate the indexes.here's an undoc trick:
exec master..xp_execresultset N'select
''drop index ''+quotename(o.name)+''.''+quo_tename(i.name)
from sysindexes i join sysobjects o on i.id=o.id
where o.type=''U''
and i.indid > 0 and i.indid < 255
and (i.status & (32|64|2048|4096))=0
',N'Your_db_name_goes_here'
For more info on this trick:
http://rac4sql.net/xp_execresu_ltset.asp
-oj
"LP" <LP@.discussions.microsoft.com> wrote in message
news:FCD018BC-D7E2-446B-A49B-CF99FC3F160B@.microsoft.com...
>I want to call a script/sproc at the beginning of a nightly ETL process
>that
> will drop all indexes in a user-defined database.
> At the end of the ETL process I will call a stored procedure (I already
> have) to recreate the indexes.
>

Drillthrough

Hi all,
I'm new to OLAP and especially drillthrough and just have a question about
the way it works.
I can see clearly why the process exists and the complete benefits of it,
but correct me if i'm wrong but:
1. It appears to issue an SQL query against the data source to return the
information and not from the cube?
2. I assume I am able to send parameters to the query , for example the
current dimension selection as parameters? If so, how?
Currently, everytime i try a drillthrough, i get a timeout message from
AS2000 and my server CPU hits 100%.
I am correct in saying, for example, that If i have a value rolled up to a
week, I should be able to use the drillthrough feature to access the
underlying data that makes up that value, AND ONLY THAT DATA and not the
whole fact table which curerntly appears to be happening to me?
Many thanks
Immyyou have to capture the SQL query to verify what's appends exactly.
you have to insure that there is enough joins between your tables, sometimes
AS don't add corectly the right joins which result in a large table scan.
in the drill through option page, you can add static filters which also can
act has join between tables to insure the usage of joins.
"Immy" <therealasianbabe@.hotmail.com> wrote in message
news:eI$0whKXGHA.4132@.TK2MSFTNGP04.phx.gbl...
> Hi all,
> I'm new to OLAP and especially drillthrough and just have a question about
> the way it works.
> I can see clearly why the process exists and the complete benefits of it,
> but correct me if i'm wrong but:
> 1. It appears to issue an SQL query against the data source to return the
> information and not from the cube?
> 2. I assume I am able to send parameters to the query , for example the
> current dimension selection as parameters? If so, how?
> Currently, everytime i try a drillthrough, i get a timeout message from
> AS2000 and my server CPU hits 100%.
> I am correct in saying, for example, that If i have a value rolled up to a
> week, I should be able to use the drillthrough feature to access the
> underlying data that makes up that value, AND ONLY THAT DATA and not the
> whole fact table which curerntly appears to be happening to me?
> Many thanks
> Immy
>