I want to make a connection between database sql server and pentaho user console. Before this I use MS SQL Server 2000. However, I can't make a connection. I also use 1433 as port number for this sql server but when I try to make a connection to Pentaho, I realize that it cannot detect port number 1433. What version of SQL Server I should use? Where I can find a good tutorial to do this connection. For everyone information, my database sql server is in 'VBOX' and pentaho is in local network.
You can use SQL Server 2000. But don't use driver from microsoft. You must use driver from http://jtds.sourceforge.net/. For detail information about this driver, read the following article : http://www.dbvis.com/doc/microsoft-sql-server-database-drivers/
Related
I'm having trouble connecting to a SQL Server 2008 R2 data source using Excel 2013 Power Query.
I have created a new Power Query query, and created a new SQL Server datasource. I have specified the server name and database, but have not specified any specific query.
I am using SQL Server authentication to login to the database, and the connection is encrypted.
When I attempt to set up the connection in Excel Power Query, I get an error message: DataSource.Error:
No further error details are supplied.
I have checked that the SQL Server allows remote connections, and I have tested the SQL Login by using the sqlcmd utility to connect to the database server and database and run a basic SELECT query.
If anyone can shed any light on what I'm doing wrong, I'd be very grateful.
For anyone reading this in 2017:
If you are using Windows 7 and above, use the driver listed in the ODBC Data Sources. The only case where I had to install a client and driver, was when I wanted to connect to an oracle database.
To setup and connect to SQL server, I opened ODBC Data Sources, selected 'Add', chose the SQL server option (not native client versions) and added the server and database details where prompted. Then test the connection from ODBC data sources.
My SQL server connections usually require full TNS info all the way from server name, then database name despite the claim that it's optional.
Do you have the odbc driver?
I have run into this problem previously when I tried to connect remotely.
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?
If SQL Server Express is on a different server, have you enabled TCP/IP protocol?
I have a server machine and four client machine for database connectivity.
I installed sqlexpress 2008 in server and one machine and all remaining systems, they have connected the database through the EMS (SQL Manager 2008 for SQL Server ).
The issue is that when I connect the database from that m/c which has sqlexpress 2008 then it gives "Timeout Expired"
But all remaining systems connect to server easily.
Why it gives an error for that particular system.
I didn't get any proper solution for this issue.
It depends on what do you use to connect: Windows integrated security or SQL Server security?
And also, make sure you are connecting to the right instance of SQL Server on server machine (default instance doesn't need to specify the instance name, while for named instances you need to connect to \\
Hope this helps,
Bye
cghersi
I just upgraded to a Windows 7 box and installed MS SQL Server 2005 and am trying to open and connect to my local machine using Windows Authentication.
I keep getting 'Cannot connect to CHRISW7O980'. Do I have to start a server locally?
Suggest using this fantastic ServerFault answer to a similar question to help troubleshoot connectivity issues to new instances of SQL Server. There are a few configuration points to check.
Some likely culprits:
W7 firewall allowing SQL Server traffic on 1433.
SQL Server services running?
SQL Server Configuration Manager not allowing TCP connections.
SQL Server Can't Connect
Check in Sql Server Configuration Manager to ensure your instance of SQL Server is running. If not, you can start it and set the Start Mode to Automatic to automatically start it when windows reboots.
Maybe you are running SQLExpress? Try this for the instance name:
Try using .\SQLEXPRESS.
When you installed SQL Server on your local machine, did you install SQL EXPRESS? If so, you may have to use the instance name CHRISW7O980\SQLEXPRESS.
Also, remember that connections over TCP/IP are disabled for newly installed SQL servers. You'll have to enable that in the SQL server manager.
I'm working with a device (barcode printer) that can connect to a database to retrieve some of it's information. I want to host SQL Server Compact Edition on the PC that is talking to the printer. Will the SQL Server Compact allow an external connection from the printer?
Yes, it will for sure. It have limitations, but it can be connected from another machine.
What are the limitations to SQL Server Compact?