Does Crystal !! Lock Table 1

[LooseUnit]

Using Crystal 11 via ADO in classic asp against MS SQL 2000.
Our DBA is suggesting that our Crystal reports are locking tables on our production server(don't ask)whilst running. He says it is either the report or the sub-report that is responsible.The locks are causing kickouts on production apps.
The problem I have is that all he is seing is the sql query and cannot identify the source. We have approx 30 cryatal reports and a number of asp.net reports running on our internal webserver.
Does anyone know of an offical Business Objects Paper that outlines the types of locks Crystal 11 will take?
What I'm hoping for is something that take the issue from my desk and puts it on the .net developers desk.;-)

 

[dgillz]

Unless the application itself need the table without any one else reading it at the time, I am not buying it.

If you really want to put this to the test create a new windows user and log into the network with it, and run crystal. In SQL enterprise manager you can see the user who is locking the table. If it is not the new user, it is not crystal.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"What version of URGENT!!! are you using?

 

[MJRBIM]

Unlikely, if you are using the CRYSTAL tools to generate the SQL.

However, if your reports are based on a COMMAND or MS-SQL STORED PROCEDURE - one of those methods of data-access may have a LOCK function in it while the RPTs are executing.

 

[LooseUnit]

dgillz that worked a treat.
We used the profiler in Enterprise manager and set up a new user as suggested.
I wrote a quick and very nasty report adding a subreport that was completely unnessesary aquiring a field I could have retrieved without the subreport.
On running the report a requesting the last page the report went crazy with the subreport accessing the database 3 or for times a second.
No matter how I manipulated the report I could not force a lock of any sort besides the session lock expected.
This put the focus on our .net developer and within an few minutes we found data/table locking queries.