cancel
Showing results for 
Search instead for 
Did you mean: 

Uncommited isolation level or With no lock for Crystal report

Former Member
0 Kudos

Hi, I have been working with Crystal report for Vs.net 2005 since long time ago, I have developed a fair amount of reports, most of them not using SP or querys, I have used tables and relations so crystal report itself generates the sql.

Now, I have been told that seems like the reports are constantly locking the records in our database (sql2000) so we want to add the NOLOCK thing or change isolation level to uncommited..... but how can I do that to 200+ reports which are not comming from SP.

I'm usng OLEDB connection to our sql server ....

I appreciate your help!

thanks!

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi, thanks for the answer but I cannot see in any way that you have answer the question, first becuse my connections is OLEDB and second because you don't even know if this is possible to do in CR, finally your recomend to see the Microsoft help... honestly don't you think that the first thing people do is check the help of Microsoft and Business object?

thanks

ido_millet
Active Contributor
0 Kudos

From personal experience:

1. Don has been extremely helpful in these forums (I'd hate to see his motivation dimmed by comments like the previous message)

2. OLEDB connections can be changed to ODBC connections

3. Many people don't check online help resources before posting questions

Don, it would be nice to have a clarification explaining if this isolation level registry option is valid for ODBC connections in later versions of Crystal. That note is very old - it refers to Crystal 8.

Former Member
0 Kudos

I'll have to disagree again, how come is helpful if is not anwering it...

I'll not enter in discussions of this kind... I was just making a point of please don't just anwer questions... for answering...

answer them when you hae the answer... so many people just answer for the points!

yes of course can be change to ODBC but I did explain I have 200+ reports... I'll have to change for all of them - and also I did tell what was my crystal report version... and he don't even know if the answer he is giving could work for odbc and cr in .net... so again... how come this be the answer?

ok lots of people don't check the help... but again... is not answering telling someone to check the help.....

thanks

0 Kudos

Hi Lindaot,

Sorry you are correct. I did not think to tell you that CR has NO options to turn on/off Isolation levels when using OLE DB. To do this CR side your only option is to use ODBC, to do this Client/Server side you'll have to ask Microsoft. Others have done this by using an internal stored procedure or add the uncommitted or no lock state in the stored procedure. If you decide to use ODBC the registry key is for .NET.

All, or 99% of the legacy registry keys are carried forward, what worked in CR 8 should still work. But of course there are exceptions depending on the functionality/feature.

Personally I don't care about points, I just give them for quality answers or mark the post as answered otherwise....

If you want to update your reports you have an option to either write your own report verifying tool or Ido has access to third party tools you could use.

Thank you

Don

Former Member
0 Kudos

Thanks

I'll try the key and see what happens.....

0 Kudos

Hello,

Although it is not recommended for obvious reasons, any data marked to be deleted is also reported on, you can set this up but not sure if it works for CR .NET.

In this [note|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233313332333033363336%7D.do]: it refers to CR 8 so just change the path to: HKEY_CURRENT_USERSoftwareCrystal Decisions10.2Crystal ReportsDatabaseOptions and add ODBC key.

If this doesn't work then your only option is to do this server side. For info on how to Please refer to Microsoft's help files for SQL Server 2000.

Thank you

Don