import from Excel to ArcSDE

[KiranShakya]

I have a strange problem.  I received a geo-Database in a excel file, it seems that they have gone to SQL server, copied the rows from there and pasted it into Excel sheet.
The excel sheet has all the attributes and the SHAPE geometry (binary).

Now the problem is how to push it back (import) to my ArcSDE.  The source is in Excel file.

All the help and support is appreciated and thank you in advance

Kiran

[VinceAngelo]

While it may not be impossible, reconstituting this data will require more information than
you currently have (and probably several weeks of work).  If you need to go back to the
provider anyway, it's probably easiest to ask that they provide the data in a specific format
(file geodatabase, ArcSDE shpexport, shapefile, XML, even ASCII).  Make sure you talk to
the GIS people, not a database admin who is clueless about spatial data formats.

- V

[JohnWall]

I am in a similar situation. However, the data that I have been provided is all tabular in nature (lacks the spatial attribute). I am wanting to join this tabular data to spatial data which already exists within an ArcSDE geodatabase. Are there any issues that I might encounter when doing this and can I delete the imported tables from ArcCatalog if I find out that tables are not what I want/need? Prior training told me that exporting tables from an ArcSDE via ArcCatalog is a bad idea.

[VinceAngelo]

I've been joining tabular and spatial data for 25 years now, and I still encounter challenges
with every new dataset, so yes there are likely to be issues, but it's difficult to predict what
they may be.

I'm confused as to what you might fear about deleting unneeded data with Catalog.  As long
as you drop the tables using the highest level of registration (ArcGIS to delete tables registered
with the geodatabase, ArcGIS or ArcSDE to delete tables registered with ArcSDE, and ArcGIS,
ArcSDE, or SQL to drop unregistered tables), you're unlikely to corrupt your ArcSDE geodatabase.

I don't use ArcCatalog all that often, but when I do, it's usually to export data from ArcSDE;
I don't understand how this could be a bad idea.

- V