|
Hi SteveIf this is what you think where is the logic in even deploying SQL Server at all ?
Why not just use the iSeries database for everything and be done with it ?Also, by "one database" do you mean one central database or one "brand" ? Either way, one database on the iSeries would make your life a lot simpler, irrespective of your choice of programming language.
regards Evan Harris
You have a lot more practical experience than I do Joel. I am just a recent .NET school grad with a lot of big ideas! I simply dont see the point in an organization running more than one database. They all do the same thing, so settle on one and be done with it. Of course working with the remote iSeries database is a another matter. Thinking about it, your approach could provide value as a way to hide from the programmer the details that the tables could be located any place in the network. -Steve
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.