The geography data type only supports SRIDs that appear in the view sys.spatial_reference_systems. On my server, the SRID 1047 did not appear in that view so I suspect you are attempting to use a spatial reference that is incompatible with the geography data type.
Use the following query to see what SRIDs are supported:
select * from sys.spatial_reference_systems;
Bill
As long as you have gdb connections to both you will be able to use esri (catalog) tools to move data between.
You will want to double check your CRS for support in both spatial databases.
If you don't use esri tools you will have to register your data in sde.
You simply mention that oracle supports spatial without saying that your data is in oracle spatial.
There are many things to consider if your data type is spatial (SDO) and especially if you are going to mssql-spatial.
It is possible to use both databasees without using "spatial", and unless you are developing applications and or processing huge amounts of data using the sdo functions I would suggest just using the esri binary format and allowing sde to manage the "spatial".
I am sure all of this sounds very confusing unless you already have some understanding of sde.
If not you can read more here...
ESRI Resource Center.
Edit:
When You define a geodatabase in ESRI you have several choices for the rdbms. Oracle, db2, informix, mssql. among others.
SDE creates all the tables and relationships needed to maintain the data with ESRI. There are several choices for the data type for creating tables. ESRI binary is the normal default for most of these rdbms.
Care should be taken when deciding what format to utilize as access from other applications, and interfaces can be affected by this.
ESRI resources should be able to fill in the rest of the gaps.
Best Answer
You can always resort to querying the INFORMATION_SCHEMA.TABLES and COLUMNS dictionaries to find out if there are tables that are spatially enabled.