1

I'm trying to connect a local SQL Server database to an ETL utility called Pentaho. Pentaho very easily connects to full versions of SQL server without issue.

I've set mixed mode authentication and created a sql server account for the sql server express instance that can be used to login through SSMS.

When I try to log in via Pentaho, I get errors about it not knowing what the server is, or the server not responding. I've tried {localhost, myip, localhost\SQLEXPRESS, myip\SQLEXPRESS, just SQLEXPRESS} as the server name (and SQLEXPRESS is the instance name).

I know I've had trouble connecting other programs to SQLEXPRESS databases in the past. Can someone tell me why it acts different than when using a full install of SQL Server and how I can get around these differences?

John Humphreys
  • 37,047
  • 37
  • 155
  • 255
  • If SQL Server Express is on a different server, have you enabled TCP/IP protocol? – Diego Aug 14 '12 at 13:18
  • Toss it up as an answer, I'll check and accept if that's the problem :) – John Humphreys Aug 14 '12 at 13:38
  • Check it first, I wrote it as a comment as it's one of these "WTF facepalms" that happen to me all the time. Like read only attributes, basic permissions and stuff like that. – Diego Aug 14 '12 at 13:39
  • Yup, that was it. Sorry it took so long I was in a meeting :p It threw me off because I could connect from SSMS using "localhost" but I couldn't connect using JDBC from another program using it. I guess it did some Microsoft magic in SSMS :) – John Humphreys Aug 14 '12 at 15:23
  • Not at all. You can connect locally because it uses Shared Memory protocol, therefore TCP/IP is not needed. :) – Diego Aug 14 '12 at 16:16
  • I added the answer, as you asked. :) – Diego Aug 14 '12 at 18:53

1 Answers1

1

If SQL Server Express is on a different server, have you enabled TCP/IP protocol?

Diego
  • 7,312
  • 5
  • 31
  • 38