I had thought that the underlying database where the data are being stored (SAS, in your example) would have to have intrinsic capabilities of supporting this to make it work, but I certainly could be wrong. Give it a try and let us know.

Mike Rhoads Westat RhoadsM1@Westat.com

-----Original Message----- From: Marty . [mailto:lebeau777@hotmail.com] Sent: Monday, November 15, 2004 4:27 PM To: Mike Rhoads; SAS-L@LISTSERV.UGA.EDU Subject: RE: SQL Server, T-SQL & Linking

T-SQL would handle the data which does support commits and rollbacks. Same way it would if connecting to another sql server.

>From: Mike Rhoads <RHOADSM1@WESTAT.com> >To: 'lebeau' <lebeau777@HOTMAIL.COM>, SAS-L@LISTSERV.UGA.EDU >Subject: RE: SQL Server, T-SQL & Linking >Date: Mon, 15 Nov 2004 12:44:38 -0500 > >Interesting question. Although I haven't tried this, the answer is almost >certainly "Yes, but only up to a point." > >Given SQL Server's ability to link to data in other formats, I can't see any >reason why it couldn't, for instance, retrieve data from a SAS data set. On >the other hand, SAS data sets inherently don't support commit and rollback,

>and I don't see how processing them with SQL Server could add this >functionality. > >Mike Rhoads >Westat >RhoadsM1@Westat.com > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of lebeau

>Sent: Monday, November 15, 2004 10:42 AM >To: SAS-L@LISTSERV.UGA.EDU >Subject: SQL Server, T-SQL & Linking > > >Is it possible to use SQL Server 2000 to work on PC sas datasets. I >would like to use T-SQL and stored procedures to insert and update >data on my sql server. I FTP data from a mainframe to a Windows PC. >I want sql server to handle all the processing (updates, inserts, >commits and rollbacks, etc.). > >I have the SAS ODBC driver and am looking to create a linked server to >a sas dataset on a local machine.