Hi Jiri... I wanted to avoid this option because I have about 20 tables.
I have done this when I had a MSSQL to Oracle connection, but I was kind of hoping that I could avoid it here... I am going to try synonyms for the database link name - if this fails then it's time to put on the "Bob the Builder" hat. Thanks. On Friday, March 23, 2012 11:53:10 AM UTC-4, Jiri Pospisil wrote: > > ** > > Try creating a local view of the remote table first, i.e. in the Remedy > database. > > Then build the view form on the local view rather than remote table with > all the link connection string. > > This way you get much better chance that the view form gets built since > Remedy can see it as a simple local view. > > > > Regards > > Jiri Pospisil > > LCH Clearnet > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Elry > *Sent:* 23 March 2012 15:48 > *To:* arslist@ARSLIST.ORG > *Subject:* View Form Fails With Linked Database > > > > ** Hi Folks... > > > > I am having a little trouble creating and saving a View Form based on a > MSSQL to MSSQL database link. > > > > Environment: > > - Windows Server 2008 > - ARS 7.5 Patch 2 > - MSSQL Server 2008 > > Preface: > > > > We have followed what is outlined in the manual for this procedure: > > > > ====================================================== > > Setting up a remote database for view forms > > ====================================================== > > *SQL Server Setup* > > · Create a link to the remote database and either give ARAdmin an > account on the remote database or use the proper login credentials. > > · Turn on Distributed Transaction Coordinator for both the local and the > remote databases. > > · Specify the following server configuration setting in the ar.conf ( > ar.cfg) file: > > SQL-Server-Set-ANSI-Defaults: T > > This setting enables the DB-Library connection that AR System uses to use > ANSI-NULLs and ANSI warnings. There should be no impact on the performance > of the database. For more information about the ar.conf (ar.cfg) file, > see the*Configuration Guide*. > > The format for the table name is: > > LINKNAME.DATABASENAME.OWNER.TABLENAME > > ====================================================== > > > > What happens: > > 1. We try to connect to this table: > swarsdog23\inac.arsystem.dbo.INAC_SDS_DATA_PPL_People > 2. The available columns that are returned are all Integers. > 3. We try to go ahead and create the View Form anyway. > 4. When we try to save we get a save failed error 552. that references > SQL Server 102: Failure during SQL operation to the database syntax near > '\'. (SQL Server 102). > 5. The CREATE statement in the SQL Log uses the table > name: swarsdog23\inac.arsystem.dbo.INAC_SDS_DATA_PPL_People > 6. When I run straight SQL from the calling database we can execute > and return entries: SELECT * from > "swarsdog23\inac".arsystem.dbo.INAC_SDS_DATA_PPL_People > > Conclusions: > > 1. Somehow the Linked Server Name is creating a problem. > 2. We have tried "[ ]" and using double quotes in the View Table > creation wizard and this fails; therefore, we cannot alter the naming. > 3. Somehow in the CREATE statement - ARS fails to place quotes around > the LINKNAME. > 4. swarsdog23 is the name of our production database server (not the > real name, but the syntax is correct) - we cannot change this right now. > > > > Query: > > 1. Is it the name of the database server that poses the probem? OR > 2. Is this a bug? > > > > > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > ************************************************************************************************* > > > > This email is intended for the named recipient(s) only. Its contents are > confidential and may only be retained by the named recipient(s) and may > only be copied or disclosed with the consent of LCH.Clearnet Limited and/or > LCH.Clearnet SA. If you are not an intended recipient please delete this > e-mail and notify postmas...@lchclearnet.com. > > LCH.Clearnet Limited, LCH.Clearnet SA and each other member of the > LCH.Clearnet Group accept no liability, including liability for negligence, > in respect of any statement in this email. > > The contents of this email are subject to contract in all cases, and > LCH.Clearnet Limited and/or LCH.Clearnet SA makes no contractual commitment > save where confirmed by hard copy. > > Cet e-mail et toutes les pièces jointes (ci-après le "message") sont > confidentiels et établis à l'intention exclusive de ses destinataires. > Toute utilisation de ce message non conforme à sa destination, toute > diffusion ou toute publication, est interdite, sauf autorisation expresse > de LCH.Clearnet Limited et/ou LCH.Clearnet SA. Si ce message vous a été > adressé par erreur, merci de le détruire et d'en avertir immédiatement > postmas...@lchclearnet.com. > > LCH.Clearnet Limited, LCH.Clearnet SA et les autres entités du groupe > LCH.Clearnet Group, ne peuvent en aucun cas être tenues responsables au > titre de ce message à moins qu’il n’ait fait l’objet d’un contrat signé. > > LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High > Street, London EC3N 1EA. Recognised as a Clearing House under the Financial > Services & Markets Act 2000. Reg in England No.25932 > > Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.com > > LCH.Clearnet SA, Siège Social, 18 rue du Quatre Septembre, 75002 Paris, > Chambre de Compensation conformément au Code Monétaire et Financier. > > > > > ************************************************************************************************* > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
