It is highly recommended that you upgrade your version of UniVerse before you consider what interface to use.
An ODBC interface is mostly the easiest to implemented, but the slowest and hardest to debug. Especially on such an old version of UniVerse. Further, unless you're UV data is in a format readily or easily translatable/accessible from SQL Server - then you'll be forced to use intermediary tables to "bridge" the updates. Imagine the worst-case scenario where your live UV database is irreversibly corrupted by erroneous SQL Server UPDATE statement(s). A potential work-around would be the use of UV/BASIC subroutine(s) invoked as a stored procedure from SQL Server to translate the underlying complexities of your UV database/application. Hence, helping to manage this risk of corruption (to an extent) and also potentially negating the need for multiple and complex SQL queries and update statements (potentially aiding performance). You don't mention the nature of the processing model. So you'll also need to also carefully consider the potential database lock contention issues and the impact of updates (esp. bulk updates) or queries on the performance of your UV system...should have a system that is already heavily utilised or has performance or reliability issues. Regards, David -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Castilletti Sent: Monday, 17 August 2009 11:47 PM To: [email protected] Subject: [U2] Connecting to a Universe Database New project requirement to Connect to and Update the Universe Database from an external system. We will also need to Connect to and Update an external system (possibly SQL Server 2005) from the Universe System. We are currently using Universe 9.6... . What are the best methods/technologies that I should consider and those that I should avoid. Thanks in Advance for any feedback on this subject. John Castilletti ************** IMPORTANT MESSAGE ***************************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ************************************************************** _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
