Creating a spatial context with a dot (.) in the name makes it un-destroyable

[jng]

If you create a spatial context in SQL Server whose name contains a dot (.) character, it cannot be destroyed later on through the equivalent FDO command.

I suspect this is the same class of issues with this provider when dealing with objects with dots in their names (such as #930)