topic SQL Server views can be seen, but not for use, after been registered by Management Console in Administration and Deployment

SQL Server views can be seen, but not for use, after been registered by Management Console

Haikuo — Thu, 10 Jan 2013 14:05:18 GMT

Dear Friends,

Now I have ODBC connections to several SQL server database, Using Management Console I have built some libraries and "successfully" registered with both tables and views. The displayed libname statement is as following:

LIBNAME T_SQL ODBC DATASRC=SQLDATA1 SCHEMA=DBO USER=XXX PASSWORD=XXX;

EG opens tables fine, but when try to open views (I can still see them), I got:

[Error] File SQLDATA1.VWXXX does not exist.

[Error] The metadata for the table/view SQLDATA1.VWXXX does not exist.

Now is the puzzling part: if I run the above libname statement using either Base or EG to define a library, views can be opened without issue. That hints pre-assigned option may work, but I want to avoid using pre-assigned setting unless it is absolutely necessary. So is it? is this the case that Meta engine can't have it covered?

Thank you in advance!

Haikuo

Re: SQL Server views can be seen, but not for use, after been registered by Management Console

sas_9 — Thu, 10 Jan 2013 15:38:18 GMT

for base library if you don't want to go for pre-assigned - following options would be work for you

use SASApp as Assigned selected server

on extended attributes tab :

fieldname: Assign Mode

Value: 2

description: Metaout=data

this behavior make it possible to add, modify, and delete table within the library...for the clients i guess...

you would not go for SASMeta as a selected server as you want makes Base libraries available clients...

Re: SQL Server views can be seen, but not for use, after been registered by Management Console

VarshaD — Thu, 14 Feb 2013 14:11:49 GMT

SAS Note at 44703 - Errors opening database views in SAS® Enterprise Guide® or other SAS® client applications

Re: SQL Server views can be seen, but not for use, after been registered by Management Console

Haikuo — Thu, 14 Feb 2013 14:41:09 GMT

Thank you for your answer. SAS Tech support did have referred this same note to us. Unfortunately for some reason the option 2-3 did not work, we had to do "pre-assign" for a while, until we upgraded to M2, then it is all good.