Our organization is running Visual Analytics 7.3 as a non distributed deployment on Linux. It is a standard deployment with the data analysts being assigned the VA predefined role of Data building. However, when they attempt to load a database table by right clicking the table and selecting the load table option and specifying the folder as the autoload folder , they get the error "You do not have permission to add items to the selected folder."    However, for users assigned the predefined role of Visual Data Builder Adminstrator, this process works without an error.    I would like to know if this is the default functionality of these roles in SAS VA. If it is the default functionality, how can users with the role Data building work around the size limitation of 4 GB for data imports? The user guide mentions that the work around for the size limitation is the autoload but I do not see it is as an option for the data analysts because of the error described above.     ... View more

Hello,    I am running into problems working with DBMS column names that have a "/" in them. I noticed that when the library was defined in metadata and the table containing the column name with the "/" was registered, SAS changed the name of the DBMS column that had a "/" in it to an "_". However, when I run a proc means statment using this column as a classification variable, the SQL access driver is not able to interpret this variable and gives me a driver error    "CLI describe error: [SAS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Invalid column name 'Coated'. : [SAS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Invalid column name 'Insulated'. : [SAS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Statement(s) could not be prepared."   For context to the error above, the column name on the DBMS is "Coated/Insulated". When registering the table in metadata, SAS changed the variable name to "Coated_Insulated". The error above was thrown while executing the following statement: "PROC MEANS DATA=RS.tbldimProduct FW=12 PRINTALLTYPES CHARTYPE NWAY VARDEF=DF MEAN STD MIN MAX N ; VAR product_name_id; CLASS Coated_Insulated / ORDER=UNFORMATTED ASCENDING; RUN;"   Is this error specific to the SAS/Access engine 9.4 and is there a workaround? Incidentally, I have set the VALIDVARNAME to v7.   ... View more

Hi,  This is probably a long question. So please bear with me.  I would like some guidance from members on how to effectively set up a directory structure for our SAS deployment. To set the context, we currently run SAS on a Linux environment and have about 10 developers working on different client tools such as Enterprise Guide(EGuide) and Enterprise Miner(EMiner) or Visual Analytics(VA). The current issues that we are coming up against are that these developers create content suich as SAS data sets, EGuide reports/projects, EMiner Models and VA queries and I need guidance on: How do I set up a directory structure so that it is intuitive enough for developers to place their content into the respective folders and i can provide the appropriate permissions to those folders The directory structure should also allow for easy migration of content from a DEV workspace to a QA workspace and then on to a PROD workspace. These workspaces will be be on the same Linux environment as we have do not have separate SAS environments for test and prod. What tools I can use for version control so that I can have multiple developers work on the same artefacts independently but can still keep track of the changes made.   I would love to hear from members about their thoughts on this.  ... View more

Has anyone faced problems while loading an SQL table with long column names? When i try to drag a table having long column names onto a process flow from a library , I get the error that an Open data operation and the error is that the variable < long column name> is not foind in the file. It appears to me that the SAS/Access engine for SQL server is not able to recognize long column names. If anyone has experienced this, would love to know what workarounds are avaialbe for this issue.   Thanks, Sethu ... View more