Connecting to SQL Server 2014 - 64 Bit

Am using ETL Professional 5.7.9.43
Windows 7 Professional 64 Bit
SQL Server 2014 Development 64 Bit

Office 365 2013 Professional - 64 Bit

Connections both Read & Write to Excel and Access 2013 work just fine.

First time connecting to SQL Server so I figure I must be missing a step. Using the AdventureWorks 2014 Multidimensional Database as a test. Also tried a Tabular instance without success, but figured that might not be supported yet.

Anyhow, I can connect to the database and select a table then the program will freeze.

Charlie

Our software is 32 bit so you need to install 32 bit client for sql server otherherwise it will use sql server 2000 client
sql server 2008 is usually enough.

Do not use (local) as server name use actual server name.

Also have you enabled remote connections?

Peter:

Thanks for the response. I decided to reinstall SQL Server 2014 Development with 32 bit. I was having additional issues with deploying projects within Visual Studio 2013 to SQL server due to the 64 bit install. It would only work with the 64 bit MS Database Engine (why it even needed the database engine is strange in of itself)which wasn't compatible with Advanced ETL since my transformation which wrote to MS Access, despite being 64, bit would not work. I thought I was close when I found a tread regarding having two installs of the database engine, one normal and the other passive, but I couldn't get that to work.

I downgraded to Visual Studio 2012 32 bit which can now deploy to SQL Server and all of my transformations which write to MS Access also work using the 32 bit 2010 Database Engine.

Unfortunately I still can't get the reader to work on SQL Server. It still freezes at the same spot.

I think I have done everything to enable remote connections. Again, I'm new to SQL Server.

I went to DComcnfg.exe and provided all of the rights for SQL Server Integration Services. All are apparently turned off by default.

Also:

1.Ran SQL Server Configuration Manager.
2.Went to SQL Server Network Configuration > Protocols for the Server Instance
3.Made sure TCP/IP was enabled.

Then:
1.Right-clicked on TCP/IP and selected Properties.
2.Verified that, under IP2, the IP Address was set to the computer's IP address on the local subnet.
3.Scrolled down to IPAll.
4.Made sure that TCP Dynamic Ports was blank
5.Made sure that TCP Port was set to 1433

Looked on your website to search for other suggestions.

Since the application freezes, nothing gets recorded in the log files that I have been able to see to get any clues.

Charlie

Peter:

Forgot to mention that I removed the "local" reference of the server name and provided the actual name.

Charlie

We are happy to connect remotely and assist

Mike

Remote Connections