The issue is I get this message. I hadnlt considered using sastrace. Thank you for reminding meof it.   ERROR: BCP initialize error: [Microsoft][ODBC Driver 13 for SQL Server]Connection is not enabled for BCP   Does anyone know how to turn BCP on for Azure? ... View more

Thank you. DBIcommit isn;t an option is SAS 9.2. The options DBIDIRECTEXEC; seems to have sped up the process, but not by enough to use it.   I am going with the BCP load option available in SQL Server ... View more

Back to being unable to connect. libname AZsand ODBC DSN="EReKA DB Sandbox"; NOTE: Libref AZSAND was successfully assigned as follows: Engine: ODBC Physical Name: EReKA DB Sandbox   But no tables appear in the libname.   However,   PROC SQL NOPRINT; CONNECT TO ODBC ( DSN = "EREKA DB Sandbox" ); create table az_counts as select * from connection to odbc ( select ereka_model_seq,count(*) as counter from [dbo].[ereka_model_data] group by ereka_model_seq ); DISCONNECT FROM ODBC; QUIT;   Works. So the DSN is working, just not for a libname. I have tested the conenction through ODBC-32 bit and SQL Server Management Studio.   ... View more

I was making an error somewhere. I am able rto connect via the dsn. Thank you. ... View more

Thank you SAS for providing these links. 10 years ago people would look for data to work with to learn. This is a starting point for people to get some data. Pistol-stem data set will no longer be the only data set people use. ... View more

Not really. Having the encrypted password in the log does not make it secure.You are corect that one does not know the password, but they don't need to know the password in order to get into the system. Internally we lock our databases down to protect PHI and Employee PHI. Having the encrypted password go into a log means someone without access to EPHI can use that login/encrypted password to see EPHI. This user would be internal to the company with access to every system. While {sas02}A48sdgkjsdhkljer may seem secure because you can't see the original password, that encrypted password can still be used to get access to the system. A log file that says password = ********** is secure. ... View more

All great ideas I have aexplored. Peter C. lead me down the path of Creating an Idea which is more of what I needed. ... View more

I need the symbolgen mlogic mprint on for the log files audits. Symget was something I tried in the past and it didn't work. I want a property to be on the macro variable that makes it so SAS knows the macro variable should not be printed versus using a different method of calling the macro variable. This may not be possible as macro variables are plain text with no real inherent properties. ... View more

Chikku, What region are you working in? I would get the BASE SAS certification, Advanced SAS certification, and BI developer certification. If you are good at administering systems, go for the SAS Administration certification. You can take course work from SAS (expensive), read the course books ($100 each), buy the preparation books. There is a SAS professional license ($199 for 6 months and $299 for 12 months) available (SAS® Solutions OnDemand Support). Your local SAS User Group probably has meetings. The one I co-chair is in PDX and they are free, but only occur once a year. For job hunting I use www.indeed.com and www.linkup.com. Post your resume and once you have certifications, you will get a lot of headhunters calling. The jobs may not be great though. Do not underprice yourself. Hiring managers and headhunters know the market rate for SAS programmers and someone that asks for too little will be looked over. Most companies are not posting to job boards either. Job boards are expensive and they have their own internal web pages often. You may have to look at who licenses SAS and just start networking your way in. Sumner ... View more

Daniele, I just recently had this problem myself. You can put the output from the log into a rudimentary dataset using the code below: path = %sysfunc(pathname(work)); /*find out the work directory of current session*/ %put &path; printto log="&path/temp.log" new; /*Create a new log file in the work directory*/ run; proc infomaps; open infomap "<Infomapname>" mappath = <map location in SAS internal foldr system>"; list; run; printto log = log; /*Go back to a new log window*/ run; /*Input log fiel from infomap into a dataset*/ data infomap_metadata;      infile "&path/temp.log" dsd dlm = '`'; /*Nothing in the file is dlm = '`' so whole                                                   row will be in one column*/      input log:$1000.;  /*I want the whole row in one column so I use a large value*/      if index(log,":") > 0; /*Get rid of rows without good data*/ run; That gets you a dataset that can be manipulated. Sumner ... View more

Great response. If I started this company or if SAS had a version of it available, here are my responses. The code would have to be developed by you the owner. Obviously your company isn't going to release the IP it paid you to develop, but many companies will split profit making on products developed. Many places sell their code, but you have to go through their website. There is no central location for finding or depositing code like you might see with CRAN or iTunes. the other side of it could be a consultant resource. Consultant A has code that calculates HEDIS scores (I am in healthcare so examples will come from this). You can buy and run the code, but you might want to hire the consultant for interpreting the results. As a consultant selling code, you would have an asset that can be sold many times to many people. It would generate profit for you with minimal upkeep or development (if you make the code flexible enough). Even if you are not consulting, your code could be earning you money. My biggest area of expertise is in macros. The code could be copied and shared as much as you want, but unless running proc setinit on the machine matches provide the setinit stored in the macro, the macro will not work. I do this a lot for macro variables. If the macro variables are incorrectly specified, then documentation is surfaced in the log window. The macros will obviously be compiled with nosource as the option chosen. This would also force a company to perpetually license your code rather than a one time buy. I am sure their are ways someone could get around this security feature, but hopefully I would have figured out a stronger way to secure the program. Finally, this kind of company would be similar to a social networking site. You are selling your code and consulting services. You would have a profile and availability. You are your own owner. Smith Hanley or any of the other SAS consulting services do not own you or your work. This companies cut would be for providing the service and keeping head hunters away. Companies could view your profile and seek out your services. ... View more