Đang tải dữ liệu ...
Trang chủ
Kinh Doanh Hà Nội 1
live:70ecda23a35b5e1e
Kinh Doanh Hà Nội 2
live:70ecda23a35b5e1e
Kinh Doanh HCM 1
live:70ecda23a35b5e1e
Kinh Doanh HCM 2
thu.hien968
Hỗ Trợ Kỹ Thuật 1
vinhbkhutskype
Hỗ Trợ Kỹ Thuật 2
vinhbkhutskype

SpatialWare for SQL Server

I have been doing some thinking about the future of Spatialware for SQL server 2008, now that Microsoft are moving into the spatial database realm. I use PB MapInfo Pro as the client and store all my geometries in SQL server running Spatialware and for the most part, this is quite adequate. What I would really like is a truely client independent implementation, using the native database geometry on the backend, allowing me to use what ever client GIS on the front end.
Giá: Liên hệ
Nhà sản xuất: Pitney Bowes Software Ltd
Kho hàng: Có hàng
Lượt xem: 1.178
Chia sẻ:
Tính năng
Yêu cầu hệ thống
Download
Sản phẩm liên quan
At the moment, I can do this to a certain extent using Spatialware, and transforming the geometry in WKT/WKB which many other client applications can read. Now as we move to SQL server 2008, will PB MapInfo Pro support the native Microsoft geometries? If they do, why would they continue to support Spatialware for SQLserver, as I would imagine that everything that is in Spatialware would be rolled into SQLserver 2008. So I suppose this leads me on to thinking why would PB MapInfo support the new Microsoft geometries if it means that Spatialware becomes effectively useless? All this leads to me thinking that PB MapInfo will not support the Microsoft geometries. Anyone else got ideas on this? Perhaps they could see more markets opening up by supporting the Microsoft geometries, so they may well support it? I put the question of whether Spatialware was going to be supported on SQL Server 2008 to a sales rep here in Australia and they came back that it was. Is it going to run side by side with SQL server 2008? Are the two types of geometry going to be able to convert to each other?
Chưa có hoặc chưa được cập nhật!
Total load time (116.118.48.94) : 0.07009s