T-SQL: is there any way to enforce ANSI SQL?

We plan to write a boot process that uses SSIS and loads the SQL 2008 database. Conversions can be performed in batches or in stored procedures called from a batch or directly from our task scheduler.

What can we do now, while at the planning stage, to minimize the impact, do we need to transfer the application to Oracle in the future?

I see that SSIS packages can be modified to use a different provider.

What about the SQL we use?

Q: Is there a way to put, for example, a stored procedure in "ANSI" mode due to the lack of a better term, to ensure that only standard SQL is used internally to increase our chances that SQL will migrate to Oracle?

+5
source share
2 answers

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

+3
source

I do not know any ANSI standard for RDBMS programming languages. And the constructs between TSQL and PL / SQL are completely different.

Common Runtime Environment ( , ) SQL Server JAVA? , , , Oracle JA VA, , .

0

All Articles