T-SQL: is there a way to force conformance to ANSI SQL?

We are planning on writing a load process that uses SSIS and loads a SQL 2008 database. Transformations may be done in the packages or in stored procedures that are called from a package or directly from our job scheduler.

What can we do now while in planning stage to minimize the impact should we have to migrate the app to Oracle in teh future?

I picture the SSIS packages could be changed to use a different provider.

What about the SQL that we use?

Q: Is there a way to put, for 开发者_如何学Pythonexample, a stored procedure in "ANSI mode" for lack of a better term to ensure that only standard SQL is used within to increase our chances that the SQL will migrate to Oracle?

One thing you can do is SET FIPSFLAGGER FULL etc. More info here: http://msdn.microsoft.com/en-us/library/ms189781.aspx

I am not aware of any ANSI Standard for RDBMS programming languages. And the constructs between TSQL and PL/SQL are quite different.

But can you use the Common Runtime Environment (I think that's what its called) in SQL Server to run JAVA? If you can, and given that Oracle can run JA VA this might offer a pathway to what you want to acheive.