Author Topic: EA on SQL Server 2012? (Read 4524 times)

chintsys · « **on:** January 11, 2013, 05:21:05 pm »

Has anyone been able to successfully host a EA database on MS SQL Server 2012 and get it to work? Are the SQL setup scripts different than those for MS SQL Server 2008?

Geert Bellekens · « **Reply #1 on:** January 11, 2013, 06:39:05 pm »

Yes, we have ours on SQL Server 2012 and we used the scripts for 2008 to create the initial databases.

Geert

jdoran-anglo · « **Reply #2 on:** January 15, 2013, 11:12:29 am »

Thanks Geert. I am getting stuck at what should be the most trivial stage.

I keep on getting the error: "Invalid data source... check configuration"

I am attempting to host the DB on the Azure platform. I have run the initial database script to make the tables, and it gives the error. I have also tried creating the suggested clustered indexes in the thread below, still errors.

A bit lost...

http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1326934114/0#5

Geert Bellekens · « **Reply #3 on:** January 15, 2013, 03:09:33 pm »

you better try Sparx support then.

Geert

wdchilders · « **Reply #4 on:** January 16, 2013, 02:35:09 am »

Yes, we upgraded from 2008 but we had to change how we connect to the database. I'm not sure if its different defaults in SQL Server but the settings and drivers we were using did not work with our 2012 dbms. We consulted with our DBA's and adjusted our data source definitions accordingly.

wdchilders · « **Reply #5 on:** January 16, 2013, 02:48:12 am »

More info. Our DBA's provided us with a string that identified the database and port. In EA we selected "connect to server". We chose OLE DB Driver for SQL Server. In the next panel we entered the string, the userid and password (allow saved password) and then selected the repository name from the drop down of database names. Pushed "test connection" and everything was good. With SQL Server 2008 and before our ODBC connection required a number of distinct entries - DNS name, database instance name, etc. That no longer works.

jdoran-anglo · « **Reply #6 on:** January 16, 2013, 11:23:31 am »

Thanks for the replies everyone. I ended up getting it working. Through trial and error, I eventually narrowed it down to it being an ODBC driver problem.

Out of the three SQL ODBC drivers, only the "Microsoft OLE DB Provider for SQL" worked.

Not sure if this is purely because the DB is hosted in the Azure platform.

Sparx Systems Forum

News: