SQL DB crashed while running Impromptu Query

[JaneWilder]

Has anyone ever brought down a SQL DB while running an impromptu query? What would be the cause of this? The same thing has also happened while generating categories for an iqd in transformer. I am able to schedule these to run at night when users are not accessing the data but when I run them in the day it seems to crash the SQL DB every now and then.

Any help would be appreciated.
Jane

 

[n30er]

You should probably check system and DB temp and disk space, you might be running out.

 

[JaneWilder]

The SQL error is:
Process ID 36 attempting to unlock unowned resource Rid: 7:1:111907:14

Error: 1203, Severity: 20, State:1

There are times when I am not even connected to the DB when running a query and it gives this error.

 

[n30er]

Not sure what the message is, I would check the SQL Server messages (help). On the second part, how do you run a query without being connected to the DB?

 

[JaneWilder]

While opening the catalog you uncheck the connect to database box. What I meant to say was that you open the imr in impromptu without connecting to the database not run a query without connecting to the database. Sorry about that.

Could it be possible that when I open an imr in impromptu it locks the tables in the database and prevents users from accessing them?

 

[n30er]

I'm not sure if it does a read lock or not. I imagine that it is connecting natively so if you connect using another application to query the DB it would do the same behavior. Regardless you said that just the one query (IMR) will lock the DB up so I would think that the problem lies in the DB, not Impromptu. Sorry that I am not a SQLDB dba or I would know more on where to look. You might want to try some of the SQL DB newsgroups and ask about queries that lock up the DB and see what dba might think.