This is the error when connecting to server
Please help. When connecting to sql server using odbc.
You're trying to connect to a SQL Server instance that is running on a server that is in a different Windows domain than the client. Either the domains need to trust each other, or you need to login using SQL Server authentication instead of Windows authentication.
Related
We are using a third party software which we have to connect to SQL Server. We are using SQL Server DSN connection, but the third party tool suggested that we have to use SQL Server native client DSN for the better performance.
Please suggest which DSN connection would be preferred SQL Server or SQL Server native client.
Yes always try to use SQL server native client for this. you could download this microsoft site.
For 2008 R2 you need to use SQL SERVER NATIVE CLIENT 10.0 and you could download this form download link
you was asking about which DSN connection would be proffered. I think this depend on your sql server version.
I need to connect a number of MS Access client applications to a SQL Server database. Does the Native Client need to be installed on each client machine or just on the server?
On each client machine.
Here is a link with some additional info.
http://msdn.microsoft.com/en-us/sqlserver/aa937733.aspx
I was able to connect to my database engine using SQL Server 2005 Management Studio, but now I cannot connect using the newer 2008 version.
Has anyone experienced the same problems? Is there a small feature to turn on that I am missing somewhere? Thank you in advance.
Given that you do not provide any usefull informations, like error message, how you tried to connect (windows authentication/sql authentication), .... that's hard to come up with the solution.....
1) try to run SSMS as admin... if you can connect, then grant specific user with proper access
2) if you try to connect via TCIP/IP, try to run SQL Server Configuration Manager to enable TCP/IP protocol
3) if you need sql authentication, change the authentication on the server's properties.
I have two SQL Servers at two different servers:
SERVER 1: SQL Server Enterprise edition 2008 r2 64bit
SERVER 2: SQL Server Standard edition 2008 64bit
I have db_admin permission on both SQL Server, when I am connecting server 1 from server 2 then it is connecting(means connecting enterprise from standard) but when I am doing reverse it is not connecting. How can I resolve it?
Note: When I am connecting SERVER 1 from other servers with same SQL Server edition and vice versa, it is connecting well.
The edition is not going to be relevant if you are using SSMS. When you cannot connect, the problem is usually a configuration issues but if it works both ways to other servers, that might not be the case. Try the below first.
In the server properties dialog of Server 2, go to the Connections tab on the left. About 3/4 of the way down is an option to "Allow remote connections to this server". It should be checked.
If it is checked, the next thing to do is verify what port the server is on. If it is not on the standard 1433, you will need to add the port to the connection (e.g. MyServer,1234)
I have two virtual machines runs on my laptop, let's say their name are VMApp and VMDB, and both are runs the same OS, Windows Server 2008 R2.
On VMDB, I installed all SQL Server 2008 features except the Reporting Services. in contrast, I installed only SQL Server 2008 Reporting Services on VMApp.
I run Reporting Services Configuration Manager on VMApp and point the Server Name to the VMDB's computer name, then I got an error message
"A connection to the computer cannot be established"
I enabled the named pipe from SQL Server Configuration Tools on VMDB, but I still get that error message on VMApp.
I think the problem is not network connection because the VMs are connected in same domain network and they could ping each other.
Sorry for this dumb case because I am newbie in SQL Server, and I really appreciate any help from you guys!
Regards,
Chrisma Andhika
You cant set the DB path to SERVERNAME\INSTANCENAME on the configuration manager. There isnt even that option. First you set the server:
and then the DB:
where exactly are you having your issue?
FYI: try to enable SQL Browser on VMDB or to connect by IP if you cant enable browser