Can I cause damage when using LiveReports

I was sent on the 209 course for training and my Adminastrator is reluctant to give me the privledge to create Livereports in LL. His reason is "I was referring to security and or permissions of these tables, i.e., if a user tries to update or try to add any new information in these tables intentionally or otherwise, this could bring the whole database down. When you queering directly against the underlying tables a small syntax error could cause a lot of problems." Is this true? I am only querying against the database not writing too it?

Find more posts tagged with

Comments

Marie_Lindsay_(MLindsay_(Delete)_15608)

Message from Marie Lindsay <<A HREF="mailto:marie@opentext.com">marie@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Yes, this is definitely true. You may plan to only query the database, but there's nothing preventing you from writing to it or deleting from it.

-----Original Message-----
From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: Friday, October 17, 2003 2:11 PM
To: eLink Recipient
Subject: Can I cause damage when using LiveReports

Can I cause damage when using LiveReports Posted by ONTREL01User1 (Evans, Janet L) on 10/17/2003 03:06 PM

I was sent on the 209 course for training and my Adminastrator is reluctant to give me the privledge to create Livereports in LL. His reason is "I was referring to security and or permissions of these tables, i.e., if a user tries to update or try to add any new information in these tables intentionally or otherwise, this could bring the whole database down. When you queering directly against the underlying tables a small syntax error could cause a lot of problems." Is this true? I am only querying against the database not writing too it?

eLink User

Message from Mohsin Jessa via eLinkHi Janet:Your Admin is justifiably concerned about not only the integrity of the databut the upkeep of the data source also (i.e the database) and theapplication (i.e LiveLink).Potentially you could damage the d/b logically (i.eupdating,modifying,deleting) records from tables etc...You could also unknowingly write a query that could bring the entire d/b andLiveLink to a stand still.A classical example would be to write a join between several large tablesand make an error in the where condition or not have a join condition atall. The sql would still be valid, but would return what is called aCartesian product which could be millions and millions of records. Thiswould tie up a LiveLink thread and keep the d/b working like crazy (not tomention flood the memory with useless information and the disks workingovertime to retrieve the data).While you as a LiveReport user would not know what was happening, so infrustration you would re-run the report and it would tie up the next threadand so on. So in three attempts you could not only lock up the LiveLinkserver but choke up the d/b server too - oh and have network packets beingtransmitted like crazy.So, in this case he is right.Hope this helps. _____Mohsin M. JessaOracle Technical Specialist (Escalation Group)Open Text CorporationPh: 519-888-7111 x 2416Fax: 519-888-6737Email: mjessa@opentext.com _____Join us in Orlando for LiveLinkUp 2003!Open Text ConferenceOrlando, Florida, USANovember 3-6, 2003Find out how we're helping sixteen million great mindswork together to improve efficiencies and save money.livelinkup-orlando.opentext.com -----Original Message-----From: eLink Discussion: Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com]Sent: Friday, October 17, 2003 3:11 PMTo: eLink RecipientSubject: Can I cause damage when using LiveReportsCan I cause damage when using LiveReportsPosted by Evans, Janet L on 10/17/2003 03:06 PMI was sent on the 209 course for training and my Adminastrator is reluctantto give me the privledge to create Livereports in LL. His reason is "I wasreferring to security and or permissions of these tables, i.e., if a usertries to update or try to add any new information in these tablesintentionally or otherwise, this could bring the whole database down. Whenyou queering directly against the underlying tables a small syntax errorcould cause a lot of problems." Is this true? I am only querying againstthe database not writing too it?[To reply to this thread, use your normal e-mail reply function.]============================================================Discussion: Livelink LiveReports Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2249677&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

Victoria_Freihofer_(rgsinc01admin_-_(deleted))

Message from Olson, Leonard via eLinkAnother viewpoint: It would be perfectly OK for someone with a basic knowledge of SQL to write LiveReports as long as they take a few precautions. The first precaution is to not write reports that can modify the database --Leave the box UNCHECKED. Two; always use the "filter by permissions" parameter when querying against dtree (this feature does not apply to workflow tables). Three, check the schema: this will help avoid a lot of frustration and errors. And last, where possible test your SQL in a non-production test environment that matches Livelink and database versions. -----Original Message----- From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Fri 10/17/2003 4:33 PM To: eLink Recipient Cc: Subject: RE Can I cause damage when using LiveReports 2 RE Can I cause damage when using LiveReports 2 Posted by eLink on 10/17/2003 04:33 PM In reply to: Can I cause damage when using LiveReports Posted by ONTREL01User1 (Evans, Janet L) on 10/17/2003 03:06 PM Message from Mohsin Jessa via eLinkHi Janet: Your Admin is justifiably concerned about not only the integrity of the data but the upkeep of the data source also (i.e the database) and the application (i.e LiveLink). Potentially you could damage the d/b logically (i.e updating,modifying,deleting) records from tables etc... You could also unknowingly write a query that could bring the entire d/b and LiveLink to a stand still. A classical example would be to write a join between several large tables and make an error in the where condition or not have a join condition at all. The sql would still be valid, but would return what is called a Cartesian product which could be millions and millions of records. This would tie up a LiveLink thread and keep the d/b working like crazy (not to mention flood the memory with useless information and the disks working overtime to retrieve the data). While you as a LiveReport user would not know what was happening, so in frustration you would re-run the report and it would tie up the next thread and so on. So in three attempts you could not only lock up the LiveLink server but choke up the d/b server too - oh and have network packets being transmitted like crazy. So, in this case he is right. Hope this helps. _____ Mohsin M. Jessa Oracle Technical Specialist (Escalation Group) Open Text Corporation Ph: 519-888-7111 x 2416 Fax: 519-888-6737 Email: mjessa@opentext.com _____ Join us in Orlando for LiveLinkUp 2003! Open Text Conference Orlando, Florida, USA November 3-6, 2003 Find out how we're helping sixteen million great minds work together to improve efficiencies and save money. livelinkup-orlando.opentext.com -----Original Message----- From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Friday, October 17, 2003 3:11 PM To: eLink Recipient Subject: Can I cause damage when using LiveReports Can I cause damage when using LiveReports Posted by Evans, Janet L on 10/17/2003 03:06 PM I was sent on the 209 course for training and my Adminastrator is reluctant to give me the privledge to create Livereports in LL. His reason is "I was referring to security and or permissions of these tables, i.e., if a user tries to update or try to add any new information in these tables intentionally or otherwise, this could bring the whole database down. When you queering directly against the underlying tables a small syntax error could cause a lot of problems." Is this true? I am only querying against the database not writing too it? [To reply to this thread, use your normal e-mail reply function.] ============================================================ Discussion: Livelink LiveReports Discussion https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2249677& objAction=view Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe _____ [To reply to this thread, use your normal e-mail reply function.] Topic: Can I cause damage when using LiveReports Discussion: Livelink LiveReports Discussion Livelink Server: Knowledge Center

volvostephen

As a Livelink Admin, I wouldn't want anyone here to be writing Reports Directly in our Production Environment. We use SQL server here and I always develop the reports in SQL Query Analyser first before moving to Livelink. Things are far easier to debug that way. Also, if you run a long running report in SQL Server without setting the transaction level appropriately, you can lock your system. To avoud this, I always make sure to allow dirty reads by using 'with (nolock)'. For example - select * from dtree with (nolock).So, I would grant you full rights to create Livel Reports in a development system and then have a process by which an Admin can put them into production. I think this would be a good compromise.

Lee_Butler_(lbutler_(Delete)_2946657)

Message from Lee Butler <<A HREF="mailto:lbutler@opentext.com">lbutler@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi,

Better late than never...

You can alleviate some of these issues by Separating the SQL query from the display of the actual data. The WebReports PSO module does just this. Your SQL statements/LiveReports are written by someone with the appropriate privileges but you can then utilise this "raw" LiveReport information using WebReports. On the whole the LiveReports should be simpler and faster to develop as you'll be processing/filtering most of the data in the WebReport. This should make your admin happy as he/she will only have to implement a smaller number of simpler LiveReports. You can then use lots of different WebReports to cut/present the LiveReport data in many different ways through basic HTML/JavaScript.

Cheers,
Lee.

-----Original Message-----
From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: 17 October 2003 20:11
To: eLink Recipient
Subject: Can I cause damage when using LiveReports

Can I cause damage when using LiveReports Posted by ONTREL01User1 (Evans, Janet L) on 10/17/2003 03:06 PM

I was sent on the 209 course for training and my Adminastrator is reluctant to give me the privledge to create Livereports in LL. His reason is "I was referring to security and or permissions of these tables, i.e., if a user tries to update or try to add any new information in these tables intentionally or otherwise, this could bring the whole database down. When you queering directly against the underlying tables a small syntax error could cause a lot of problems." Is this true? I am only querying against the database not writing too it?