The ODBC API is based on the CLI specifications from Open Group and ISO/IEC. This API is independent of any one DBMS or operating system although this manual uses C, the ODBC API is language-independent. To many others, it is the answer to all database access problems ever imagined.įirst and foremost, ODBC is a specification for a database API. To the application programmer, it is a library containing data access routines. To the end user, it is an icon in the Microsoft® Windows® Control Panel. If that is the case then I don't know why they would do that as avoiding DSNs also avoids having to maintain ODBC Administrator definitions all the time - a major advantage in my view.Many misconceptions about ODBC exist in the computing world. IT can't stop this happening via security restrictions, they can only say "you must use the ODBC Administrator DSNs". Pretty much anything you can set up in the ODBC Administrator (we are talking Windows only here) defining your DSN can also be done in Management Console or in SAS SQL CONNECT or LIBNAME statements. Not sure what you mean by "IT restrictions". If you want to be sure you can use SQL passthru, but that requires you to write your DSN in code. Then in SQL when you write SQL referring to them, SAS will then process the entire query in SQL Server - in theory.
So you define a data source for each SQL Server database you want. Data Library Manager allows you to set up a connection to one SQL Server database at a time - you are automating the creation of a single LIBNAME statement behind the scenes. Server Manager allows you to define one SQL Server server connection at a time. No need to say sorry - we all learn all the time!
0 kommentar(er)
