Migrating OBIEE Repfrom Oracle database to SQL server database in Solaris.

Hi,
I need inputs in how we would migrate our connections in Repository from Oracle database to SQL server database in Sloaris server.
Is there a complication here.
Regards,
Bhavik

Well that makes more sense, you probably have phrased your question better. Microsoft SQL Server Connectivity Components are not supported in any other operating system than Windows. So you will not be able to use the SQL Server native drivers to connect to your SQL Server. ODBC it's an option but there aren't many ODBC drivers for Unix systems. Luckily for you OBIEE includes the DataDirect ODBC drivers and supports using them to connect to a SQL Server. Check [the documentation|http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/e10416/general_101331.htm#sthref9] on how to use them. Having said that I would say that whoever is pushing to move your DWH to SQL Server should consider also moving OBIEE to a Windows server to be able to use the SQL Server native drivers to connect to SQL Server.
PS: No needs to post 3 times. :-)

Similar Messages

How to convert Oracle database to Sql server Database

Hi All,
I have one database made in the Oracle 8i, i want to convert that database to Sql Server Database,
Can anyone please give me the step by step process to do this conversion.
Regards
Ramesh Jha

Try using the DTS (data transformation services) services of SQL Server 2000
DTS is based on an OLE DB architecture that allows you to copy and transform data from a variety of data sources. For example: Oracle directly, using native OLE DB providers.
Alternatively, you could follow the following broad steps for data migration (assuming you are retaining the same table structures in SQL Server, and that you are talking about SQL Server 2000).
1. Get the CREATE scripts corresponding to each Oracle table / view / index. These can be reverse engineered from the database using a tool.
2. Map Oracle datatypes to SQL server datatypes e.g: date maps to datetime/smalldatetime, numeric maps to one of int, bigint, smallint, etc depending on the range of values in the CREATE scripts.
3. Indexes in SQL Server are of two types: Clustered / non-clustered. There can only be one clustered index on each table.
4. Converting procedures and triggers will have to be line by line, since SQL Server uses a proprietary T-SQL instead of ORacle's PL/SQL
I have yet to see a really good tool to do this migration, but it is possible to write a PL/SQL procedure / Pro*C program to automate the script creation for creating tables in the SQL Server database.
For the actual data import into SQL Server, export the Oracle data table by table into flat files, and then use the import wizard of SQL Server enterprise manager

What are the Basic Differences between Oracle and MS-SQL server Database?

Hello,
anybody pls Guide me about the Differences between Oracle and MS-SQL server Database.and also IBM Databases also
Regards,
Balaram

SQL Server only works on Windows-based platforms, including Windows 9x, Windows NT, Windows 2000 and Windows CE.
In comparison with SQL Server , OracleDatabase supports all known platforms, including Windows-based platforms, AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, Linux Intel, Sun Solaris and so on.
The SQL Server advantages:
SQL Server holds the top TPC-C performance and price/performance results.
SQL Server is generally accepted as easier to install, use and manage.
The Oracle Database advantages:
Oracle Database supports all known platforms, not only the Windows-based platforms.
PL/SQL is more powerful language than T-SQL.
More fine-tuning to the configuration can be done via start-up parameters.
Samrat

Migrating data from Oracle 9i to SQL Server 2005

I am new to both. I need to first migrate data from oracle to sql server. After this I need to create a daily nightly batch process to insert new records from oracle to sql server into that table.
As my knowledge in SQL server is zero. Can somebody help me how I can accomplish this.
Somebody told me that I can use sql server import/export to do initial data dump into sql server and after that I can create a link in in oracle to do new iserts for new records. does any one have some example on this. I will really apprecite this if someone can give me step by step example. Thanks

I have been to SQL Server training, but my SQL server databases are off the shelf system, so I don't have to muck with them. Anyway, Sql Server is just MS Access on steroids, so some of the same concepts apply. You need to create an external table links to oracle. The following tidbits I found by googling might help you.
http://www.sqlmag.com/Article/ArticleID/22264/sql_server_22264.html
http://www.lazydba.com/sql/1__152.html
http://www.sswug.org/see/35034
http://decipherinfosys.wordpress.com/2007/07/16/linked-servers-in-sql-server/
Some of the above require subscriptions (free and or paid). Hope this helps.

Can OBIEE 10G connect to a SQL Server database (2005)?

We have Oracle BI running already. We have also a SQL Server database running. Now there is requirement that asks to connect to the SQL Server and directly send some SQL quires to the SQL Server and get result back and display it in answers. I know the normal process should be set ETL to load the data from the SQL Server to OBIEE and from there the report can be built. So I am not sure is this doable?

Hi Srini,
These is the steps I have done:
1. open Oracle BI administration tool
2. create a new repository
3. select import from database, and specify the ODBC (connection to the SQL Server). It asked me to choose tables to import. I then selected one table. Now I can see the connection pool and the table being created in physical. I saved it.
4. I then goes to BI interactive dashboard -> answers-> Direct Database Request. In the connection pool I entered the name of the connection pool in step 3. And entered some simple query and I got:
error : Odbc driver returned an error (SQLExecDirectW).
error : State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 27022] Unresolved Connection Pool object: "asepostest_pool". (HY000)
error : SQL Issued: {call NQSGetQueryColumnInfo('EXECUTE PHYSICAL CONNECTION POOL asepostest_pool select * from branch')}
Should I modify NQSConfig.INI in C:\OracleBI\server\Config\ to make it point to my new repository? Like this?
Star
=
asepostest1.rpd, DEFAULT;
But then I couldn't restart BI server.

Converting a SQLite database to a SQL Server database

Hi
I have a SQLite database. I want to convert it to SQL Sever 2005 database. Can u pls guide me how to do it?
Imalka

Hi
There are several known tools for converting between SQLite database and SQL Server database. I id not check them all but you can get more information on each using Google, and then choose the one that fit your needs
1. Convert SQL Server DB to SQLite DB
http://www.codeproject.com/Articles/26932/Convert-SQL-Server-DB-to-SQLite-DB
Written by, liron.levi, from Israel
* Open source & free
2. SQLite Manager 0.8.1
https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/
Written by, by lazierthanthou
* This is Firefox free add-on (I ont think that they publish the source code)
3. RazorSQL
http://www.razorsql.com/index.html
4. MDB Tools project
http://mdbtools.sourceforge.net/
* Open source (LGPLv2) & Free
5. You can use SSIS to import to/from SQL Server
[Personal Site] [Blog] [Facebook]

OBIEE 11g, Informatica and DAC: Migrating from Oracle DB to SQL Server?

Hi Gurus,
Currently we are implementing OBIEE 11g with Oracle BI Application for EBS (Supply Chain, Procurement & Finance modules). We have incorporated all OUT-OF-THE-BOX mappings and configurations in DAC, Informatica and RPD (no change, only OOTB). We were using Oracle DB and Linux servers.
Now the client wants to migrate this to one Windows box.
Can anyone point out, what are the changes need to done to migrate to SQL Server database. Any existing documentation or link will be helpful.
Edited by: Sudipta Gupta on Aug 2, 2012 1:59 PM

If you are using SQL Server 2008 then you need to edit the DAC config.bat file replace sqljdbc.jar with sqljdbc4.jar.
Rest of DAC and Informatica configuration is almost similar.
Let us if you come across any issues.
Hope this helps

How to Migrate my database from SQL Server 2000 to Oracle

I want to transfer my database from SQL Server 2000 to Oracle, Can I do this without using Oracle Migration Workbench ??
Please help me.
Thanks in advance
Vicky... :-)

Do you have a good technical reason for not wanting to use the Migration Workbench?
Given that it's free and does a hell of a lot of the work for you, why wouldn't you use it?
Other than that, I would say you would be on your own...
cheers,
Anthony

Migrating from SQL Server to Oracle - Emulating SQL Server databases

I want to offer Oracle connectivity from an ADO.NET application that was developed for SQL Server. The application accesses multiple databases, each having the same schema but each storing different data that is confidential to the users of each database. I’ve been reading up on Oracle but have not yet found a way to group tables, views, etc. in a way that would emulate the ‘databases’ of SQL Server.
The application currently uses the SQL ‘CREATE DATABASE’ command to generate each database and then populates each with the appropriate tables. However, CREATE DATABASE appears to work differently with Oracle, creating a new instance rather than a new ‘internal database’. I’m wondering if CREATE TABLESPACE would give me the functionality I’m looking for, if it were subsequently possible to refer to a specific table within a specific tablespace.
I guess it comes down to whether it’s possible to access specific groups of tables, views, etc. within Oracle (e.g. Groups A, B and C, each having relational tables T1, T2 and T3, and be able to access and update data within any specific table, say, B-T2), while also being able to limit access to any of the Groups.
Would ODP.Net offer advantages over the System.Data.OracleClient for this architectural problem?
Any thoughts on how best to proceed would be most welcome. Thanks in advance for any ideas you might have.

Sorry for the delay closing-out this thread but I work from a rural location and we lost our internet service for the two-weeks prior to the holidays. Now back on-line so let's wrap-up.
Oracle and SQLServer are now both being accessed from my ADO.Net application, so a big thanks to all who've helped me with this first use of the forum. Hopefully these final comments might help someone else in turn...
In migrating from SQLServer to Oracle I initially found it hard to stop thinking about accessing multiple databases on a single dataserver and start thinking more about a single instance of a database that supports muliple users, any one of which can be assigned the same schema. While I had used the SQL CREATE command to produce miltiple databases within SQLServer, it serves a completely different purpose for Oracle, creating an entirely new instance that I did not require.
Other differences that I ran in to included Oracle utilizing 'sequences' to autoincrement identities, whereas SQLServer lets you specify the identify while creating a table (here SQLServer may simplify declaration but Oracle's approach may be more powerful, e.g. if the same identity applies across multiple tables). Also ADO.NET command parameters use an '@' prefix in SQLServer but ':' for Oracle. But by-and-large few changes were required to my SQL to get up and running with Oracle (I found the 'Oracle Database SQL Reference' useful but no substitute for logging into Oracle and just trying each string in the 'SQL Commands' area).
Clearly I'm no database expert and I've barely scratched the surface with Oracle, but after logging in through the 'Database Home Page' I've found Oracle to offer a very 'clean' and logical interface that made it easy to move around the application and get a 'feel' for its organization and what it can do before digging furhter into the documentation. The 'Object Browser' is also a great way to quickly view and edit your various tables, views, sequences, triggers, etc., and ditto your data. In short, I think I'm going to like Oracle.
Thanks again and bye for now.

Migrating SQL Server database to Oracle 8i - any known issues

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh Hi Ramesh!
The Migration Workbench does not make any modifications to the SQL Server database. It only reads information from it. Your users should be able to use the SQL Server database as usual.
Please note however that if you migrate the data over to Oracle using the Migration Workbench and your users continue to enter/update data in the exiting SQL Server database then you may need to move all that data over again in order to have the most up to date data in the Oracle database.
thanks
- Garry

Migrating Oracle Databases to SQL Server 2000

Hi friends,
I wanna to Migrating Oracle Databases to SQL Server 2000.
But i don have idea abt that.
could u plz help how to start and procced.
Neeraj Goel

Hi Neeraj,
This forum is dedicated to Migrating from SQLServer and other third party databases to Oracle.
Not the other way round.
The Oracle Migration Workbench facilitates migrations to Oracle.
Regards,
Dermot.

My Experiences re: Migrating SQL Server Database to Oracle

I am using SQL Developer EA4 for thsi conversion, best attempt yet.
I had numerous problems with this conversion.
1. The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database. I also noticed a file name "Migration.out" was produced; it contained errors such as:
Error starting at line 3 in command:
CREATE USER Emulation IDENTIFIED BY Emulation DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:3 Column:36
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 4 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM,CREATE PUBLIC SYNONYM TO Emulation
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 7 in command:
CREATE USER dbo_COREv13 IDENTIFIED BY dbo_COREv13 DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:7 Column:38
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 8 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM TO dbo_COREv13
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges".
I followed all of the steps listed in the "Help" section re: Migrations but still ended up with these errors.
2. My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
3. While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
4. Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
5. A log of all activities should be produced for review and completeness.
6. I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
7. I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
I dont want to appear negative on this Migration; I have used SQL Developer since it inception; in my opinion this is the best attempt to date.
Murray Sobol

Hi Murray,
Thanks for this feedback.
There is a lot of questions here, I think some of it boils down to misunderstandings, which we should clarify in the doc.
Hopefully Ill get a video of a migration online soon as well.
But here is a brief break down.
*1.*
"The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database."
So this relates to Step 7 of the Migration Wizard. Where you can select the target connection.
SQL Developer doesn't ignore the Target Connection you selected, It just uses it to connect to the target database , not the target schema.
SQL Developer generates a new target schema for the migrated objects. It standard approach is not to generate objects directly into an existing Schema.
The Target Connection is used to create all the migrated objects (including new Oracle Schemas) in your target oracle database. So you should choose an Oracle Target Connection which has enough privileges to create new Schemas and Objects.
But as you have found, it doesn't generate the migrate objects , like tables, ... , directly into your chosen Target Connection.
From the errors you encountered it doesn't sound like the Target Connection (and the underling Oracle Schema) doesn't have the privileges to create other Schemas.
If you use something like a connection to the SYSTEM schema on your target database, it should run OK.
It wont create any objects in SYSTEM, rather it will use SYSTEM privileges to create a new schema (ex: dbo_Northwind) and populate it.
You don't have to use SYSTEM, but you do need a schema with enough privileges to create other schemas.
That is the straight forward way. But if you really need to generate into an existing schema the following steps can be taken.
a)rename the schema under the Converted Database Objects
b)Right click "Converted Databases Objects" and choose generate. it will kick off the Migration Wizard in the correct place
*2.*
My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
When you say Migration.sql , is the entire generation file , which can be found in your <outputspecified>/generated/<projectname.modelname>.sql ?
When your say "pasted it into the new Oracle database" , are you running it in SQL Developers SQL Worksheet using the Target Connection.
Basically your migration is all out of shape once the target Schemas are not created. So the above issues (insufficient privileges) has to be resolved first.
Please post back if it is still an issue.
*3.*
While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
Objects are converted in a particular order and their dependencies are persisted so that they can be generated in the correct order.
Are you seeing an issue?
*4.*
Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
I'm surprised any tables were populated with data due to the target schema not being created.
The online data move is pretty simple and it does not report or recover very well from issues.
If you are having difficulties once item 1. is resolved, please post an example of the source table and I will give it a go.
For better control of the data move with much more powerful tweaking, error handling, reporting and performance try the offline data move.
SQL Developer can created a suite of scripts which use SQL Servers BCP tool to dump out the data to dat files, and Oracle SQL*Loader tool to insert the data in the dat file into Oracle.
*5.*
A log of all activities should be produced for review and completeness.
The output/generated/<projectname.modelname>.out provides the output of running the generation script.
The migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html outline what happens during the migration.
Apart from online data move issues, is there any other data missing?
*6.*
I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
Do you mean "Copy To Oracle" ? This option is intended to migrate tables from non Oracle databases like SQL Server to Oracle.
Can you give more details on what issue you are seeing.
*7.*
I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
The generation script is meant to be run using SQL Developers SQL Worksheet. I think you only get this "instance name" issue if running from SQL*Plus.
Can you confirm
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
The online data move is performed separately from creating the objects. It is not script based, it uses JDBC to pump the data from the source database to the target database.
In summary , I would
a) Create a connection to your Target database using your SYSTEM schema
b) Right click on your "Converted Database Objects" and choose "Generate Target"
c) Choose your new "System" connection as the Target Connection
d) Follow the Migration Wizard to the end.
You will end up with a new target Schema and the migrated objects in it.
Check the .out file to see the errors
and the migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html
Regards,
Dermot
SQL Developer Team.

Quick Migrate: SQL Server database to Oracle

When I try Quick Migrate: SQL Server database to Oracle, I get the following error messages:
1. Locating source plugin...failed
2. Checking multi-schema privileges...Privilege 'CREATE ROLE" is not granted with admin option.
Error #1 I do not understand.
Error #2: I created the user as follows:
DROP USER GRAINTEST CASCADE
CREATE USER GRAINTEST
IDENTIFIED BY SQL
DEFAULT TABLESPACE SMARTSOFT_DATA
TEMPORARY TABLESPACE TEMP
QUOTA UNLIMITED ON SMARTSOFT_DATA
QUOTA UNLIMITED ON SMARTSOFT_INDEX
GRANT CONNECT,
RESOURCE,
CREATE ROLE,
CREATE VIEW,
CREATE SESSION,
ALTER ANY TRIGGER TO GRAINTEST
DROP ROLE R_GRAINTST
CREATE ROLE R_GRAINTST NOT IDENTIFIED
GRANT R_GRAINTST TO GRAINTEST
WITH ADMIN OPTION
Thanks
Murray

Murray,
Apologies for referring to the 1.5 documentation but the 2.1 documentation still has the same information about creating a user to hold the repository.
You initially reported 2 problems -
1. Locating source plugin...failed
2. Checking multi-schema privileges...Privilege 'CREATE ROLE" is not granted with admin option.
For the first error have you installed the necessary JDBC driver ? I have just installed SQL*Developer 2.1 on a new laptop and could successfully connect following the documentation steps -
Oracle® SQL Developer
User’s Guide
Release 2.1
2.5.2 Before Migrating From Microsoft SQL Server or Sybase Adaptive Server
To configure a Microsoft SQL Server or Sybase Adaptive Server database for
migration:
1. Ensure that the source database is accessible by the Microsoft SQL Server or
Sybase Adaptive Server user that is used by SQL Developer for the source
connection. This user must be able to see any objects to be captured in the
Microsoft SQL Server or Sybase Adaptive Server database; objects that the user
cannot see are not captured. For example, if the user can execute a stored
procedure but does not have sufficient privileges to see the source code, the stored
procedure cannot be captured.
2. Ensure that you can connect to the Microsoft SQL Server or Sybase Adaptive
Server database from the system where you have installed SQL Developer.
3. Ensure that you have downloaded the JTDS JDBC driver from
http://jtds.sourceforge.net/.
4. In SQL Developer, if you have not already installed the JTDS driver using Check
for Updates (on the Help menu), do the following:
a. Click Tools, then Preferences, then Database, then Third Party JDBC Drivers.
b. Click Add Entry.
c. Select the jar file for the JTDS driver you downloaded from
http://jtds.sourceforge.net/.
d. Click OK.
========
The second error is again documented in the 2.1 documentation -
5.99 Privilege Warning for Migration
This dialog box is displayed if you click Verify in the Quick Migrate box and the
database user for the connection does not have all privileges necessary for a
multischema migration. For multischema migrations, this user must granted the
RESOURCE role with the ADMIN option; and this user must also be granted the
CREATE ROLE, CREATE USER, and ALTER ANY TRIGGER privileges, all with the
ADMIN option.
If you are performing a single-schema migration, you can ignore this warning.
=====
Which errors are you now seeing and which user was used to hold the repository ?
If you are using GRAINTEST for the repository then create it using this syntax -
CREATE USER GRAINTEST IDENTIFIED BY password <=== change password as necessary
DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp; <=== change tablespaces as necessary
GRANT CONNECT, RESOURCE, CREATE VIEW, CREATE PUBLIC SYNONYM TO
GRAINTEST WITH ADMIN OPTION;
GRANT ALTER ANY ROLE, ALTER ANY SEQUENCE, ALTER ANY TABLE, ALTER TABLESPACE,
ALTER ANY TRIGGER, COMMENT ANY TABLE, CREATE ANY SEQUENCE, CREATE ANY TABLE,
CREATE ANY TRIGGER, CREATE ROLE, CREATE TABLESPACE, CREATE USER, DROP ANY
SEQUENCE, DROP ANY TABLE, DROP ANY TRIGGER, DROP TABLESPACE, DROP USER, DROP ANY
ROLE, GRANT ANY ROLE, INSERT ANY TABLE, SELECT ANY TABLE, UPDATE ANY TABLE TO
GRAINTEST with admin option ;
then when making the migration make sure the Oracle connection is to this user.
Please update the thread with the errors you get after following these steps.
Regards,
Mike

Convert varchar to date in OBIEE-sql server database

Hi we have SQL server database,
and we need to convert varchar to to_date .
In OBIEE we use evaluate,cast etc on Oracle......Not sure about sql server..please help

i am usiing below formula in my reports-answer side:
Cast((case when "Job CV Fact"."Total Cv Sent" is not null then "DATE DIM".Date end)as Date)
below error is coming:
A general error has occurred. [nQSError: 46046] Datetime value 01/01/08 does not match the specified format. (HY000)
cast("DATE DIM".Date as date) the above error comes :)

Converting Access application after migrating SQL Server database

I have used migration workbench to migrate an access database and application. I now have sql server databases with access applications that need to be migrated. How can I convert the access applications that currently use sql server as a database? I don't see that migration workbench considers this combination.

If you have and Access/SQL Server combination. then download the SQL server plugin appropriate to your version of SQL server. Go ahead and migrate the SQL Server database to Oracle. Once this is done, then update your access application so your link tables point to your newly migrated Oracle database.
Donal

Migrating OBIEE Repfrom Oracle database to SQL server database in Solaris.

Similar Messages

Maybe you are looking for