Is there anyone have tried to connect to SQL Server 2008 r2 by using Map 3D 2012? I can't to make it. It prompts the message "Invalid connection". I used the IP as the service name of map 3d.
I connect OK to SQL express 2008 OK, using the server name as the Service Name.
Note: The SQL Server is running on the same workstation as Map3D/Civil3d 2012 version.
You should check if SQL Server has been configured to allow remote connections.
I believe by default this is not the case.
Do you know of a FDO provider for or through SQL Server Express?
The SQL Server Express connection works for me ArcGIS 10, but is not available to me within Civil 3d (FDO).
Any thoughts would be appreciated.
I am running Civil 3d 2012, 64bit, Win7, 8GB.
SQL Express should work with Civil 3D 2012. I just tried it for my first time the other day and it was pretty easy. Just use SQL Server connection. FDO actually works better than any of the options I've used with ArcMap. Pretty impressive actually.
The company I work for has SQL Server 2008. I want to connect to it but they won't let me. I set up a SQL Express at home and it's working fine. However, I want to connect to my server at home from work. Has anyone here remotely connected to SQL Express? It's super easy with Postgres but that's not what my company is using. I'm trying to prove a point with IT because they don't think I can connect to spatial data on SQL Server.
Do you use ODBC FDO connections to connect to non-spatial tables? I haven't messed with that too much but I did notice that they are grayed out when connecting to the spatial ones. I would like to perform a join of a spatial table and normal table that are stored within SQL Server. I'll probably try it out tonight ODBC.
Unfortunately, doing a join in AutoCAD is a slow go so I try to keep everything on the SQL Server. The biggest pain is the way the tables get setup when creating them on a SQL Spatial Server you cannot look at SQL Views spatially.
Why would you not just the SQL Server connection instead of ODBC? It is what I use because ODBC on 64bit seems to be more trouble than it's worth.
The SQL connection doesn't have Window Authentication. I had to set up SQL for Database Authentication. It worked fine after that.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!