Hey People,
I'm fairly new to SSAS and SSIS, but I've ended up needing to sync an internal SSAS DB into our DMZ SSAS instance.
This crosses domain/forrest, subnet and firewall boundaries.
I've been reading about using IIS to publish SSAS internally.
On an internal -> internal environment (same domain/forrest, subnet and inside the firewall), I can get it working using Windows Auth in IIS.
However, when I try to switch to HTTP Basic auth in IIS, it doesn't appear to attempt to authenticate. (Yes, I'll change this is HTTPS Basic auth later)
I'm using a basic SSIS package, running on the destination server (it's running SQL, SSIS and SSAS), which just consists of an Analysis Services Execute DDL Task containing the following XMLA:
<Synchronize xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine"> <Source> <ConnectionString>Provider=MSOLAP.4;Data Source=http://10.x.x.x/olap/msmdpump.dll;ConnectTo=10.0;UserName=DOMAIN\USER;Password=PASSWORD;Initial Catalog=SSAS_SOURCE_DB</ConnectionString> <Object> <DatabaseID>SSAS_DESTINATION_DB</DatabaseID> </Object> </Source> <SynchronizeSecurity>CopyAll</SynchronizeSecurity> <ApplyCompression>true</ApplyCompression> </Synchronize>
I've seen lots of posts and comments about hooking the likes of Excel into an HTTP published SSAS and being prompted to authenticate, but this needs to be an automated process.
Anyone got any ideas? or can you point me at some decent documentation, as the MS docs don't seem to go any further than "here's how you use IIS to publish SSAS"
Note: this may be better served in the SSAS, so I'll cross-post and link them together.
Thanks
Craig