Visit our Sponsor   Visit our Sponsor
delphi3000.com - the free delphi knowledge platform
delphi3000.com - the free delphi knowledge platform
491 Users Online NOW
Have a look at your member-status

connecting people's knowledge


  - Recent ArticlesRSS feed for Recent Articles on delphi3000.com
  - List of All Articles
  - Top Viewed Articles
  - Articles (+Attachem.)
  - Articles Of Interest
  - Categories
  - Top Uploader
  - Search
  - Index

  - My Home
  - Submit an Article
  - My Articles
  - My Personal Data
  - My Bookmarks
  - Activities
  - Login/Logout

  - Sign Up
  - Why Sign Up
  - Newsletter

  - Press
  - Advertise

  - Contact
  - Feedback





Community
Borland
ClubeDelphi
Dr. Bob
UK-BUG
Delphi Meetings
Planeta Delphi







Startblatt.de






Share this article with friendsShare this article with friends
Rate this articleRate this article - to keep the quality of delphi3000.com !
Comment this article or read through previous comments (3)


D6+ADO+MS.SS => D6+ADO+Oracle ????Go to Hans Pieters's websiteFormat this article printer-friendly!Bookmark function is only available for registered users!
Product:
Delphi all versions
Category:
DB-General
Skill Level:
Scoring:
Last Update:
01/15/2003
Search Keys:
delphi delphi3000 article borland vcl code-snippet ADO ORACLE MS-SQL-SERVER BACK-END
Times Scored:
1
Visits:
2917
Uploader: Hans Pieters
Company: IHP Software France
Reference: Ridbase.com
 
Question/Problem/Abstract:
This a question and not a solution. But read further.....
Answer:



My best selling app. runs like a fox (yes, the brown one) as Delphi 6 + ADO + MS Sql Server application. But next week I will have to install it with an Oracle back-end.
My first Oracle installation.

Who can give me some advice me what I have to do to migrate from MS Sql Server to Oracle?
I suppose adapting the udl file is not sufficient.
I heared something about table ownership and Oracle, but I hope it is not true that you have to hardcode the owner if you want to use Oracle.

I know that a part of the D3K Community will jump on me ('this is no .... etc.) but nothing is written about this on D3K and the comments and advices could be as useful then a 'normal' article.

Tx & Regards
Hans Pieters





Please rate this article!
Skill level:
BeginnerExpert

Useful:
No!Very!

Overall rating:
PoorExcellent



Comments to this article
Write a new comment
MS.SS to Oracle
    Bob Dole (Jan 15 2003 8:22PM)

Well, migrating from one to the other can either be very simple or very complicated...there are a few variables involved.  The main one being: How much MSSQL-specific features have you used in your DB.  Using things like "Auto-inc" fields in your table structure as opposed to creating your own auto-inc methodology (such as an ID: int field that gets it's next ID number from a stored proc in an INSERT trigger), or the "@@new" variable in a stored proc, will cause you to have to create an Oracle-specific version of your scripts.  To figure out what MSSQL-specific stuff you've used, you won't have much choice other than to read your scripts and look for MSSQL-specific keywords and structures.  The other option is to try running your scripts against Oracle or InterBase.  I've had the task of implementing a DB Platform-independant app, and I chose to start out with InterBase because it has the least amount of home grown features and is easier to use when trying to create generic scripts.

continued . . .
Respond

RE: MS.SS to Oracle
Bob Dole (Jan 15 2003 8:22PM)

So, lets assume you've got a SQL-92 compliant script set.  Migrating generic SQL structures to Oracle is really not that complicated.  Oracle handles table ownership the same way SQLServer does.  You create a DB owner, create your objects with that owner, and set user permissions to the objects.  I have been using Oracle for a number of years, and havn't touched SQLServer in a few, so I can't remember some of the terminology, but i would suggest just reading up on Oracle's ownership and permission rules.  There's a difference between a DB owner and a DB user.  A user in a DB named JDoe can own an object "Customers".  THat table's fully qualified name would be "JDOE.Customers".  It is then up to a DBA to specify that DB user "BSMith" has permission to log on to JDOE's database and use JDOE's objects.

It may sound complicated, but once you read over it you'll see it's just a matter of organizing your DB owners and users.

other than that, things should run pretty smoothly, as long as you have generic SQL that works in both environments.  like i said, this would include the use of keywords, structures, and datatypes.  If you've kept your design SQL-92 compliant, everything should work fine.  If you've downloaded FieldDefs in your DFM files, SQL-92 compliant fields shoudl generate the same FieldDef info.

Hope that helps out a little
Respond

MS.SS to Oracle
Hans Pieters (Jan 17 2003 8:55AM)

Tx Bob.
Hans Pieters
Respond














 
Sign up to consume product discounts for Bronze memberships !

read more


  Visit our Sponsor

 

  Community Ad of
C.A. Longen
 
   














 







     
  Copyright © 2000 - 2007 delphi3000.com - All rights reserved. Terms of use. || Privacy
delphi3000.com is a service by bluestep.com IT-Services GmbH (Vienna)