I am new to SQL Server and trying to familiarize myself with it, so I have some questions.
My background is Oracle and am wondering if it works very similar to SQL Server.
On a client machine we need to install a client version of Oracle, and with the installation it comes with a TNSNames.ORA file which has settings for all of the Oracle DB's which are located on an Oracle DB server.
I would assume that SQL server would follow something similar, install a client version of SQL server? If so, does SQL Server has something similar to local Oracle?
I've found how connect to SQL server from another computer, just wondering if I still would need a slim down/client version of SQL Server, I would assume yes.
https://technet.microsoft.com/en-us/library/ms345343(v=sql.110).aspx
Some of you might be asking, why don't you try it, don't have my second computer yet, would like this info. ahead of time.
Thank you
SQL Server client APIs include the low-level components needed to connect to and use SQL Server so there is generally no need to install other connectivity components. To name a few Microsoft ones:
ODBC: Latest version is ODBC Driver 13.1 for SQL Server
OLE DB: Latest is SQL Server 2012 Native Client
.Net Provider for SQL Server (SqlClient): included .NET framework
JDBC: Latest Microsoft version is 6.2
There are also a number of other open source and commercial APIs available for use in various programming languages and development frameworks (e.g. Tedious for Node.js).
Related
Suppose that I've created a project using MS SQL Server.
Now if somebody asks me to run my application on their brand new PC, should I install the entire SQL Server management studio on their computer? Or are there any other choices?
Please note that I just want to run my app (.exe template) not to debug it or anything else.
If your application is intended for standalone use on a PC, you can include the redistributable version of SQL Server Express in your installer. It's a limited but functional version of SQL server intended to be included with application programs like yours free of charge.
https://www.microsoft.com/en-us/sql-server/sql-server-editions-express
If your application program is designed for either shared or standalone use, and you have time to polish up your installer, you can ask your users whether they want to use a shared SQL Server instance. That will let you skip the installation of SQL Server Express when it's not necessary.
No they don't need SQL server or management studio , however they a database driver to access the server. ADO, ODBC and JDBC are the types of drivers you would look at. This depends on the language you wrote your application in and the connection string.
You clients would use the server's address and connect to it using the driver which is specified in a connection string. See the examples below:
.Net Framework Data Provider For SQL Server:
Server=myServerAddress;Database=myDataBase;User Id=myUsername;
Password=myPassword;
SQL Server Native Client 11.0 OLE DB Provider:
Provider=SQLNCLI11;Server=myServerAddress;Database=myDataBase;Uid=myUsername;
Pwd=myPassword;
If you application only connect to the database that you have a two-tier client server architecture. For the server to be reachable it needs to be on a network or network endpoint that the clients(people running your software) can see. The server needs to be on as well(your comments).
If I am run OLAP application in SQL installed machine (Machine A), it will work perfectly. But I need to run that application in another machine (Machine B) with Machine A's MSOLAP DLL.
Is it possible?
If yes how can I do that?
Update
I have fixed this issue by using Adomd connection instead of OleDb connection... :)
"MSOLAP.4" is the name of the OLE DB provider for Analysis Services as included with SQL Server 2008. This driver is included with the Feature Pack for SQL Server. The SQL Server 2008 Feature Pack is here. Expand the "Install instructions" header and download the correct "Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider" for your platform.
Since, typically, the latest versions can connect without problems to older versions, and SQL Server 2008 is no longer supported, I recommend installing the version from the SQL Server 2014 Feature Pack instead. Use "MSOLAP" as the provider name in the connection string to use the latest version rather than a specific one.
I have POWERBUILDER 11.1 installed on my workstation, however I dont see the SNC SQL Native client in the Database Profile window. I have reinstalled the IDE multiple times without succesfuly having the SNC SQL Native Client dipslaying. My OS is Windows XP 32 bit.
How do I resolve this issue so I can connect to my SQL DB?
Do you have the SQL Server Native Client runtime installed on your machine? It's a package from Microsoft that is needed to access SQL Server. You can get the SQL Server 2008 version here: http://www.microsoft.com/en-us/download/details.aspx?id=16978 (Scroll down until you find sqlncli.msi). It needs to be installed on all the client machines that will be accessing SQL Server.
It sounds like you need to do a Full install or a Custom install and select SNC. I don't recall if SNC is part of the default installation, but it sounds like not.
Good luck,
Terry.
I think that you can not connect to SQL Server 2008 using PB 11.1, but I am not sure. Maybe you can but I can't remember if it is possible to use all the new features of 2008 version.
I am sure that you can connect to SQL Server 2005 cause I'm doing it every day, but you must first install SQL SNC driver as slapout answered.
Could someone give me an orientation on the use of any version of SQL Server?
I'm working with version 2003 at the moment.
There is a C library freetds that allows you to natively talk to Microsoft SQL Server and Sybase databases.
In order to use it in vala you need to create a "vapi file" (probably writing it manually) containing the class and method declarations in Vala syntax
In addition to the freetds library that o3o mentioned you can use unixODBC to access Microsoft SQL Server.
There are multiple unixODBC drivers for Microsoft SQL Server:
Microsoft ODBC Driver 11 for SQL Server on Linux (There is also an older version available
Microsoft SQL Server driver from easysoft
FreeTDS
There is also a list of unixODBC drviers on their homepage.
There is no readily available vapi file for unixODBC at the time of this writing. I'm working on a two layered approach for this. It's not finished yet, but might be useful someday ;).
I have an Oracle server (version 9, I believe) and a MS SQL server (version 2000). The MS SQL server is running MS Windows Server 2003.
I would like to use DTS to extract some data from the Oracle server and pour it into the MS SQL server. I'm having problems finding out what driver I should install on my MS SQL server for it to be able to communicate with the Oracle server. (I don't really care if it's ODBC or a "native" Oracle driver.)
When I looked at this a while back I was stunned by the sheer number of different Oracle drivers and versions out there. Any help with a direct link to the exact Oracle driver recommended would be greatly appreciated, and I wouldn't mind any other helpful tips you could provide either. :) (Apart from upgrading the server/OS, that's not going to happen any time soon...)
I understand that it's the Instant Client that I'm being recommended to install, but more specifically for my situation, on the page http://www.oracle.com/technology/software/tech/oci/instantclient/htdocs/winsoft.html, are these the two packages I should install?
Version 11.1.0.6.0
Because it's the latest version, and it should be able to connect to Oracle 9.
Instant Client Package - Basic: All files required to run OCI, OCCI, and JDBC-OCI applications
Because "all installations REQUIRE the Basic package", per information at the bottom of the Oracle webpage.
Instant Client Package - ODBC: Additional libraries for enabling ODBC applications
Because I need to use ODBC.
Have I understood this correct?
My first choice would be the Instant Client: http://www.oracle.com/technology/software/tech/oci/instantclient/htdocs/winsoft.html
Although this was not available for 9i, the 10g client will certainly connect to 9i without any problems, and the 11g probably would also.