Sql-server – SQLServer – need to access an ACT! database for data migration

sql serversql-server-2005ssms

I'm looking for a way to access data in an ACT! database for a data migration to a custom application.

The ACT! software uses SQLServer 2005.

The data conversion script and new application will be written on a Linux system using Python and Postgresql.

My problem is getting my hands on the data !

I don't know how ACT! has their SQLServer installation configured.

Initially I installed Microsoft SQL Server Management Studio Express to see if I could view and query the data.

I currently have …

  • Windows XP machine
  • ACT! 2009 version 11.0.0.367
  • Microsoft SQL Server Management Studio Express version 9.00.2047.00

There are two instances of the SQLServer running. One for the ACT! software and one that was loaded with the Studio Express installation.

In Studio Express I can connect to the latter instance but not to the SQLServer for the ACT! database.

Using the Windows Authentication login I get Login failed for user ... Error 18456.

I don't know what the SQL Server Authentication login would be.

  • Is there a way around the connection/login issue ?

  • Can the second instance of SQLServer be configured to see the ACT! database ?

  • Copy the database files … ?

Best Answer

We have a Customer who has the unfortunate need to use this program.

Sage purposefully makes it difficult to get to your data because they see that as a "revenue opportunity". (I guess they want to have all of the "lock-in" power of a proprietary file format combined with all of the convenience and performance of using SQL Server 2005...)

Read your license agreement. Sage demands you pay them additional fees to get access to the data. Legally, your only way of accessing your data directly is via their "licensed" means. (It's completely bogus, and makes me think of Sage software as a bunch of dirty, underhanded jerks, personally.)

They do some mean things to make sure that you can't get and keep "sa" privilege to the database easily, but since you physically control the box you can get around that.

I'm not sure how much I should say on here for fear of getting Server Fault into trouble and / or getting a cease-and-desist order myself. Suffice it to say there's a mode that you can start SQL Server in that allows "sa" access regardless of credentials. That's your back door to get in.

Sage: You're a bunch of bozos and your business model sucks re: ACT!. I hope that free and open-source and cloud-based alternatives drive you out of business.

Related Topic