10-08-2013 07:41 AM
09-11-2013 04:09 AM
On server explorer I can see Phisical drive A: C: D: and network location: B: U: L: that I already mapped.
From Data Integration Studio Browse I can see only the phisical ones.
09-12-2013 06:54 AM
Currently I don't have access to an environment to replicate what you describe so I can't give you a advise for your concrete question.
The approach I'm usually taking is to define the "root" UNC path as macro variable in an autoexec set up for DI jobs. Then I use this macro variable as part of the file path in the external file definition.
I make always sure that the application specific folder structures are the same in all environments so that I can migrate DI jobs between environments without any changes. I need only to populate the macro vars in the autoexec with different UNC paths.
So a filename used in the external file could look like:
And then make sure that you also select "double quotes" for the filename.
The only disadvantage to this approach is that when you click on the external file metadata object you can't access the underlying data as there the macro variable doesn't get resolved. I couldn't figure out yet (and haven't also invested too much time with it) if there would be a way to define the macro variable also somewhere else so that the pathname gets always resolved.
I believe the advantage of this approach is that you don't need to map network drives on the server. In my experience mapping networks on the server is something the server admins in a lot of organisations are very resistant to do.
09-11-2013 03:54 AM
You can use the following code to map a network drive to the SAS Server. \\READYSHARE\USB_Storage is the UNC path you wish to map to t:\.
X 'NET USE T: \\READYSHARE\USB_STORAGE';
If you want to know more then check out How to Map Network Drives From the Command Prompt in Windows.
10-08-2013 07:41 AM
Need further help from the community? Please ask a new question.