Manifold now shipping GIS product for SQL Server 2008 Spatial (Katmai)

I thought readers of this forum would be interested to know commercial products are now supporting Katmai.

Manifold Release 8 started shipping last Tuesday, 28 August 2007, to the general public with direct, native support for SQL Server 2008 (Katmai) Spatial built in.

Links...

Home page (SQL Server 2008 featured prominently):

http://www.manifold.net/

News page overview of Release 8:

http://www.manifold.net/info/news.shtml

Spatial DBMS user manual topic:

http://demo.manifold.net/doc/spatial_dbms.htm

The spatial DBMS user manual topic is long because it introduces the general ideas behind spatial DBMS for users new to this part of GIS. SQL Server 2008 users will probably want to skip right down to the "Supported Spatial DBMS" section of that topic, as well as the "Projections and Spatial DBMS" section, which discusses use of EPSG codes within Katmai data stores.

From the user manual page:

"Manifold supports SQL Server 2008 spatial today for those Microsoft employees, partners, beta testers and independent developers who have been given access to SQL Server 2008 spatial, and will continue to support SQL Server 2008 spatial when it is released to the public."

Note that Manifold Enterprise Edition ($395) is required to work with native Katmai connections and native Katmai geometry types. This is true of SQL Server 2008 as it is of the other spatial DBMS's supported by Manifold (Oracle, IBM DB2 with Spatial Extender, PostgreSQL/PostGIS). If you have the Katmai spatial CTP you don't need to get anything than the standard Release 8 production edition of Manifold. It will automatically recognize SQL Server 2008 spatial data stores upon connection using the new, dedicated SQL Server data source. For example, once you connect (you can connect to many different types of spatial DBMS at once) you can copy data from Oracle Spatial or legacy storage like ArcSDE and paste it into Katmai. The Database Console in Manifold also works with Katmai, which provides a useful way of crafting and executing queries.

By the way, we'd like to compliment the Katmai team on a job well done. We've had a lot of experience with spatial DBMS and GIS and this is clearly a world-class entry from Microsoft.

Ah, almost forgot: if you work for Microsoft, Manifold is free for you. Drop me an email and I'll arrange a free license for you.

Regards to all,

Clearing open "question".

Manifold now shipping GIS product for SQL Server 2008 Spatial (Katmai)

I thought readers of this forum would be interested to know commercial products are now supporting Katmai.

Manifold Release 8 started shipping last Tuesday, 28 August 2007, to the general public with direct, native support for SQL Server 2008 (Katmai) Spatial built in.

Links...

Home page (SQL Server 2008 featured prominently):

http://www.manifold.net/

News page overview of Release 8:

http://www.manifold.net/info/news.shtml

Spatial DBMS user manual topic:

http://demo.manifold.net/doc/spatial_dbms.htm

The spatial DBMS user manual topic is long because it introduces the general ideas behind spatial DBMS for users new to this part of GIS. SQL Server 2008 users will probably want to skip right down to the "Supported Spatial DBMS" section of that topic, as well as the "Projections and Spatial DBMS" section, which discusses use of EPSG codes within Katmai data stores.

From the user manual page:

"Manifold supports SQL Server 2008 spatial today for those Microsoft employees, partners, beta testers and independent developers who have been given access to SQL Server 2008 spatial, and will continue to support SQL Server 2008 spatial when it is released to the public."

Note that Manifold Enterprise Edition ($395) is required to work with native Katmai connections and native Katmai geometry types. This is true of SQL Server 2008 as it is of the other spatial DBMS's supported by Manifold (Oracle, IBM DB2 with Spatial Extender, PostgreSQL/PostGIS). If you have the Katmai spatial CTP you don't need to get anything than the standard Release 8 production edition of Manifold. It will automatically recognize SQL Server 2008 spatial data stores upon connection using the new, dedicated SQL Server data source. For example, once you connect (you can connect to many different types of spatial DBMS at once) you can copy data from Oracle Spatial or legacy storage like ArcSDE and paste it into Katmai. The Database Console in Manifold also works with Katmai, which provides a useful way of crafting and executing queries.

By the way, we'd like to compliment the Katmai team on a job well done. We've had a lot of experience with spatial DBMS and GIS and this is clearly a world-class entry from Microsoft.

Ah, almost forgot: if you work for Microsoft, Manifold is free for you. Drop me an email and I'll arrange a free license for you.

Regards to all,

Clearing open "question".

Managing DB updates to client DB servers

I'm looking for ideas on how to write SQL scripts for updates that are
pushed out to clients for product updates. Obviously, We could just
keep track of the changes on a pad or write a database that requires
us to input those changes and eventually hand write the update
scripts. I was wondering if anybody has any solutions that may help
automate this process.

Is there a way to write an application that will compare a current
(updated) database structure against the last realease that will give
us the fields that need to be changed?

As far as creating the scripts for the initial install, thats easy. We
can do that right from the SQL Enterprise Manager.

Call me lazy! Any ideas?

ThanksDuncan (duncan.loxton@.gmail.com) writes:
> I'm looking for ideas on how to write SQL scripts for updates that are
> pushed out to clients for product updates. Obviously, We could just
> keep track of the changes on a pad or write a database that requires
> us to input those changes and eventually hand write the update
> scripts. I was wondering if anybody has any solutions that may help
> automate this process.
> Is there a way to write an application that will compare a current
> (updated) database structure against the last realease that will give
> us the fields that need to be changed?
> As far as creating the scripts for the initial install, thats easy. We
> can do that right from the SQL Enterprise Manager.

There a couple of products on the market. SQLCompare from Red Gate does
indeed compare two databases. DBGhost likes to tout itself as being
good for this. I have not use any of them.

Whatever method, you should keep all your code under version control,
and all your update scripts should have their foundation in the
version-control system. Basically a shipment is all changes between
the label for the previous shipment and this one. With some files added,
like triggers or indexes for changed tables.

In fact, once you have a good version control system up and running,
composing your scripts manually is not daunting task - but admittedly
it becomes boring after a while. The flip side is that you learn to
understand your process.

In fact, I started in our shop with something like this many years
ago. This has now evolved to a versatile toolset that we use. It is
available as freeware for anyone who want to try, see
http://www.abaris.se/abaperls/index.html.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Management Studion Express alongside full-blown Management Studio?

Is it possible to run both Sql Server Management Studio: Express and full blown side by side?

I am developing with the full blown product but would like to test Management Studio Express on the same box.
Is this possible?

Thanks

Eric Hi !

For a full and realistic test, I would put them not on the same machine, as you can′t be sure in which way the big brother will interfer with the deployed assemblies. Just deploy it on a dedicated test machine to do your tests.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Somehow this is the kind of answer I expected...

Well, I think I'll just do that then.

Thanks

Eric