Infrastructure Map Server General Discussion

Active Member
Posts: 10
Registered: ‎06-15-2009
Message 1 of 5 (205 Views)

SQL 2008

205 Views, 4 Replies
01-19-2010 11:55 AM
What SQL 2008 certain patch level does Mapaguide Enterprise 2010 require?
Is there a specific Service Pack and Cumulative Update level required for SQL 2008?

We've install Microsoft SQL Server 2008 (RTM) - 10.0.1600.22

This translates into the unpatched Release-To-Manufacturing version of SQL Server 2008.
Valued Mentor
Posts: 273
Registered: ‎10-06-2008
Message 2 of 5 (205 Views)

Re: SQL 2008

01-20-2010 03:08 AM in reply to: KenCheng9054
RTM, SP1 and anything in between should work fine

- Jackie
Active Member
Posts: 10
Registered: ‎06-15-2009
Message 3 of 5 (205 Views)

Re: SQL 2008

02-01-2010 11:18 AM in reply to: KenCheng9054
I've been joining SDF3 files and SQL 2008 tables using Mapguide Studio with mixed results. The joins are not stable. I get a successful "test connection" with my SQL 2008 tables. I can see all the tables but fails on the SDF3<->SQL 2008 table joins. I made both joining fields integers with mixed results.

I made the joins using the FDO ODBC provider ... trying both connection types "database" and "DNS connections".

So my questions is three fold;

1) Who has made Mapguide 2010 and SLQ 2008 table joins successfully?
2) how many joins have you made?
3) and are you using mapguide 2010 in a production enviornment?
Active Member
Posts: 10
Registered: ‎06-15-2009
Message 4 of 5 (205 Views)

Re: SQL 2008

02-03-2010 11:31 AM in reply to: KenCheng9054
Active Member
Posts: 7
Registered: ‎11-18-2009
Message 5 of 5 (205 Views)

Re: SQL 2008

02-26-2010 02:35 PM in reply to: KenCheng9054
Hi Ken:

How are you doing? Sounds like you're experiencing similar frustrations to what I'm facing. From what I've been able to discover, the SQL 2008 Spatial FDO provider does not support SQL Views that are made by joining tables in SQL and it does not support Feature Joins created in Studio on SQL data connections.

I've updated the Autodesk SQL 2008 Spatial FDO provider with the latest OSGEO release. It solved some other issues with SQL 2008 data (namely MGE not recognizing UniqueIdentifier data types), but still no luck on the joins.

Here's an OSGEO post that might provide some clues. I haven't had time to go through it entirely yet, but I'm hoping that we may be able to come up with a workaround from some of this info.

At present, what we are doing is creating a new table that joins data from the required tables in SQL Server, creating a stored procedure that updates the new table on a regular basis (almost live) and then using that table in MGE.

Let me know if you come up with any solutions.

George Gaeke
Global CADD Systems Inc.

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Are you familiar with the Autodesk Expert Elites? The Expert Elite program is made up of customers that help other customers by sharing knowledge and exemplifying an engaging style of collaboration. To learn more, please visit our Expert Elite website.

Need installation help?

Start with some of our most frequented solutions to get help installing your software.

Ask the Community