Mixing spatial references in same SDE DB?

[grahamcooke]

Hi,

Quick question for an SDE expert to help me with please? Is there a "recommended way" to handle raster data that has different spatial references? We have a lot of OS Mapping (British national grid) but we also look after some training areas in Northern Ireland and Germany which obviously have different spatial referencing. As it is all training map data, the obvious thing - to me at least - is to store it all in the same SDE Db and schema. But i'm wondering if the different spatial referencing of the mapping makes this a no-no?

If it is not advisable what is the preferred way? Put it in a different schema? Put it in a different SDE Db altogether?

We are using Version 10, SP3. SqlServer 2008 backend on Windows Server 2008.

Hope someone can advise!

thanks,

Graham

[VinceAngelo]

There's nothing inherently wrong about using different spatial references for data over different areas.
It certainly won't harm ArcSDE functionality, yet it may confuse clients if the data owned by a single
user is in different projections.  There are two easy ways to address this:
1) Use different owners for different projections (different databases is an option, but only if the volume
of data warrants the overhead of multiple services)
2) Prefix or suffix the table name with the projection
Either way, Desktop is going to let you know if you try merging data in different projections in a single view.

- V