Thanks Audrey
I was afraid that it had been depreciated. Realizing that it didn't guarantee preservation of the cluster ids, it at least maintained the existing cluster id for those existing customers who didn't have changes to their customer information.
The loading of the old records into the Cluster node should work if we were using static data but our customer information is dynamic. In this case corrected information may trigger a cluster between these old records. This would cause renumbering of clusters after that point.
Example for those that may explore this option. Old customer records with cluster id 100 and cluster id 150 have their information corrected and both are now assigned to the same cluster 100 on future Cluster Node runs. This would be OK but customers after 150 will be renumbered.
I can take this one step further and join it back to the original cluster run and maintain existing cluster ids. I am not under this requirement at this time and will forgo this extra step.
... View more
I would like to be able to retain the cluster id assigned to customers in previous runs of a data flow in Data Managerment Studio 2.6.
I have handled this in previous versons of dataflux with the Cluster Update node in dfpower architect 8.1/8.2. So far I haven't identified if this is still an option in or replaced by a different node.
... View more
We will have lots of MS Access databases containing multiple tables, so it will be a time consuming manual step to convert each one, nightly to xls and then to SAS. EG appears to be a more direct option and I have been able to load MS Access tables in the past. Yes, we have SAS/Access Interface for ODBC. Its on a Linux box which doesn't give me the MS Access ODBC driver by default.
... View more
Thanks Andreas I have tried the Proc Import and also the Libname options for accessing the database and SAS come back with the following Proc Import out=work.activities dbms=ACCESScs table="activities"; database="\\10.10.10.13\activity.mdb"; replace table='activity'; port=8621; server="my.web.server.com"; ERROR: DBMS type ACCESSCS not valid for import. I also tried DMBS=ACCESS and received the same message. We are using the 64 bit SAS (accesscs). Run across another option for accessing data and tried the following libname myref pcfiles server="my.web.server.com" 30 port=8621 path="activity/activity.mdb"; ERROR: The PCFILES engine cannot be found. ERROR: Error in the LIBNAME statement. So it appears my Linux install did not come with engines like a Windows 32 bit box would. It appears I'm at a dead end with this option. Option 3) unixODBC for MS Access. Do you/anyone have a recommended unixODBC for MS Access? This appears to be my best option for automation.
... View more
Thanks Doc, I missed seeing the scheduler in the past, so may have a option there. If I get the EG project running on a VM, I may be able leave EG open so it can run as scheduled. Will give it a try if I can't get the unixODBC option going.
... View more
I am attempting to load MS Access data onto a Linux SAS server (BI 9.2) but running into road blocks except when handled by EG. Would really like to schedule these loads outside of EG. 1) This works. EG 4.2 allows me to load each of the tables using my local windows ODBC driver. EG then allows me to insert into/update a SAS dataset. 2) Attempted Proc Import out=work.activities dbms=access table="activities"; database="/var/sasextract/activity.mdb" This returns: ERROR: DBMS type ACCESS not valid for import. I am running on a Linux server. Found one hint for Windows 64 but not Linux with this error. 3) Attempted server based ODBC connection. Currently do not have a unixODBC driver for MS Access loaded on the Linux server. This option works when used with MySQL ODBC driver and SAS/Access for ODBC. 4) I also have access to DIS but it also appears to need a MS Access ODBC driver for Unix.
... View more
Thanks Angela. Do you know where the logon.jsp file will be on a Linux distribution? The only copy I can locate is in the JBOSS directory. ../jboss-4.2.0.GA/server/SASServer1/tmp/deploy/tmp52458sas.svcs.logon-exp.war/logon.jsp. I was expecting from your note that I would first need to update the SAS version and then move it over.
... View more
I am looking for the options on adding a Term of Use statement to the SAS Information Portal website. Currently we are using SAS 9.2 and JBoss which has many customization options in SAS but I haven't run across one that will handle this. My next option would be to put it as part of the description on a collection portlet on the Home tab so that users can read it after the log on.
... View more