Synchronization in SSAS
Hi -
I am trying to use synchronization feature of SSAS to synchronize to data bases on different SSAS server. I am assuming that when you try to sync two data bases (these two data bases are replica of each other) with synchronization utility it should copy only the changes. Or it tries to copy all data again. Can some one help me on this?
We have cube of around 140 GB when we are trying to sync its taking around 6 hours. Which implies that its not copying on changes but all data.
Is there any other faster way to sync data between two cube?
Thanks,
[1281 byte] By [
DeepakJ] at [2008-1-10]
I'm pretty sure that the synchronisation feature uses the backup/restore functionality under the covers, so I think it copies the whole database.
Have a look at the "Scale-Out Querying with Analysis Services" whitepaper http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/scoqryas.mspx about 3/4 of the way down there is a description of a custom parallel synchronizing architecture.
Hello everybody!
I'm trying to synchronize my databases using the "Synchronize..." command from Development Studio, but I get the error: "Error at the transport layer. Peer prematurely closed the connection." There is a thread on this forum about this error message (see "Database synchronization IN Analysis Services"). And I have a question: how do you manage to start the synchronizsation at all? How do you do it?
Thanks in advance,
A.G.
This error is not really to do with Synchronizing as such, it indicates a lower level connectivity issue. The following article is quite good for helping with connectivity issues:
http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/cisql2005ascs.mspx
I could not see the exact error message in the article, but there is a mention of the transport layer when the user does not have appropriate permissions. You might want to double check firewall settings and the permissions on the source server. Setting up a profiler trace might help to see if connections are being refused.
Hello, Darren.
Yesterday I searched exactly for the error message, and found several relevant posts. One of them - hosted at www.sql.ru - was done by Mosha Pasumansky - he explained, that this message has something to do with instance security. I'm going to test his solution - I hope, it works.
Regards,
Andrey
Hello again.
I made several tests using SQL Profiler, and noticed the following: the synchronization - ran as XMLA script or directly using menu command - connects to the source datbase using anonymous logon. And is being rejected. Perhaps, this might be the reason for the error at the transport layer.
Regards,
Andrey.
Hello.
There is thread with similair issue: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=560221&SiteID=17
At the present we decided not to use synchronization (another solution found), but I would really appreciate any hint from .NET/SSAS gurus for the workaround. Earlier or later we will come to the synchronizsation...
Regards,
Andrey
That thread is referring to an issue regarding double hop authentication when accessing an SSAS database from ASP.NET code, you said that your were just trying to use the synchronize command from Management Studio. If the source server is in another non-trusted domain you might see this sort of issue, but I don't see how .Net comes into your situation.
