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.
Related
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.
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 have installed mysql and MSSQLSERVER on my windows server 2012 i need to monitor them using system center operations manager 2012 sp1.
now am able to monitor sql server but not the mysql server so can i integrate mysql and microsoft sql server so that i can get all the databases in the mysql as in the sql server. how can i achieve this? is there any way to do this?
The only way to be able to monitor a MySQL Database you must have a proper Management Pack Imported into SCOM. Bridgeways offers such a Management Pack, but it is not free. As today, Microsoft has not yet released a MP for MySQL.
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DSView'. (rsErrorOpeningConnection)
The feature: "The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services. (rsOperationNotSupported)
Hi, I have encountered the above mentioned error while doing an SSRS project. And from the research, it seems like it is SQL server related issue.
I am trying to access a remote SQL server....so I was wondering how can I get rid of that error?
Do I have to install SQL server Standard edition on my local machine or the server that I am trying to access should be installed with Sql Standard edition?
I have got Express editions installed on both my local machine and the server...
Thx
From Books Online:
Report data sources must be SQL Server relational databases that run
locally in SQL Server Express.
Features Supported by Reporting Services in SQL Server Express.
With SQL Server Express you can only use a Data Source where the database engine is from the same instance running SSRS.
If you need to connect to other instances your only options are to get a backup restored to your local instance or to install a SQL Server edition that allows remote Data Sources; most likely Developer for your own needs or Standard or above for any production instances.
It depends on what's allowed under your specific licencing agreement.
A neat way to get around this (that just worked for me) is to add a Linked Server on the Local machine to point to the server that hosts your remote data source.
Then modify your Dataset query in the SSRS report to look something like this...
select * from openquery(REMOTE_SERVER,'Put your original query here');
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.