Hi,

I am trying to migrate my SQL Server database (contains tables, views and stored procedures) using the Oracle migration workbench. I am having a few problems and I am wondering if someone has any suggestions for me.

- It failed to import some tables with date columns. The message is "table contains date column. Milliseconds not migrated. How can I resolve this error?

- Also, all the tables are encapsulated in the "SA" Schema. Now, all my imported views fail to complie because I think they need "SA"."<TableName>" whenever it accesses any table. How can I work round this?

Thanks,

Pankaj

The millisecond error may not be resolvable. A DATE column in SQL Server contains millisecond data, a DATE column in Oracle does not. If you really need the millisecond data, and you are on Oracle 9i or later, I would expect that Oracle Migration Workbench would try to insert the data into a TIMESTAMP column.

Are the views also in the SA schema?

Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Hi again Justin,

Man, you are an Oracle superhero! :) Newbies like me would be totally lost without invaluable guidance from people like you.

Well, I checked the migration wizard puts the SQL server datetime field to an Oracle 'Date' field. Do you think changing it to TimeStamp will be better?

Thanks again,
Pankaj

If
- you need the millisecond precision
- you can change the default mapping
- you are migrating to Oracle 9i or later

yes, go to a TIMESTAMP. Honestly, I haven't use the Migration Workbench in a couple of years, so I don't recall how much control you have over the mappings.

Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

I tried the TimeStamp and it works all right. Thanx man! If you are ever in Munich, the beers are on me :D

Pankaj